The SchematicExportAttribute Field Model Name
You can assign the SchematicExportAttribute field model name to fields you want to include in the schematic diagrams. For example, in the sample data the Name field on the fiber optic cable feature class already has this model name. This means when you run any of the schematics, Name is included in the output as shown in the following image:
If you also wanted to include the CableManufacturer field, for example, you would assign it this field model name as shown in the following image:
And, the next time you run a Circuit Schematic, for example, CableManufacturer appears in the output:
Adding the field model name is straightforward, but there are a few important considerations:
-
Adding the model name does not retroactively populate existing schematic diagrams. Only new diagrams generated after the model name include the field.
-
Adding the field model name to a new field is all that is required to update subsequent Circuit and Splice Schematics. In other words, after adding the model name, the next schematic generated includes the field.
-
With the new field visible in subsequent schematics, you can include it in your symbology or labeling for diagrams. Remember to export and import the symbology to keep these changes as described in the help topic Define Default Symbology.
-
To create the field name displayed in the diagram, the field model name combines the feature or object alias with the field alias separated by an underscore, as seen in the following image:
IMPORTANT:-
If you change the alias after the field model name has already been assigned, the schematic diagram lists the field twice: once with the old name and once with the new. Further, the old name appears with a null value and the new name receives the actual contents of the field. For example, above in this help topic, CableManufacturer received the field model name. If you later changed the alias to simply “Manufacturer,” the resulting schematic would look like the following image:
And, if you continue to change the alias, the application continues to add the field. All the old names remain null, and the most recent name receives the field contents. In other words, if you went through four iterations of aliases, the resulting diagram would look like the following image:
-
Deleting the extra fields from the schematic dataset does not change this behavior. Even if you delete them from the dataset, they appear in subsequent diagrams.
-
The only way to “clean up” these extra fields is to delete the entire strand from the dataset using the Schematic Dataset Editor in ArcCatalog. But, this deletes the strand from all existing diagrams too. This might not matter during an implementation stage, but you likely do not want to alter existing diagrams in a production environment. If you do choose to delete the entire strand, it is regenerated automatically (cleaned up, without the superfluous fields) upon generating the next diagram. You do not need to manually add it back in after the deletion in the Schematic Dataset Editor.
-
-
For all these reasons, we recommend you and your company agree on an alias first, then assign the field model name.
-
Schematics cannot accept special characters in the alias. If you use special characters, the field name appears null in the diagram.
-
You can use spaces in the alias, but they are replaced with underscores in the diagram.
-
Schematics can accept up to and including 19 characters in the alias.
-
-
If data are not displaying in the schematic diagrams, check their Storage and Evaluation Modes in the Schematic Dataset Editor.