Feature Class Fields Grid

The feature class fields grid is designed to link the feature class fields to fields in Lucity, or to set default values to a field. A mapping enables the Lucity application to update the feature class when the data is updated in the Lucity desktop or web application. A mapping also enables the Lucity extension in ArcMap to update the Lucity database when the data is updated in the feature class during an ArcMap edit session.

Note: GIS Fields that link to a Lucity Picklist field can only link to the Code portion of the Lucity Picklist field.

Decide which feature class field should be linked.
Look at the Lucity module and decide what fields you want to link to your GIS data. You can get the field's caption or CTRL + Right -click to view the field properties to obtain the field's name.
In the geodatabase configuration, select the feature class you are linking to Lucity.
In the grid on the right, find the Lucity field, using its field name or display name.
Map the field by:
1. Clicking the Field Lookup button for a list of fields from the associated feature class.
  - The following pop-up will appear:
  - Click Only show fields with compatible data type to filter out fields that aren't the same type as the field you are mapping to.
  - Click Only show unmapped fields to filter out fields that aren't already currently mapped to.
  - Select a field and click OK.
2. Or Type the geodatabase field name in the Feature Class Field Name field.
The Import Field and Export Field checkboxes are automatically checked.
- Uncheck the Import Field if you do not want data in the Geodatabase field to be imported to Lucity field.
- Uncheck the Export field if you do not want data in the Lucity field to be exported to the Geodatabase field.

You can set a field to a default value instead of mapping it to the feature class. This will set the field in Lucity to that value for every record synced. This happens every time the record is synced and will overwrite existing values in the field.

Click in the field you want to set a default value.
Type = and then the value you want
- Examples:
  =6
  
  =Red
Click out of the field to save the edits.
Note: The value you use must match the type of field you are trying to push it into (text into a text field).


Column Purposes
FieldName:	The field name in the Lucity table.
DisplayName:	The field caption in Lucity.
Field Type:	The type of data stored in the field.
MaxMask:	The data format. A numeric value followed by an "x" indicates the number of characters allowed. n indicates a numerical digit.
Feature Class Field Name:	This is the name of the field in the feature class. This is NOT the alias field name.
Field Lookup:	This button column displays a list of the feature class fields. Note: If a connection to the geodatabase was unsuccessful then no fields will be listed.
Import Field	Allows the data in the Geodatabase field to be synced into Lucity.
Export Field	Allows the data in the Lucty field to be synced into the Geodatabase.
Lookup Lucity ID	This column only works for feature classes linked to Lucity Inspection modules and only appears next to the field that links to a Record #. The feature class must have contain an ID for the Lucity Asset the inspection is for. If the ID stored in the feature class is the asset's Rec # link that field to the Rec # field and leave this box unchecked. If the ID stored in the feature class is the the asset's common ID then link the field to the common ID and check the Lookup Lucity ID field next to the Rec #. This is done because in this case Lucity needs to know the record number. This looks up the record number based on the common id.
Color Coding	Red - Required field Orange - Stores the required ID numbers of related features. Yellow - Stores the optional ID numbers of related features. Green - Composite address field. Pink - Strongly recommended field. Typically this is the Lucity auto ID field. Although, technically this field isn’t required it is strongly recommended that the feature class contain a field that stores the Lucity autoID. Not having this field will impact the performance of some of the Lucity GIS tools as additional resources will be used to determine the AutoID value based upon the common ID.