We were importing the data as CSV file. Let\u2019s say, we have one entity named \u201cReferral\u201d in CRM and we need to create multiple \u201cReferral\u201d records after importing CSV file.<\/p>\n
As you can see in below table, CSV data needs to be mapped with \u201cReferral\u201d record field in CRM as below:<\/p>\n
![\"Unable](\"https:\/\/www.inogic.com\/blog\/wp-content\/uploads\/2018\/02\/Unable-to-import-CSV-file.jpg\")
<\/p>\n
Now to import the CSV file in Dynamics 365, perform these steps – Navigate to Setting\u2192Data Management\u2192Import\u2192Click on Import Data\u2192 and then choose the file<\/p>\n
We were experiencing failures while processing some of the data present in the CSV file, when we were trying to import CSV file with above data into Dynamics 365 containing \u201cDate\u201d and \u201cSingle Line of Text\u201d data type. CRM was giving the OOB error \u201cThe source data is not in the required format\u201d<\/strong> and hence, failed few of the records specifically for Date fields <\/strong>while processing.<\/p>\n As shown in below screenshot \u201cReferred Date\u201d was failed, as it was the date field with a format (MM\/DD\/YYYY) in CRM but while importing through CSV file the date format used was (DD\/MM\/YYYY).<\/p>\n We were not sure why this was happening, so to explore it further we did below:<\/p>\n We navigated to \u2192Options\u2192Formats for checking the current format for Date.<\/p>\n And found that Current Format in CRM selected was \u00a0English (United States)\u00a0 as shown below:<\/p>\n When we continued exploring, we found that there was a discrepancy in the date format (DD\/MM\/YYYY) passed in CSV file and date fields format (MM\/DD\/YYYY) present in CRM. And hence while processing through OOB import functionality it failed with the description \u201cThe source data is not in the required format\u201d<\/strong>.<\/p>\n It was happening, because in the US they follow MM\/DD\/YYYY format for date where as in UK they follow DD\/MM\/YYYY format. And in our case source system was the UK and target system was US due which we were getting that OOB error while processing the data with date field such as one which is processed above 30\/01\/2018, as there are no 30 months in the year.<\/p>\n Also, we noticed while importing, there were few data with date field which were processed successfully in excel like with date 12\/01\/2018. (Because there are 12 Months in a year)<\/p>\n We were able to get rid of this failure, just by one step as below:<\/p>\n Navigate to\u2192Options\u2192Formats\u2192Select the Current Format as English (United Kingdom)<\/p>\n And it did work.\u00a0 We were able to import the CSV file. Without any failure.<\/p>\n Note: while using OOB importing functionality make sure that \u201cSource\u201d and \u201cTarget\u201d date formats are same. Because if \u201cSource\u201d system format is different than \u201cTarget\u201d then system will not allow to do so instead it will throw an error.<\/em><\/strong><\/p><\/blockquote>\n We had a business requirement to \u201cCreate\u201d entity records in bulk using OOB \u201cImport Data\u201d feature of Dynamics 365. While doing so, we were experiencing an issue while importing data in Dynamics 365, the error we were getting was \u201cThe source data is not in the required format\u201d We were importing the data as CSV\u2026 Read More »<\/a><\/span><\/p>\n","protected":false},"author":13,"featured_media":11238,"comment_status":"closed","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"om_disable_all_campaigns":false,"_monsterinsights_skip_tracking":false,"_monsterinsights_sitenote_active":false,"_monsterinsights_sitenote_note":"","_monsterinsights_sitenote_category":0,"footnotes":""},"categories":[16,19],"tags":[1748],"class_list":["post-11230","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-dynamics-365","category-dynamics-crm","tag-unable-to-import-csv-file"],"aioseo_notices":[],"_links":{"self":[{"href":"https:\/\/www.inogic.com\/blog\/wp-json\/wp\/v2\/posts\/11230","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.inogic.com\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.inogic.com\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.inogic.com\/blog\/wp-json\/wp\/v2\/users\/13"}],"replies":[{"embeddable":true,"href":"https:\/\/www.inogic.com\/blog\/wp-json\/wp\/v2\/comments?post=11230"}],"version-history":[{"count":0,"href":"https:\/\/www.inogic.com\/blog\/wp-json\/wp\/v2\/posts\/11230\/revisions"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/www.inogic.com\/blog\/wp-json\/wp\/v2\/media\/11238"}],"wp:attachment":[{"href":"https:\/\/www.inogic.com\/blog\/wp-json\/wp\/v2\/media?parent=11230"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.inogic.com\/blog\/wp-json\/wp\/v2\/categories?post=11230"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.inogic.com\/blog\/wp-json\/wp\/v2\/tags?post=11230"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}![\"Unable](\"https:\/\/www.inogic.com\/blog\/wp-content\/uploads\/2018\/02\/1Unable-to-import-CSV-file-due-to-error-The-source-data-is-not-in-the-required-format-in-Dynamics-365.png\")
<\/p>\n![\"Unable](\"https:\/\/www.inogic.com\/blog\/wp-content\/uploads\/2018\/02\/2Unable-to-import-CSV-file-due-to-error-The-source-data-is-not-in-the-required-format-in-Dynamics-365.png\")
<\/p>\n![\"Unable](\"https:\/\/www.inogic.com\/blog\/wp-content\/uploads\/2018\/02\/3Unable-to-import-CSV-file-due-to-error-The-source-data-is-not-in-the-required-format-in-Dynamics-365.png\")
<\/p>\n![\"Unable](\"https:\/\/www.inogic.com\/blog\/wp-content\/uploads\/2018\/02\/4Unable-to-import-CSV-file-due-to-error-The-source-data-is-not-in-the-required-format-in-Dynamics-365.png\")
<\/p>\n![\"Easily](\"https:\/\/www.inogic.com\/blog\/wp-content\/uploads\/2017\/11\/Click2Export.png\")
<\/a><\/p>\n","protected":false},"excerpt":{"rendered":"