Coded Value Domains

Feeder Services incorporates common, industry-standard domains to facilitate the creation of Geodatabase Regions (GRRs). Every geodatabase also utilizes domains to ensure data integrity and quicken the editing process, but the domain values vary from customer to customer. Thus, the Feeder Services domains need to by mapped to the customer’s domains.

IMPORTANT:

For most components, you map a Feeder Services domain to an Esri domain. In other words, you map a “drop-down” to another “drop-down.” However, this same subtab also allows you to map equipment specifications to an Esri domain. In this case, you type the equipment specifications for the Feeder Services side, and map to a “drop-down” on the Esri side.
You must map all possible values within the Coded Value Domain. You should analyze your GIS to determine the list of values within the domain, then ensure every value is mapped. If an unaccounted for value “slips in” during the GRR create or update process, the process fails.
Regarding numerical format (especially the use of commas or periods to denote numeric separators and decimals), ensure the format of the coded domain values is defined to match the region where the tenant’s Hosted Edge service is running. In other words, if the service is expecting commas and periods in a certain regional convention, ensure the coded values match that convention.

As an example, here is how to map domains for energized phases:

In the menu, select Coded Value Domains, then click the Add button to map a new domain.
Under Create Coded Value Domain, choose the geodatabase layer you would like to map, then choose the specific field that contains the desired domain.
Choose the equivalent Feeder Services domain. The purpose of mapping is to map the Feeder Services domains (which cannot be edited) to the customer domains (which vary from customer to customer). You are telling the application which Feeder Services domain goes with the geodatabase domain.

IMPORTANT: In this example, we are mapping a Feeder Services domain to anEsri domain. Thus, you would choose the Feeder Services domain as stated above. If you were mapping equipment specifications, you would leave the Feeder Services Domain null, as there is not a domain for these values. When you start to add the Entries, you would type the equipment specifications for the Feeder Services side, and map to a “drop-down” on theEsri side.
Determine whether this domain mapping satisfies all subtypes or not. By default, all subtypes are selected.
1. If you need to specify subtypes, click the Edit button.
2. Click the x to remove a subtype from the list.
3. To add a subtype, click the button that says “Edit.” This opens a separate dialog.
4. Check the desired subtypes, then click Apply.
Determine if this domain mapping should be the default for this feature class and field. If so, set Default to True.

IMPORTANT: What does this default mean? First, if this domain mapping satisfies all subtypes, then this setting is actually unnecessary. It does no harm to set this case to true, but leaving it false also works. The default matters when you are dividing subtypes between different domain mappings. In that case, you need to choose which mapping acts as the default in case there is a subtype that was not accounted for in the schema. As an example, if there is more than one mapping for conductor material and streetlight conductors were never mapped, they use the default mapping. For consistency, we recommend setting a default domain mapping for all feature and object classes (even if the mapping satisfies all subtypes as described above).
To start mapping the individual domain values, next to Entries click Add .
For each coded value, choose the Designer Value, then map it to the appropriate Esri Name.

IMPORTANT: In this example, we are mapping a Feeder Services domain to an Esri domain. Thus, you would choose the Feeder Services domain values as stated above. If you were mapping equipment specifications, you would type the equipment specifications for the Feeder Services side, and map to a “drop-down” on the Esri side.
Next to Entries click the Add button to repeat the process for the next coded value.
Continue until all values are mapped.
Click Save.