Required Field Mappings

While there is general flexibility on how you map the fields expected by Feeder Services to the fields in your GIS, there are few fields that must be mapped as described below (letter casing does not matter). These are “first-level” properties on components.

• SubnetworkName must map to SubnetworkName (or the name of your company’s field that tracks subnetwork name) and nothing else.

• LifecycleStatusType must map to LifecycleStatus (or the name of your company’s field that tracks lifecycle status) but could also map to additional fields.

Regarding LifecycleStatus, if you need to map this to an additional field, you can, but you must change the Designer field name to a non-matching name. For example, if you need to map the LifecycleStatus to another field, you can change the Designer field name to Lifecycle_Status (with an underscore) so that the fields names do not match. That is just an example, and the important takeaway is the name must be different.