In a project with more than 3 ISV solutions installed we encountered the following compile error from time to time while updating to a new version of ISV Solutions: [AxFormExtension/EcoResProductDetailsExtended.ourOwnExtension/Controls/FormExtensionControlnhogurxf1/Parent]:The parent 'ButtonGroupNameFromISV' of the additional control 'FormExtensionControlnhogurxf1' was not found on the base form.
We recently upgraded to PU39 and restored a database from a UAT environment to a Test environment (DevTest). After that import and export projects failed without a clear error message. The eventlog stated the following: Application: DMFExecutePackage.exe Framework Version: v4.0.30319 Description: The process was terminated due to
There is a way to get the default report layout by code using the following line: PrintMgmtDocType::construct(PrintMgmtDocumentType::SalesOrderInvoice).getDefaultReportFormat(); Finding the report design from the print management settings for a report type is easy on the surface. As example, navigate to Accounts receivable > Setup > Forms > Form setup, select
There is a good documentation on how to install a deployable package on the various types of environments in the Microsoft Docs which I don't want to repeat here. Recently there was a need to run AXUpdateInstaller devinstall on a Tier-1 Microsoft managed LCS environment for a Platform Update package
Creating a new SSRS Report design for a customer is not a big deal. Overwriting the default report design for a specific document type in the print management is also simple, it just needs an event handler on PrintMgmtDocType.getDefaultReportFormatDelegate with a switch statement on the document type that modifies
After searching to enhance the performance of D365 DevBoxes I tried a lot of stuff. During the analysis one thing stood out clearly: Windows Defender plays a huge role regarding the performance of Visual Studio, the IIS, Database Sync, Report Server and other parts of the D365 environment running on
In a previous article I shared the transition from TFVC to GIT as source control provider with Dynamics 365 for Operations (D356fO). Microsoft does not support Azure Dev Ops (VSTS) automated builds for git repositories by default. When deploying a build environment from LCS, it creates a template build definition