At a given time, the schematic features contained in a schematic diagram may not be up-to-date with the current state of the input data that was initially used to generate the diagram. This happens in these circumstances:
- The associated input elements (that is, the associated GIS features/objects, XML elements, network elements, and so on) no longer exist.
- Some attribute values on the original input elements have changed.
- Some new input elements are now detected as initial data—that is, the results of the initial trace, network analysis, custom query, select by attribute operations, and so forth, that have been used as the initial input data just before diagram generation now return some new elements.
The following sections detail how these changes can be reflected in the diagram content when updating depending on the builder on which the diagram is based.
Standard builder diagram updates
A schematic diagram template based on the Standard builder can be configured to work with different input data:
- GIS features organized a geometric network or network dataset when such features are highlighted in a map document after a selection or geometric network trace operation
- Custom queries configured on all its associated schematic feature classes that determine the content
When the diagram content is based on GIS features organized into a geometric network or network dataset
In this case, schematic diagrams are generated from network features highlighted in the map after selection or geometric network trace operations. When any diagram is generated, Schematics builds the schematic features associated with those highlighted network features and puts them into schematic feature classes in the schematic dataset before the diagram is displayed. Then, each time the diagram is reopened, schematic features are directly queried from the schematic dataset's feature classes, not from the network feature classes. If changes were made to the GIS data, such as feature state changes or feature removals, they are not automatically reported in the schematic dataset, and your schematic diagram content may be inconsistent with the GIS dataset content.
An update of the schematic diagram can then be launched so the schematic dataset is synchronized according to the GIS data and the changes on GIS network features are reflected in the diagram.
The table below shows which kind of changes will be reflected in the updated diagram depending on the update option you choose:
Type of changes on the initial GIS features | Synchronize against original selection/trace/query | Refresh attributes | Append new features to the active diagram | Overwrite the active diagram |
---|---|---|---|---|
Removed GIS features are reflected in the updated diagram. | Yes | No |
| Yes (See note 4 below.) |
New GIS features are included in the updated diagram. |
| No | Yes | Yes (See note 4 below.) |
Changes on GIS feature attributes are reflected in the updated diagram. | Yes See also note 3 below. | Yes See also note 3 below. |
See also note 3 below | Yes (See note 4 below.) See also note 3 below. |
During diagram updating, Schematics not only reflects the changes that could have impacted the GIS network features associated with the schematic features contained in the diagram; some other specific operations—for example, schematic rules execution—can also be reexecuted during the update process. The table below shows which kind of operation is systematically reexecuted during diagram updating according to the chosen update option:
During the Schematics update process | Synchronize against original selection/trace/query | Refresh attributes | Append new features to the active diagram | Overwrite the active diagram |
---|---|---|---|---|
If trace parameters persist in the schematic database, the trace is automatically reexecuted during updating. | Yes | No | No | No |
Rules are reexecuted during the update. | Yes | No | Yes | Yes |
Specific editing operations, such as schematic feature removals, reductions, and schematic link reconnections, persist in the updated diagram. | Yes or No (It's an option.) | Yes or No (It's an option.) | Yes or No (It's an option.) | Yes or No (It's an option.) |
When the diagram's whole content comes from custom queries
In this case, schematic diagrams are generated from a set of configured queries that returns a set of records from database tables. When any diagram is generated, Schematics builds the schematic features associated with the set of records expected in the diagram and puts them in schematic feature classes in the schematic dataset before the diagram is displayed.
When the diagram is reopened, the schematic features are usually queried from the schematic dataset's feature classes, not from the real database tables. This means that if changes have impacted the real database content, they are not automatically reflected in the schematic feature classes or in the diagrams. To reflect those changes, the schematic diagram needs to be updated.
The table below shows which kind of changes will be reflected in the updated diagram depending on the update option you choose:
Type of changes on the record set returned by the custom queries | Synchronize against original selection/trace/query | Refresh attributes |
---|---|---|
Removed features/objects are reflected in the updated diagram. | Yes | No |
New features/objects are included in the updated diagram. | Yes | No |
Changes on feature/object attributes are reflected in the updated diagram. | Yes | Yes |
During diagram updating, other specific operations, such as schematic rules execution, can also be reexecuted during the update process. The table below shows which kind of operation is also reexecuted during diagram updating:
During the Schematics update process | Synchronize against original selection/trace/query | Refresh attributes |
---|---|---|
Rules are reexecuted during updating. | Yes (See caution below.) | No |
Specific editing operations, such as schematic feature removals, reductions, and schematic link reconnections, persist in the updated diagram. | Yes or No (It's an option.) | Yes or No (It's an option.) |
Network Dataset builder diagram updates
When using the Network Dataset builder, schematic diagrams are generated from solved network analysis layers. When any diagram is generated, Schematics builds the schematic features associated with the in-memory features that compose this network analysis layer and puts them into schematic feature classes in the schematic dataset before the diagram is displayed. Then, each time the diagram is reopened, schematic features are directly queried from the schematic dataset's feature classes. If changes were made in the network dataset that cause the solved network analysis layer to be different, the changes are not automatically reported in the schematic dataset. In that case, you might want to update your schematic diagram content to reflect these changes. Before updating the diagram, you need to resolve the network analysis layer.
The table below shows which kinds of changes are reflected in the updated diagram:
Type of changes on the in-memory features that compose the network analysis layer | Update |
---|---|
Removed network elements are reflected in the updated diagram. | Yes |
New network elements are included in the updated diagram. | Yes |
Changes on network element attributes are reflected in the updated diagram. | Yes |
During diagram updating, Schematics not only reflects the changes that could have impacted the network elements associated with the schematic features contained in the diagram; some other specific operations—for example, schematic rules execution—can also be reexecuted during the update process. The table below shows which kind of operation is systematically reexecuted during diagram updating according to the chosen update option:
During the Schematics update process | Update |
---|---|
Rules are reexecuted during the update. | Yes |
Specific editing operations, such as schematic feature removals, reductions, and schematic link reconnections, persist in the updated diagram. | Yes or No (It's an option.) |
XML builder diagram updates
When using the XML builder, schematic diagrams are generated from input XML data. When any diagram is generated, Schematics builds the schematic features associated with the XML elements in input and puts them into schematic feature classes in the schematic dataset before the diagram is displayed. Then, each time the diagram is reopened, schematic features are directly queried from the schematic dataset's feature classes. Changes in the input data are not automatically reported in the schematic dataset. To reflect those changes, you need to update your schematic diagram content.
The table below shows which kinds of changes are reflected in the updated diagram:
Type of changes on the initial XML elements | Update |
---|---|
Removed XML elements are reflected in the updated diagram. | Yes |
New XML elements are included in the updated diagram. | Yes |
Changes on XML elements attributes are reflected in the updated diagram. | Yes |
During diagram updating, Schematics not only reflects the changes that could have impacted the XML elements associated with the schematic features contained in the diagram, but other specific operations—for example, schematic rules execution—can also be reexecuted during the update process. The table below shows which kind of operation is systematically reexecuted during diagram updating according to the chosen update option:
During the Schematics update process | Update |
---|---|
Rules are reexecuted during the update. | Yes |
Specific editing operations, such as schematic feature removals, reductions, and schematic link reconnections, persist in the updated diagram. | Yes or No (It's an option.) |