Limitations

GIS mappings have these limitations:

• The GIS synchronization process can add values for Operations and Regulations code definitions if new values are detected in the GIS, but the reverse is not true. There is no mechanism to add new code definition values in the GIS.
• If a GIS mapping is configured to synchronize data from the GIS to Operations and Regulations, and a GIS feature is deleted, the corresponding record in Operations and Regulations will not be expired. If the mapping is configured to create a GIS record when a new Operations and Regulations is detected, the deleted GIS feature can even be recreated. For this reason we recommend that you do not delete GIS features. Instead you should use an attribute of the GIS feature to indicate that it is expired.
• When data is exported from Operations and Regulations to the GIS, there is no mechanism to determine when the GIS feature was last modified. As a result, GIS data can be overwritten if a record is updated manually in the GIS at the same time it is synchronized from Operations and Regulations.