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

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

Details can be found here.

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.

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

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.

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

Access denied: SysOperationController

A MenuItem for a SysOperationController should normally look like this:

[SysClientCacheDataMethodAttribute(true)]
public display container displayOnHoldImage()
{
    if (trueContition)
    {
        return ImageReference::constructForSymbol(ImageReferenceSymbol::Pause).pack();
    }
    return connull();
}

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.

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

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

[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

DimensionDisplayValue displayValue = 
LedgerDimensionFacade::getDisplayValueForLedgerDimension(ledgerJournalTrans.LedgerDimension);

public static void setFormViewOption(
    FormRun _formRun,
    FormViewOption _formViewOption = FormViewOption::Details
    )
{
    if (_formRun
        && _formRun.viewOptionHelper())
    {
        _formRun.viewOptionHelper().setViewOption(_formViewOption);
    }
}

Such a case are for example, event handlers that have a predefined parameter profile, but if one of these parameters is not used, it causes a BP deviation.

class MyFreeTextInvoiceHeaderFooterTmpEH
{
    [DataEventHandler(tableStr(FreeTextInvoiceHeaderFooterTmp), DataEventType::Inserting)]
    public static void FreeTextInvoiceHeaderFooterTmp_onInserting(Common sender, DataEventArgs e)
    {
        FreeTextInvoiceHeaderFooterTmp freeTextInvoiceHeaderFooterTmp;
    
        freeTextInvoiceHeaderFooterTmp = sender;
    
        if (freeTextInvoiceHeaderFooterTmp.CompanyBankAccount == "")
        {
            freeTextInvoiceHeaderFooterTmp.CompanyBankName = "Unknown";
        }
    }
}

With the above EH, the following BP deviation would be output because the parameter e is not used:

BP Rule: [BPParameterNotUsed]:The parameter 'e' is not used.

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 reason for this error was quickly found - after downloading the VHD from LCS, the name of the virtual computer was changed, but not all neccessary steps were done. As a result, SQL Reporting Services had a problem, a new database had to be entered here. How this works, and what else you have to consider when renaming a VHD, can be found here.

Executing step: 19
GlobalUpdate script for service model: AOSService on machine: D365FOSHLocal
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: 19 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)

...may be the reason that the computer name of the VHD has been changed, but not all steps recommended by Microsoft have been performed.

What they are can be found here: https://docs.microsoft.com/en-us/dynamics365/fin-ops-core/dev-itpro/migration-upgrade/vso-machine-renaming

Argument to method getFieldValue out of range

During debugging it turned out that a field name could not be determined in the method DimensionDynamicAccountDataEntityResolver.getEnumValue(). However, the responsible method DictDataEntityField.dynamicDimensionEnumartionField() is not visible.

1. Create a New Foreign-Key Relationship to the DimensionAttributeValueCombination Table
2. Select RecId as the index of this relation.
   A new field is now generated in the table and the relation to this field is created.
3. he Extends property of this new field should now be changed to DimensionDynamicAccount
   The field can now be renamed, for example, LedgerDimension.
4. Now another new field must be inserted that derives LedgerJournalACType from BaseEnum.

The following steps are necessary to display such a field in a (separate) form:

1. Place both created fields in the design using Drag & Drop
2. A Segmented Entry Control is created for the field that is to contain the dimension (for example, LedgerDimension).
3. The following properties must now be adjusted in the properties of this control
   • Controller Class: DimensionDynamicAccountController
   • Account type field: The field extended from LedgerJournalACType must be entered here.

Depending on the class that is stored in the Controller Class property of the Segmented Entry Control, further settings may have to be made, although not all of them are always permitted. For more information see https://docs.microsoft.com/de-at/dynamics365/unified-operations/dev-itpro/financial/segmented-entry-control-metadata-specification

Executing step: 42
GlobalUpdate script for service model: MROneBox on machine: localhost
Update the financial reporting database
Job AutoGlobalUpdateMR job failed
The step failed
The step: 42 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)

...may be the reason that the computer name of the VHD has been changed, but not all steps recommended by Microsoft have been performed.

What they are can be found here: https://docs.microsoft.com/en-us/dynamics365/fin-ops-core/dev-itpro/migration-upgrade/vso-machine-renaming

[Control("ComboBox")]
class LedgerJournalTypeCB
{
    public void enter()
    {
        super(); 

        this.delete(enum2str(LedgerJournalACType::Vend));
        this.delete(enum2str(LedgerJournalACType::Cust));
    }
}

Therefore Microsoft offers us the XppBp-Tool, see https://docs.microsoft.com/en-us/dynamics365/unified-operations/dev-itpro/dev-tools/author-best-practice-rules (at the bottom).

This tool is located in the PackagesLocalDirectory\bin directory and can be used as follows:

Xppbp.exe 
    -module:MyModel 
    -model:MyModel 
    -metadata:"C:\AOSService\PackagesLocalDirectory" 
    -all

The used XQuery files can be downloaded from GitHub. How to use them I try to describe here.

1. Install BaseX (and Java if needed)
   https://docs.microsoft.com/en-us/dynamics365/fin-ops-core/dev-itpro/dev-tools/install-basex?tabs=admin
    
2. Download and extract files from GitHub
   https://github.com/microsoft/Dynamics365FO-AppChecker
   The files must be unpacked into the corresponding directory, e.g. C:\AOSService\PackagesLocalDirectory\Bin\AppCheckerRules
    
3. Build model
   In Visual Studio, under Dynamics 365 > Builds models, select the desired model and select the Run App Checks option:
    
4. Check result
   Now corresponding entries should appear in the ErrorList if BP deviations have been detected.
   
   
   In addition, a file AppCheckerResult.xml is stored in the packages directory, where the detected deviations can also be viewed.