[srussell]

I’ve been importing new leads with the Prevent Duplicate Records option turned on. It’s matching on email (domain only). When NetSuite detects a duplicate LEAD it works as expected, my csv response shows that it failed to import the record due to a duplicate being found. However, duplicates are not prevented in cases where a PROSPECT or CUSTOMER exists with the same domain. In these cases the lead is created. When I go to the lead, the UI will alert to the possibility of a dupe – NetSuite sees that it’s a dupe, why wasn’t it prevented per the import setting?

I’d expect the Prevent Duplicates option to be agnostic about the relationship Stage. I can’t find any documentation that refers to Stage as a factor in dupe prevention. Am I missing something in my settings or process?
This is a cached copy. Click here to see the original post.

[rnedelkow]

This is related to Defect 275673 – CSV > Leads Only Import > Prevent Duplicate Records = T > Detect Customer Duplicates = Email (full) > System does not block import of new Lead even though a Customer Record already exist with the same Email Address. I would submit a case and reference this Defect to receive status updates.

[srussell]

I did, thanks. This is critical defect for users who import leads. I wish it had been noted in SuiteAnswers Answer Id: 31849 https://netsuite.custhelp.com/app/an…nt%20duplicate. Even if it’s not called out as a defect in there, it would’ve been helpful to have known that dupes are only prevented for entities in the same stage.

Does anyone have a viable workaround? As of now we’re stuck with manual dupe checking prior to import.

[Author]

Posts