Warnings |
Resolution |
Missing Optional Feature Class Common ID Link Fields for a feature class |
You have not defined fields for data in the "Parent Record Linking Information" section of the synchronizer setup. This data is optional, you do not need to define it if you do not want this data maintained. For example, if you want the system to automatically associate trees in a tree feature class to the street that they are planted next to, we allow you to define a field in your feature class that stores the segment ID. You can use the spatial relationships to define a relationship so that the field is automatically populated, and when you save edits, it will associate the tree to the segment automatically in the desktop. This is optional. |
Data in CMARCFLD and ??FIELDS does not match. This data will be synchronized to the geodatabase when changed in the desktop but not vise-versa. |
There are two tables used to store the field mappings between the desktop and your geodatabase feature class. One table tells ArcMap how to update the desktop when edits are saved, the other table tells the desktop how to update your geodatabase when edits are saved in the desktop. If you get this error, it means that there is a field that will get synchronized when edits are made in the desktop, but this field will not get synchronized when edits are made in the map. This may be desirable if it is a field you do not want map editors to update, and only want the desktop users to update. If this is not what you want, this can be resolved by finding the offending feature class in the left hand tree, selecting it, scrolling down to find the field in the grid that is mentioned here, and if there is a value in the mapping, delete the value and leave the field, then go back into the field and re-enter the field name. This should resolve the mismatched mapping. |
Data in CMARCFLD and ??FIELDS does not match. This data will be synchronized to the desktop when changed in the geodatabase but not vise-versa. |
See note on previous warning. For this warning, the edits that are made in the desktop will not get reflected to the geodatabase, but edits made in ArcMap will get updated to the desktop. For some fields this is desirable, for example, you would not want users in the desktop changing the "Subtype" field in your geodatabase. |
The Primary Feature Class flag is turned off. This means that edits made directly in the desktop will not be reflected in this feature class. |
See setup for more information on primary feature classes. You can only have one per Module. This is just informing you that the one listed above this warning is not listed as your primary. If you want to change this feature class so that it is your primary, find the feature class in the left hand tree and select it, then check the "Primary Update Feature Class" checkbox in the header. |
If you want to maintain the intersection data in the desktop, you must define the To and From Node fields. |
This warning will only occur for feature classes defined as street segment feature classes. If you want the desktop to maintain intersections (intersections are important if you want to use our Accident product), then you must define to and from node fields for the street segment feature class. See setup for more information on this. |