Tables

In the Tables portion of the schema, you map Designer XI fields to their equivalent fields in the geodatabase. For GN implementations, you can map the fields for all subtypes of a feature class, or you can create multiple table mappings to separate out certain subtypes. Further, you can decide whether the actual attributes in the fields are imported into the design, pushed back to the GIS when the design is complete, or both actions. Finally, this same area allows you to manage the relationships that might exist between a feature class and an object table.

For UN implementations, similar relationships can be accomplished by mapping Asset Groups and Asset Types.

IMPORTANT: Related object tables must include the GIS field that stores the foreign key of its parent feature class (this field is established when the relationship ior s originally created in the GIS). This field keeps track of which object table row is related to which GIS feature. The field that stores the foreign key is used when Designer XI queries attributes for dynamic spec assignment, or “specs on the fly.” See GIS Resources for more information about dynamic spec assignment.