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.
2022 Release Wave 1 PlanDynamics 365 release plan for the 2022 release wave 1 describes all new features releasing from April 2022 through September 2022.
2022 release wave 1 plan
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
We are facing a serious issue and would really appreciate any kind of help in this regard.
Couple of days ago, our Ax 2012 R3 application crashed while development on the DEV server and we did not have any back up of our latest changes. All we want is to somehow get the forms, tables and classes code from the Model DB.
Is there any way we can achieve this?
Please help us.....
You can setup a new server, install AX 2012 R3 with the same CU (as the Dev server that crashed) and restore the model DB on this new server and retrieve the code changes. All the code changes are in the model DB, so recovering them shouldn't be an issue.
But, before you go ahead and spend time setting up the new server, did you look for logs to check why the application crashed?
Thanks a lot for the help Gunjan
Can you tell me the process of retrieving the actual code from our customizations?
Will we do it through some cmd commands or there are some folders where the code is saved?
Our Ax is not starting and its showing this error
Please have a look
When you say you want to retrieve the code from the application, what do you want to do with this code? Do you want to deploy the code to another environment for review or do you want to look at any specific code?
As for the error, it looks like you have added the field MTQDepartmentHierarchy twice in DIRPARTYTABLE. I suspect you added it to DirPartyTable and to one of the tables extended from DirPartyTable. You could try cleaning out SQLDictionary and see if you can open the AX application and then remove these conflicting fields from the tables. Try running the following command on your Dev environment AX database and check if that lets you start the application
DELETE FROM dbo.SQLDICTIONARY
WHERE TABLEID = 2303 -- DirPartTable
AND FIELDID = 86131
Business Applications communities