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
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
The FastTrack program is designed to help you accelerate your Dynamics 365 deployment with confidence.
FastTrack Program | Finance TechTalks | Customer Engagement TechTalks | Upcoming TechTalks
I am working in an environment that is utilizing both Dynamics CRM 365 on-premise along with Dynamics AX 2012. Our workflow generally revolves around entering and maintaining accounts within Dynamics CRM with an integration that will create / modify the account in Dynamics AX.
An account was created in Dynamics CRM with the wrong account number, but working as expected, the account was created in AX with the same account number. I've noticed that the Account Num field in Dynamics AX is grayed out and cannot be modified from the UI. My question: Is there a way to update / change the custtable.accountnum field for an existing record, and if so, how would I do that?
I am willing to perform development work such as creating a job and calling an X++ function if necessary.My fear is that a lot of tables reference that account number field such as CustInvoiceJour.InvoiceAccount ...etc and those will all have to be updated as well I'm guessing.
Thanks for your time and I appreciate any and all help!
In AX you can make use of Rename Primary key feature.
This will also update your financial dimension (If you have customer as FD), in case if you are one of the recent version of Dynamics AX. I remember this used to be problem on AX2012-R2-CU7
Please test it on TEST system first, by year end closing.
I still remember that thread when André and Brandon were helpful at discussion.
Thank you for taking the time to respond to me and ultimately helping me out with this problem.
I cannot believe the team and myself all missed that if you right-click on a customer record and choose 'Record Info' there is a rename primary key button right there.
I tested it out in our test environment and it didn't error out at all.
Everything looks great moving forward!
Business Applications communities