Note
Access to this page requires authorization. You can try signing in or changing directories.
Access to this page requires authorization. You can try changing directories.
Note
Community interest groups have now moved from Yammer to Microsoft Viva Engage. To join a Viva Engage community and take part in the latest discussions, fill out the Request access to Finance and Operations Viva Engage Community form and choose the community you want to join.
Describes the code pattern to add Segmented Entry controls to dialogs.
The process to add Segmented Entry controls to dialogs has changed. This code is an example from Dynamics AX 2012:
DialogField dialogFeeLedgerDimension;
LedgerDimensionAccountController ledgerDimensionAccountController;
dialogFeeLedgerDimension = dialog.addFieldValue(extendedtypestr(LedgerDimensionAccount),feeLedgerDimension,"@SYS119703");
ledgerDimensionAccountController = LedgerDimensionAccountController::constructForDialog(dialogFeeLedgerDimension);
In the current release, this code would be converted to:
DialogField dialogFeeLedgerDimension;
dialogFeeLedgerDimension = SegmentedEntryControlBuild::addToDialog(
dialog,
classstr(LedgerDimensionAccountController),
extendedTypeStr(LedgerDimensionAccount),
"@SYS119703",
feeLedgerDimension);
For the second parameter, choose the class that satisfies the requirements for your dialog. The options are:
- LedgerDimensionAccountController
- LedgerDimensionDefaultAccountController
- DimensionDynamicAccountController
- BudgetLedgerDimensionController
- BudgetPlanningLedgerDimensionController
This scenario is a simple dialog scenario around Segmented Entry. More advanced scenarios include:
- Binding the dynamic account type.
- Company selection support.
- Account structure selection support.
Additional resources
Design-time metadata for Segmented Entry controls
Parm methods for Segmented Entry controls