The example above shows four feature class fields (NTG_LENGTH, NTG_LINE_CD, NTG_LOC_TY, NTG_MAT_CD) linked to the Sewer Pipe Inventory Module.
The geodatabase field NTG_LENGTH is being mapped to the Lucity field NT_LENGTH.
The geodatabase field NTG_LINE_CD is being mapped to the Lucity field NT_LINE_CD. Since NTG_LINE_CD is a numeric field in the geodatabase, it is being mapped to the numeric Code/Type field, NT_LINE_CD. Therefore, NT_LINE_TY is listed in the Linked Code/Type Field Name column for the NT_LINE_CD record, so both Lucity fields will be synchronized.
The geodatabase field NTG_LOC_TY is being mapped to the Lucity field, NT_LOC_TY. Since NTG_LOC_TY is a text field in the geodatabase, it is being mapped to the text Code/Type field, NT_LOC_TY. Therefore, in order for the numeric Code/Type field to be populated, NT_LOC_CD is listed in the Linked Code/Type Field Name column for the NT_LOC_TY record.
If you are using a field with a domain in the geodatabase, remember that we are synchronizing the values in the database, not the description of the domain. For example, the domain defined below (LifecycleStatus) is a coded value domain that is applied to a text field for users to select a status. In ArcMap, when the user is given the option to select from 'Active','Abandoned','Removed'. When the user selects 'Active', the value 'Existing' is stored in their geodatabase. This is the value that is synched to the desktop, so you would need to have 'Existing' in your picklist for the field that corresponds to this field in the desktop, not 'Active'.
