Personalized Community is here!
Quickly customize your community to find the content you seek.
Now Available in Community - New TechTalk Videos for 2020
Read More about New TechTalks for 2020
2020 Release Wave 2Discover the latest updates and new features to Dynamics 365 planned through March 2021.
Release overview guides and videos Release Plan | Preview 2020 Release Wave 2 TimelineWatch the 2020 Release Wave 1 virtual launch event
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
We are currently working on data migration using the Data Management module. The scenario we are trying to achieve is to check if a foreign key for a specific entity exists before the row gets inserted so that the insert will not fail. If the foreign key does not exist, then insert the foreign key before inserting the current row. Where is the best place to execute this login? At the entity level or the staging table level and in which method do you recommend to run such code?
Take a look at link below that states different methods available and it's usage.
It also give you difference between entity validation vs. table validation. Since you are doing data migration, i suggest that you do validate data outside D365 to make sure your validations doesn't create any performance related issues.
E.g. if you are importing customer and it has customer group as reference field from CustGroup table...just do validation on customer outside AX that all custGroup as valid per AX. you can write that scripts outside and your data import would be much faster.
Moved to D365 forum.
I do agree with Satish,
It might be much faster to e.g. first load all distinct values in the reference table. Then import the file. A check if something exists or not will slow down the import, but also the effort to put in the coding for each scenario is time consuming.
Business Applications communities