Import Failing with Unique Constraint Error
Issue: Lead import is failing for specific leads at the time of import and the Message comes as a Unique constraint error from the Prospect Base table.
Resolution: If an account has 2 unique fields, Email and Phone. And while importing both fields are imported as a record under the same row.
Example: Lead1 has Phone P1 and Email E1. But on LeadSquared there are 2 different leads, one with Phone P1 and Email E1.
Now, whichever Search key you will use while import, for example we select Phone, the system will search the account with lead that has phone number and will try to update the email ID of that lead.
Since a other lead with the email E1 already exists in the account, the import will fail with the unique constaint error.
Related Articles
No Error message on Unprocessed leads in import
Issue: When we import leads into LS, and if any of the leads are unprocessed due to any reason, the Unprocessed reason is not shown by default. Resolution: There is an explicit setting that needs to be enabled from the backend so that the Unprocessed ...
Opportunity import error | Updation | Import restrcition
Issue reported: When trying to update opportunities using the opportunity import function, the following error is displayed in the import report as shown below. Import parameter to be noted - Overwrite duplicates. Error message - "Creation of new ...
Explanation/ Solution: Lead Import Error - Column Header must not be longer than 64 characters
Issue/ Error :: While importing leads, user is getting the error Pop-up stating “Column Header must not be longer than 64 characters”, post file upload. Explanation :: It can be due to wrong CSV encoding or longer text string in headers of the ...
Issue while updating opportunity through Opportunity Import
Issue: The customer faces an issue during the import process when selecting "Overwrite duplicate" to update opportunities. An error message, stating "Creation of new opportunity is restricted," appears, even though they are not attempting to create ...
Behaviour of Origin field for opportunity created via Import
Issue: When checked under manage opportunity page the origin field value is empty Root cause: The origin field value is blank, in the scenario where opportunity has been created by Opportunity Import. Solution: As a workaround it is suggested that ...