End of mainstream support for Microsoft Dynamics AX 2009, 2012, and 2012Mainstream support for Dynamics AX 2009 Service Pack 1 (SP1), Dynamics AX 2012, and Dynamics AX 2012 R2 ended Oct. 9, 2018. After that date, only security hotfixes will be provided for these three versions through the extended support period that until Oct. 12, 2021. Read more
2019 release wave 2 Discover the latest updates to Dynamics 365Release overview guides and videos Release Plan | Early Access Availability
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 and Operations TechTalks | Customer Engagement TechTalks | Talent TechTalks
I have connected my AX 2012 R3 to Azure devops, and have implemented the build and release, however am moving projects from dev to UAT to Production, but I have to export the project into shared location then import it through devops.
while checking in the project, I can find it in the shared folder files on azure devops, but it seems empty, and when I release it, only the project moves without its elements, that's why I have to export it into shared location and release it with devops,
so my question is how can I check in the project to devops and makesure all its elements are within it so I release it from the checked in location and not from the exported shared file location ?
Thank you on advance.
That's correct - projects contains only links to actual elements stored elsewhere. You could export to .xpo, which would include elements in the project, but it would be a wrong way, because .xpo files are not intended for deployment.
The best approach is having a build server, which will create a model file based on data in Azure DevOps. If you're unable to set up a build server, export and import a model directly from DEV, but don't forget that it's not without risks. You could export changes that don't exist in version control, which wouldn't happen with build server.
Also, make sure you read Deploying Customizations Across Microsoft Dynamics AX 2012 Environments (White paper).
Thank you Martin,
so please correct me if am wrong, the best practice is to have Dev, Build, UAT, Production environment, once code checked in on dev, the model store is moved to build, and then on build the model is exported, then released to UAT and production. right ?
Thanks a lot.
No, the modelstore is not moved from DEV to the build server. The build server is where models are build based on source code stored in Azure DevOps.
The usual approach (in my experience) is deploying models to test environments and ultimately to Pre-Live, where a whole modelstore is taken to Live.
Thanks a lot Martin
Business Applications communities