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:
Create a New Foreign-Key Relationship to the DimensionAttributeValueCombination Table
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.
he Extends property of this new field should now be changed to DimensionDynamicAccount
The field can now be renamed, for example, LedgerDimension.
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:
Place both created fields in the design using Drag & Drop
A Segmented Entry Control is created for the field that is to contain the dimension (for example, LedgerDimension).
The following properties must now be adjusted in the properties of this control
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:
A new field is now generated in the table and the relation to this field is created.
The field can now be renamed, for example, LedgerDimension.
The following steps are necessary to display such a field in a (separate) form:
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