Dynamics 365 Blog - Posts from Dezember 2019

When importing data via a self-created data entity that also contains financial dimensions for a self-created table, I recently had the problem that the import always failed with the following error:

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.

In Dynamics 365 for Finance and Operations, only a few steps are required to add a field of type LedgerDimension - that is, a field that is to include financial dimensions - to a (new) table:

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

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

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