Personalized Community is here!
Quickly customize your community to find the content you seek.
Have questions on moving to the cloud? Visit the Dynamics 365 Migration Community today! Microsoft’s extensive network of Dynamics AX and Dynamics CRM experts can help.
2023 Release Wave 1Check out the latest updates and new features of Dynamics 365 released from April 2023 through September 2023
The FastTrack program is designed to help you accelerate your Dynamics 365 deployment with confidence.
FastTrack Community | FastTrack Program | Finance and Operations TechTalks | Customer Engagement TechTalks | Upcoming TechTalks | All TechTalks
I am using Data Migration tool : AX 2009 while click on generate mapping I am getting the error "The given value of type string from datasource cannot be converted to type nvarchar of specific target column".
Can you tell on what table/field you get this error? Is it a standard or custom one? As you used too many tags in your post, I'm not able to guess in what area you have your issue. Can you also review the tags and only keep the relevant ones?
You have to run the powershell command before you start the imports. This updates the model store schema to accept new models.
The issue of String error should be gone after increasing the length of DMTName EDT.
Please also be noted that the 2009 to D365 tool is still in private preview, you can find this issue on to the Yammer group page - https://www.yammer.com/dynamicsaxfeedbackprograms/#/threads/inGroup?type=in_group&feedId=11106952
Here are some document for the DMT tool.
I am using Data Migration tool : AX 2009 while click on generate mapping I am getting the error "The Microsoft.ace.oledb.12.0 provider is not registered on the local machine".
please help to have a check from stackoverflow, this means you haven't install Microsoft Access Database Engine.
Could you please create a new thread for the new issues, and please mark this as answered if the suggestion works for you.
I'm getting the same error by DMT trying to generate maps, the action you suggested should be performed on D365 side or on AX2009 ?
Business Applications communities