Parm methods for Segmented Entry controls
Describes the parm methods that can be set in code on an instance of a Segmented Entry control.
The Segmented Entry control has multiple parm methods that influence how the control will behave. Here is a description of each method.
|parmDataAreaId||The company context that the control is running under. In most cases this is curext() but there are scenarios where forms can manually set different company contexts, surface records from different companies, etc. Forms need to evaluate which context the SEC should be running under the various conditions of the form.|
|parmCurrency||This is used by Account controls for Main account validation. If this property is set, then mainAccount.checkAccountCurrency() is called during Main account validation.|
|parmControlDate||This is used in validating segment values and in some internal queries. The default is to use the current date but there are scenarios when the form would want to set a custom date based on business requirements.|
|parmDimensionAutoCompleteFilter||Adds additional restrictions in order to filter dimension autoComplete data.|
|parmJournalName||This is used in enforcing Journal control.|
|parmDimensionAccountStorageUsageType||This allows the form or class to specify how the segmented entry control is being used on the form. This property is of type: DimensionAccountStorageUsage (an enumeration with values: Setup, Transactional, Alias).|
|parmTaxCode||This was unused and has been removed.|
|parmIncludeFinancialAccounts||Correlates to the design-time property. For more information, see the Segmented Entry control Metadata Specification.|
|parmIncludeTotalAccounts||Correlates to the design-time property. For more information, see the Segmented Entry control Metadata Specification.|
|parmIsDefaultAccount||Correlates to the design-time property. For more information, see the Segmented Entry control Metadata Specification.|