Choose your path Increase your proficiency with the Dynamics 365 applications that you already use and learn more about the apps that interest you. Up your game with a learning path tailored to today's Dynamics 365 masterminds and designed to prepare you for industry-recognized Microsoft certifications.
Visit Microsoft Learn
2019 release wave 2 Discover the latest updates and new features to Dynamics 365 planned through March 2020
Release overview guides and videos Release Plan | Preview 2020 Release Wave 1 Timeline
Ace your Dynamics 365 deployment with packaged services delivered by expert consultants. | Explore service offerings
Connect with the ISV success team on the latest roadmap, developer tool for AppSource certification, and ISV community engagements | ISV self-service portal
The FastTrack program is designed to help you accelerate your Dynamics 365 deployment with confidence.
FastTrack Program | Finance TechTalks | Customer Engagement TechTalks | Upcoming TechTalks
For some reason, when I attempt to import data from an excel that was previously exported; for best practices. It gives me an error code -2,147,158,525 and all I did was change some values to see if it would take back import. I do not know what else to do... Please help!
Please share error details. As you said the excel was previously exported , if its backup purpose you can delete all the existing record and re-import again.Another options would be download the import template and fill the data for import.
That's exactly what I did with the excels templates and unfortunately, none of the options worked. I wonder if it has to do with the fact that I created these entities?
Here are some details, but not sure if these are the ones because on the "failures tab / Import logs" it shows that record (the testing one) that failed with error code "-2,147,158,525 " I click on it and it takes me to the detail below. I basically created a record; exported the excel and then just edited a value like instead of 100 to 50 just to see if at least that would work, but it would not take it back.
Something has gone wrong. Check the technical details for more details.
Session Id: cb488956-5c2f-4850-ba77-c6a82c6c9dc2
Activity Id: 501511c4-8520-46da-b778-9e17e7a50df9
Timestamp: Fri Dec 13 2019 21:58:52 GMT-0600 (Central Standard Time)
Form descriptor is null or not defined
UciError: Form descriptor is null or not defined at i (ar.crm.dynamics.com/.../app.js at new m (ar.crm.dynamics.com/.../app.js at ar.crm.dynamics.com/.../editformpage.js at Object.execute (ar.crm.dynamics.com/.../editformpage.js at ar.crm.dynamics.com/.../app.js at new Promise (<anonymous>) at S._executeAsyncAction (ar.crm.dynamics.com/.../app.js at S._executeAsync (ar.crm.dynamics.com/.../app.js at S.executeAction (ar.crm.dynamics.com/.../app.js at t.dispatch (ar.crm.dynamics.com/.../app.js
Thank you so much for your time,
Error code -2,147,158,525 denotes that the original record does not exist in CRM.
Information of the older records are stored in the column A, B and C in exported excel file and these columns are hidden by default.
Kindly try the below workaround and let me know if this helps.
(File > Save As > File type : CSV (Comma Delimited) (*.csv))
2. Open the newly saved CSV file, select all columns, right click on the column heading and select Unhide option.
3. Delete the columns A, B and C which has (Do Not Modify) text.
4. Save the file.
5. Go to CRM and import the CSV file using “Import from CSV” option. Keep the default delimiter settings and map the required fields if not already mapped and submit the import.
This should let you import the data back to system. There is a possibility that you may hit -2147220650 error which usually occurs due to formatting mismatch between the import file and CRM, this can be fixed by validating the formats in both sides and avoid the columns like Created On and Modified On in the import file.
Please let me know if you have any queries on this.
I did as you said... Thank you so much for your time; the only thing is that now is showing another error :(
" -2147220654 A duplicate lookup reference was found" and I am allowing duplicates... I am literally doing just minimum editing. I also went to data management and tried from there, making sure duplicates are allowed. Played with it, but no luck yet my friend...
This issue usually occurs when we have a lookup field in import file and the target entity of that lookup has multiple records with same name. Below is the repro to explain this scenario better.
Below is the import file which has lookup fields "Potential Customer" and "Account".
After importing above data, system throws below errors in Transform phase since the both lookups target to entity "Account" and this error means that the account entity has multiple records with the same name "Test". (Column Heading and Column Value fields would let you know the affected lookup and duplicated record name)
In UI, for the same field when you enter "Test" and search, all the accounts with name "Test" would be shown for you to select and proceed further, but in the data import scenario when the system gets more than 1 result for a particular record it will not be able to conclude which is the right record to be used and throws an exception.
To fix this, you can follow any of the below approaches.
a. In my scenario I have Account Number field which is unique in Account which is targer entity of the lookup, I can now use this field in the lookup mapping during the import.
b. Modify the import file so that the lookup fields would have the unique column's value. (Account Number)
c. Now during the import we can configure the mapping for the lookup field so that it uses the unique field as well. Follow step 1, 2 and 3 from below image.
d. Complete the import and now the data should be imported.
Please let me know you have any queries on this. :)
First of all; I am very grateful for your help given and allow me to inform you that:
1. This link was great and very useful (docs.microsoft.com/.../dynamics_error_codes)
2. The use of the csv file workaround worked fine.
3. I am taking all your suggestions about duplicates and unique columns' values into consideration when errors appear.
So I made all the fields as optional in order to not have to fill all the values on the excel to be imported and have the ability to just work with the fields that were not causing errors and that is what I am doing now... meaning that, some testing is being done.
Glad I could be of some help :)
Business Applications communities