Defining field mappings for attributes in Esri
Define field mappings for attributes stored within GIS and Infor EAM at the layer level. The fields are populated based on the mappings during equipment/feature creation and synchronization.
During equipment/feature creation, the fields are populated based on the mapping relationship, e.g, to create an equipment record based on an existing feature, map data from a GIS attribute to an Infor EAM attribute.
Infor EAM populates the field with the data contained in GIS. You can also define field mappings based on constant values, e.g., enter a GIS value of HYDRANT and map it to the category field in Infor EAM. During equipment creation, the system always populates the category field with HYDRANT.
During synchronization, the system accesses field mappings to ensure corresponding equipment records and features reflect accurate data. If there is a discrepancy in data, the system copies data from one system to the other.
You may map more than one GIS attribute to a single Infor EAM attribute. During creation and synchronization, the system concatenates the data into the single field based on the Sequence and Delimiter.
Likewise, you can map an Infor EAM attribute that contains concatenated data into more than one GIS attribute. During creation and synchronization, the data is parsed based on the Sequence. If the system must parse data because one field is mapped to multiple fields, it verifies that the number of fields to which to map data matches the instances of concatenated data in the source field. If it does not, the data is not synchronized. If, however, the source field in the owner system contains a null value, the null value is copied to the multiple fields in the other system, overwriting any data that those fields originally contained.
Identify a Source system, which controls creation, and an Owner system, which controls synchronization. The data is mapped from the Source system during equipment/feature creation. The data is copied from the Owner system during synchronization. See the following example.
You define the following field mapping for the Hydrant layer:
GIS Attribute | Infor EAM Attribute | Source | Owner |
---|---|---|---|
ADDRESS | Description | GIS | Infor EAM |
During synchronization of the Hydrant layer, the system discovers that a feature with the ADDRESS attribute of 156 Main Street does not have a corresponding equipment record. The system creates an equipment record and automatically populates its description field with 156 Main Street because GIS is the Source.
Later, you update the same equipment record’s description to 256 Main Street in EAM. During the next synchronization of the Hydrant layer, the system updates the GIS feature’s ADDRESS attribute to 256 Main Street because Infor EAM is the Owner of this attribute.