title | description | author | ms.author | ms.topic | ms.custom | ms.date | ms.reviewer | ms.assetid | ms.search.region | ms.search.validFrom | ms.dyn365.ops.version | |
---|---|---|---|---|---|---|---|---|---|---|---|---|
Design-time metadata for Segmented Entry controls |
Learn about the design-time metadata properties for Segmented Entry controls, including a table outlining property details. |
RyanCCarlson2 |
rcarlson |
conceptual |
|
06/19/2024 |
johnmichalak |
b8c5d7a4-ee2b-4ab1-b042-88472b97f035 |
Global |
2016-02-28 |
AX 7.0.0 |
[!include banner]
Describes the design-time metadata properties for Segmented Entry controls.
The custom properties for the Segmented Entry control are found under the Controller group. Here is an example.
Certain properties may be non-editable based on the Controller class that is selected. This is because only certain properties are relevant for each of the various controller classes. For more information, see Valid properties.
Property | Valid values | Usage |
---|---|---|
Account Type Field | A field from the data source. | Determines the type of account used. Typically used for journal entry from a multi-segment ledger account to single segment values from other backing tables, such as Cust, Vend, Bank, Project, and similar. |
Controller Class | One of 7 Controller classes. For example, LedgerDimensionDefaultAccountController. | Determines the pattern and behavior of the Segmented Entry control. |
Include Financial Accounts | NoYes | Determines if Main accounts that are Financial accounts are valid for use. |
Include Total Accounts | NoYes | Determines if Main accounts of type Total are valid for use. |
Is Default Account | TrueFalse | For a Dynamic account, determines if the account should be a default or full account. |
Lock Main Account Segment | NoYes | Controls whether the Main account segment is locked. Typically used in journals and distributions based on configuration. |
Posting Type | A value from the LedgerPostingType enumeration. | The Main account is validated to see if the posting type can be with that account. |
Validate Blocked For Manual Entry | NoYes | Determines if the 'Blocked for Manual Entry' status on the dimension should be respected. |
The following sections show which properties are valid for each Controller type.
BudgetLedgerDimension: Yes
BudgetPlanningLedgerDimension: Yes
DimensionDynamicAccount: Yes
LedgerDimensionAccount: Yes
LedgerDimensionDefaultAccount: Yes
LedgerDimensionAccountAlias: Yes
BudgetLedgerDimension: No
BudgetPlanningLedgerDimension: No
DimensionDynamicAccount: Yes
LedgerDimensionAccount: No
LedgerDimensionDefaultAccount: No
LedgerDimensionAccountAlias: No
BudgetLedgerDimension: No
BudgetPlanningLedgerDimension: No
DimensionDynamicAccount: Yes
LedgerDimensionAccount: No
LedgerDimensionDefaultAccount: No
LedgerDimensionAccountAlias: No
BudgetLedgerDimension: No
BudgetPlanningLedgerDimension: Yes
DimensionDynamicAccount: Yes
LedgerDimensionAccount: Yes
LedgerDimensionDefaultAccount: Yes
LedgerDimensionAccountAlias: No
BudgetLedgerDimension: No
BudgetPlanningLedgerDimension: Yes
DimensionDynamicAccount: Yes
LedgerDimensionAccount: Yes
LedgerDimensionDefaultAccount: Yes
LedgerDimensionAccountAlias: Yes
BudgetLedgerDimension: No
BudgetPlanningLedgerDimension: No
DimensionDynamicAccount: Yes
LedgerDimensionAccount: No
LedgerDimensionDefaultAccount: Yes
LedgerDimensionAccountAlias: No
BudgetLedgerDimension: No
BudgetPlanningLedgerDimension: No
DimensionDynamicAccount: Yes
LedgerDimensionAccount: No
LedgerDimensionDefaultAccount: Yes
LedgerDimensionAccountAlias: No
Support for Segmented Entry controls on dialogs
Parm methods for Segmented Entry controls
Migrate Segmented Entry controls
Migration guidance for Segmented Entry controls
[!INCLUDEfooter-include]