Dynamics 365 Blog - Microsoft Dynamics 365 for Finance and Operations

To run unit tests on a development environment via Powershell, you can use SysTestConsole.exe:

.\SysTestConsole.exe /test:NameOfTestClass1,NameOfTestClass2 /database:axdb

Are you familiar with Microsoft Dynamics 365 - Translation Service in LCS?

With it you can translate your label files fully automated - very cool!

Details can be found here.

During the data upgrade of an AX 2012 R2 to Dynamics 365 for Finance and Operations I had the following errors when running the "DataUpgrade-Package" at step 9:

Error during AOS start: Cannot create a file when that file already exists.

In my case, restarting the environment hosted on Azure and restarting the step helped.

During the data upgrade of an AX 2012 R2 to Dynamics 365 for Finance and Operations I had the following errors when running the "DataUpgrade-Package" at step 8:

Infolog diagnostic message: 'Cannot create a record in Roles (LogisticsLocationRole). Role: Stabile Organisation, Stable organization. The record already exists.' on category 'Error'. 08/20/2019 14:52:12: Application configuration sync failed.

This was caused by two records in the LogisticsLocationRole table that were created in the source environment (AX 2012 R2) by hotfix KB4048614. Interestingly, this hotfix is exactly the one that should be applied before upgrading from AX 2012 R2 to D365.

In my scenario, I was able to use the statement below to delete the records and successfully restart step 8.

delete from LOGISTICSLOCATIONROLE
where type = 104 or type = 105

If the following error occurs during a platform update of a local VPC...

GlobalUpdate script for service model: AOSService on machine: D365Local
Sync AX database
The running command stopped because the preference variable "ErrorActionPreference" or common parameter is set to Stop: System.Management.Automation.RuntimeException: An exception of type System.Net.WebException occurred when making an http request to: http://127.0.0.1/ReportServer. Refer to the log file for more details.
The step failed
The step: 25 is in failed state, you can use rerunstep command to debug the step explicitly
   at Microsoft.Dynamics.AX.AXUpdateInstallerBase.RunbookExecutor.ExecuteRunbookStepList(RunbookData runbookData, String updatePackageFilePath, Boolean silent, String stepID, ExecuteStepMode executeStepMode, Boolean versionCheck, Parameters parameters)
   at Microsoft.Dynamics.AX.AXUpdateInstallerBase.AXUpdateInstallerBase.execute(String runbookID, Boolean silent, String updatePackageFilePath, IRunbookExecutor runbookExecutor, Boolean versionCheck, Parameters param)
   at Microsoft.Dynamics.AX.AXUpdateInstaller.Program.InstallUpdate(String[] args)
   at Microsoft.Dynamics.AX.AXUpdateInstaller.Program.Main(String[] args)

...it might help to start the Reporting Services manually using the Reporting Services Configuration Manager for SQL Server 2016 and then continue the update process at the failed step.

To display a line bold in a grid, you can overwrite the method displayOption() of the FormDataSource:

public void displayOption(Common _record, FormRowDisplayOption _options)
{
    MyTable myTable = _record as MyTable;
            
    super(_record, _options);
            
    _options.fontBold(false);
            
    if (true)  
    {
        _options.fontBold(true);
    }
}

If the following error occurs when calling a SysOperationController, a possible cause may be that the properties Enum Type Parameter, Enum Parameter and Parameters are not filled in the calling MenuItem.

Access denied: SysOperationController

A MenuItem for a SysOperationController should normally look like this: