Error |
Resolution |
Missing Required Common Identifier Field # 1 |
The feature class that this error is listed under does not properly have the Common Identifier Field #1 listed. See the setup for more details. |
Missing Required Common Identifier Field # 2 |
The feature class that this error is listed under does not properly have the Common Identifier Field #2 listed. See the setup for more details. This error will only be displayed if Common Identifier #2 is a required field for this feature type. |
The Common #1 Field Must Be Defined in the Field Grid as well as the Header |
There is an error in your setup, currently the Common #1 field is listed properly in the header information for the feature class, but is not listed in the field grid. Find the field (should be colored green in the grid), and fill in the proper feature class field name for that field. |
The Common #2 Field must be defined in the field grid as well as the header. |
There is an error in your setup, currently the Common #2 field is listed properly in the header information for the feature class, but is not listed in the field grid. Find the field (should be colored green in the grid), and fill in the proper feature class field name for that field. |
Missing Required Unique Link to Lucity Field |
The Lucity AutoID link field in your feature class has not been mapped to the Lucity AutoID field in the field grid. Select the offending feature class from the left hand tree, and in the bottom grid, find the Auto ID field (it will be one of the green fields), and enter the field name that corresponds to this field in your geodatabase feature class. |
Missing Required In Lucity Flag Field |
You must define a short integer field that will store the status of whether or not the feature is in Lucity. This field is defined in the header of the feature class. Select the offending feature class from the left hand tree, and enter the field name that will contain this value from your geodatabase in the "In Lucity Flag Field" in the header. |
Missing Feature Class Parent Common ID Link Field(s) for a Park feature class that requires this data |
Certain feature classes require some parent field information, find the offending feature class in the left hand tree and select it. In the header information is a field called Lucity Parent Common ID Field. It is possible that more than one field will be listed (separated by commas), you must enter fields in the Feature Class Parent Common ID Link Field on this header that correspond to these fields. So if one field is listed, you need to list one field, if two, then you need to list two fields. This information is used to properly link a child record to its parent feature. See the setup for more information on this topic. |
Missing Feature Class Parent Link Field(s) for a Park feature class that requires this data |
Certain feature classes require some parent field information, find the offending feature class in the left hand tree and select it. In the header information is a field called Lucity Parent ID Field. It is possible that more than one field will be listed (separated by commas), you must enter fields in the Feature Class Parent Link Field on this header that correspond to these fields. So if one field is listed, you need to list one field, if two, then you need to list two fields. This information is used to properly link a child record to its parent feature. See the setup for more information on this topic. |
Feature Class Parent Link Field has been defined but Feature Class Common ID Link Field is missing, both or neither should be defined. |
If you want to define a parent relationship for this feature, you must define fields for both the Parent Link field and the Parent Common ID Link Field. You have not defined one of these fields. You cannot define one field without defining the other field, they work directly in consort with one another. Either remove the value from the Feature Class Parent Link Field, or add a new mapping for the Feature Class Common ID Link Field. |
Feature Class Parent Common ID Link Field has been defined but Feature Class Link Field is missing, both or neither should be defined. |
If you want to define a parent relationship for this feature, you must define fields for both the Parent Link field and the Parent Common ID Link Field. You have not defined one of these fields. You cannot define one field without defining the other field, they work directly in consort with one another. |
The To and From Node fields (logical network) are required for this feature class. |
If you have not added a to and from node character field (most likely UpstreamStructure/DownstreamStructure) to your feature class, you need to add this field, and include it in the synchronizer mapping. If you have already added these fields to your feature class, and have already defined them in your grid, you have probably forgotten to define the fields in the "Feature Class From Node Field" or "Feature Class To Node Field". These fields need to be the fields that contain the UpstreamStructure and DownstreamStructure, respectively from your feature class. These fields are also used for street segments, in which case these fields store the FromNode and ToNode of the street segment. These fields are not required for street segments. |
Field [Field Name] is missing the corresponding Lucity field name. |
There is an error in the setup. You need to open the CMARCFLD table in your GBAComm database and search for a record where the GF_GBA_FN is blank. Blank values for the GF_GBA_FN are only allowed if the GF_ARC_FN is "i" and if the feature class is connected to a Storm Conduit or Sewer Pipe module in the desktop. This special "i" field is a storage place for the unique index on parallel pipes. Do not delete the special "i" records. Only delete records where there is not an "i" in the GF_ARC_FN field and the GF_GBA_FN is blank. |