Personalized Community is here!
Quickly customize your community to find the content you seek.
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
2021 Release Wave 2Discover the latest updates and new features releasing from October 2021 through March 2022.
2021 release wave 2 plan
The FastTrack program is designed to help you accelerate your Dynamics 365 deployment with confidence.
FastTrack Program | Finance and Operations TechTalks | Customer Engagement TechTalks | Upcoming TechTalks | All TechTalks
I have business case and I must migrate NAV 2013 R2 from one domain to another. I have test environment where I have done to authenticate with new domain in new system, but I have another problem with old records. e.g. when I open "My Advanced Statements" I can't see old records created by me. I know that there are tables and there are relations by user ID and it must be changed.
Question: Is there any guideline from Microsoft or is there any tool to migrate from one domain to another ? Or maybe is there exact SQL steps what to change ?
Thank you in advance
There have never been best practice within this migration except to invalidate all old users by disabling all of them and creating the new ones. This will make everything consistent, even the record entered with the old USERID (that will have a orphaned SID, of course).
In your case, having completed the migration, you only have to use batch jobs to amend all of the orphaned USERIDs in related table if you want to clean them up. If they do not harm, you could even leave them there.
Rest assured that NAV 2013 R2 is out of mainstream support and it would be strongly advice to upgrade to the latest and greatest version.
You might take the chance, instead of a cleaning up now the database, to create a new implementation project instead of an upgrade and only move master data and open entries into the brand implementation (instead of upgrading)
Thank you for answer.
Business Applications communities