Common Data Import Errors in Data Extension

 Common Data Import Errors in Data Extension

In this article lets go through some of the common data import issues that we encounter while loading data. These learnings will help you avoid Import pitfalls and save your time during development or importing of data into Data extensions.

Issue 1: We try to set the field as non-nullable in our data extension and try to import data with null values.
Solution: Before quickly changing the field value to nullable on data extension to fix the issue, analyze your data or business use case if you are ok loading the field as null or populating the data.

Issue 2: No such column name exists in Data extension
Solution:  This is one of the most common errors that is encountered by customers. While importing data you might have selected the data extension field to be mapped based on the header of the file. If there is a column mismatch on your header then you will see this kind of error. Fix your header and re-import the file.

Issue 3: Date Format Issue
Solution: Marketing Cloud supports a wide variety of Date ranges. Go through below article to see supported date formats
https://help.salesforce.com/articleView?id=mc_overview_supported_date.htm&type=5
Note: Times shown in the journey and triggered send tracking information remain in CST regardless of setting.

Issue 4: Date Time field in Marketing Cloud
Solution: In the Marketing cloud, the Date field supports both Date and Date time values. If you specify Date as January 1st, 2019 then MC defaults to 01/01/2019 00:00:00. It would be confusing initially as we have both Date and Date time fields in Sales cloud/salesforce

Issue 5: StartDate issue when bringing in Data to Marketing cloud from other systems
Solution: When you are bringing in data from other systems we commonly have the start date as 01/01/1111 if the component system does not support null in date fields. In Marketing Cloud the Start Date will start from 12/31/1772 00:00:00

Issue 6: EndDate issue when bringing in Data to Marketing cloud from other systems
Solution: When you are bringing in data from other systems we commonly have the End date as 01/01/00 if the component system does not support null in date fields. In Marketing Cloud the End Date could up till 12/31/9999 23:59:59

Issue 7: “Import Validation Error: CaseSensitiveSalesforce Error Id” while loading data into Data extension
Solution: If you have one of the columns starting with Salesforce object id (001/002/003/etc) and the length of the column is 15 digit then you get this kind of error even though it may not be a Salesforce id.  To turn off this validation work with support or add MC as a prefix to records while you work with a support team member.
https://help.salesforce.com/articleView?id=000312821&type=1&mode=1

sfdclightning

Related post