Error- During the package deployment or applying VSTS/DevOps build package in UAT or Production , below error is coming in LCS (Life cycle services
“The selected package is missing the following modules that are currently deployed on your environment. You must create an all in-one deployable package that contains all your code customisations & ISV solutions.More information can be found at the following link:https://go.microsoft.com/fwlink/?linkid=2118104.Missing module(s) [AcxDocumentReports]“
Requirement: In last post i demonstrated how can we create A New Production Branch In VSTS (Visual Studio Team Services)/Azure DevOps & Microsoft Dynamics 365 finance and operations. To See my last post please click here. In this post i will show how can we Merge Branches in VSTS/Azure DevOps and Microsoft Dynamics D365 finance and operations or how can we move change or CHANGESets from one dev branch to another prod branch. Before starting this tutorial i will recommend you to please go through my last post.To See my last post please click here
Right Click on SOURCE Branch & choose option MERGE
Browse TARGET Branch
You can choose 2 option for branch changes you would like to merge.First one is “ALL CHANGES UPTO SPECIFIC VERSION” & second one is “SELCTED CHANGESETS
Introduction : In Microsoft Dynamics 365 & VSTS/Azue DevOps practice, it is always recommended to use a separate branch for production deployment else incomplete code of developer will get included in production deployment package.Developers checkedIn code or any development changes frequently in one dev branch but package should not be created from that branch in which developer is doing checkIn. Only required changes should be merged from dev branch to prod branch in Microsoft Dynamics 365 finance and operation & VSTS/Azue DevOps. Please click here to read my post – D365 FO/AX7: Merge Branches Or Moving Changes from One Branch To Another in VSTS/Azure DevOps
Requirement : Create A New Production Branch In VSTS (Visual Studio Team Services)/Azure DevOps & Microsoft Dynamics 365 finance and operations.
Once Branch of production will be created you can merge code from DEV branch to PROD branch as per requirement.In next tutorial i will show you how can we merge code from one branch to another.
Login to your Microsoft Dynamics 365 finance and operations development server.
Open visual studio in Microsoft Dynamics 365 finance and operations development server using run as administrator.
Click on VIEW tab and open TEAM EXPLORER in Visual studio of D365 fo development server.
Some X++ hotfixes related to model “DemoDataSuite” belongs to your one-box development machine only.It means you cannot deploy it on UAT or on production environment else you will get below error related to applicationfoundationformadaptor dependency
The running command stopped because the preference variable “ErrorActionPreference” or common parameter is set to Stop: Unable to resolve dependency ‘dynamicsax-applicationfoundationformadaptor’.
To exclude package “DemoDataSuite” or any other model from VSTS Or DevOps build output you can set the parameter or variable PackagingExclusions before queuing the build.Once the build will complete, deployable packages or artifacts will not contain excluded models.
Microsoft Dynamics AX, Microsoft Dynamics 365 for Finance and Operations, D365 FO, Retail, SQL, Microsoft Power Apps, Microsoft Power BI, Microsoft Azure, Logic Apps, Microsoft Flow, Microsoft power automate, Microsoft Power Platform,.Net, X++, C#, Power BI DAX, Data Warehousing, Microsoft Analysis Services, SQL Server Reporting Services