Hello,
we have 1700 records to import for our custom entity in our production. I have created a data import file and mapped all the data correctly but failing while importing with error 'lookup can not be resolved'.
The lookup is referencing to a virtual entity.
The import works fine if i do import 20 records at a time but fails for anymore records with the same error.
i'm having to divide these and import 20 at a time.
Anyone else having the same issue? Any suggestions?
Hello Partner,
'Lookup could not be resolved' usually happens when you are importing child records associated with a parent record, and the parent record doesn't exist or there are two parent records with the same value in the primary field. For example, if you import a contact with the Parent Customer value of 'Acme Inc' then you'll get this error if there is no Acme Inc or more than one.
Can you check your import file and ensure there are no extra commas or other characters. Extra commas will cause errors. You can open your file in Excel and do a Find to see if there are any extra commas. Since some of the records are importing, I suspect some data anomaly like an extra comma, a special character or some other data point that is causing an issue.
Regards,
Mohamed Sanuj Basheer
Stay up to date on forum activity by subscribing. You can also customize your in-app and email Notification settings across all subscriptions.
André Arnaud de Cal... 291,151 Super User 2024 Season 2
Martin Dráb 229,963 Most Valuable Professional
nmaenpaa 101,156