Choice lists can be managed in the forms attribute without this having to be defined as an Esri attribute domain (exception: network attribute, asset group and asset type). The selection values are defined directly in the JSON for the masking attribute. If the user selects an entry from the choice list and saves, the associated code value is stored directly in the attribute.
Coded values are used wherever Esri attribute domains can be dispensed with. Extending the selection values is simpler than using Esri attribute domains.
Value_<ChoiceListname><_attributedomaincode>
Part of the name |
Values |
Value_ |
Fixed text. This makes it clear in configuration forms that it is a case of a choice-list entry |
Choice-list name |
Name of the choice list. |
attributedomaincode |
Value of the choice-list coded value |
To ensure that the name of the choice-list is not ambiguous, the use of a combination of utility, feature class and field name is recommended. The feature class name is optional and should be used if the values in the choice list are dependent on the feature class.
Examples of possible choice-list names:
•ELE_CircuitBreakerType or ELEDevice_CircuitBreakerType
•ELE_LampsType or ELEDevice_Lampstype
•GAS_Material or GASLine_Material
Examples
•"Value_ELE_LineMaterial_2" : "Copper",
•"Value_PositionDetermination_XY_Method_3" : "GNSS (GPS)",
•"Value_GAS_BI_MaterialDevice_2" : "Steel",
•"Value_GAS_BI_MaterialLine_5" : "Plastic, unknown",
•"Value_GAS_BI_MaterialLine_8" : "Polypropylene",
•"Value_GAS_BI_MaterialLine_15" : "Polyethylene, HDPE",
•"Value_GAS_BI_LineFunction_2" : "Main gas pipe",
