Dynamics 365 Blog - Posts from März 2020

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

GlobalUpdate script for service model: RetailSelfService on machine: D365Local
Update Retail self service.
UpdateRetailSelfService.ps1 failed.
The step failed
The step: 52 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.AXUpdateInstaller.Program.InstallUpdate(String[] args)
   at Microsoft.Dynamics.AX.AXUpdateInstaller.Program.Main(String[] args)

...it might help to start the Azure storage emulator and then continue the update process at the failed step.

If you should get into the embarrassment of having to delete a label file on a development environment, you should case check afterwards whether fragments of this label file are still left in the following directories:

• C:\AOSService\PackagesLocalDirectory\MyModel\MyModel\AxLabelFile
• C:\AOSService\PackagesLocalDirectory\MyModel\Resources (also in subdirectories per language)

To measure the execution time of a function/logic, you can use System.Diagnostics.Stopwatch:

System.Diagnostics.Stopwatch watch = new System.Diagnostics.Stopwatch();
watch.Start();
// ... do something
watch.Stop();
info(strFmt("%1ms", watch.ElapsedMilliseconds));

I have had the problem in the past that the BP test did not find all expected deviations or even the following error was issued:

[BPFrameworkFatalException]:A fatal exception occured in the Best Practices framework.

In all these cases it has helped to disable the following rule: BPCheckTableDimensionFields

I found the decisive tip in the Dynamics 365 Community