Updating using the Synchronize against original selection/trace/query option

The Synchronize against original selection/trace/query option is the default option on the Update Diagram dialog box that opens when updating a diagram based on the Standard builder. It allows you to update the active schematic diagram content starting from the persistent trace parameters when the diagram has been generated from a core tracing result, from the GIS feature set used to initially generate this diagram, or by reexecuting all the custom queries that were used to initially generate this diagram:

• If diagram generation is based on a selection set following a selection operation in the map, any core tracing operation returned as a selection set, or any non-core trace result, the update operates from the GIS feature set used to initially generate this diagram.
• If diagram generation is based on a core trace result that was returned as a drawing in the map, the tracing operation parameters are stored in the schematic dataset. In that case, the tracing operation based on these stored parameters is reexecuted in memory, and the obtained tracing result is used for the diagram update.
• If diagram generation is entirely or partially based on custom queries, all the custom queries that were used to initially generate this diagram are reexecuted, and the obtained query result is used for the diagram update.

In all cases, the update process is performed as follows:

1. The schematic features contained in the diagram are loaded in memory.
2. The synchronization is done in memory as follows:
   • The schematic features initially contained in the diagram that are still associated with GIS features contained in the geodatabase, part of the new core tracing result, or associated with records returned by the custom queries are updated in memory; their attributes and initial geometry are refreshed, and their current geometry is reinitialized if the diagram was not saved.
   • New schematic features returned by the new core tracing result or associated with new records returned by the queries are created in memory.
   • All schematic features related to GIS features that have been deleted from the geodatabase are no longer part of the new core tracing result, are no longer returned by the queries, and are removed from the memory.
3. If schematic rules have been specified for the related diagram template, they are reexecuted.
4. If the Persist manually removed, reduced or reconnected features check box is checked, the removal, reduction, and reconnecting operations are reexecuted.
5. If there is a default schematic layout algorithm configured for the diagram template and the diagram has no saved layout, the algorithm is reexecuted, and the geometry for all the in-memory schematic features is updated accordingly.
6. All the schematic features in memory are saved in the schematic feature classes in the schematic dataset..
7. The active schematic diagram is then refreshed with the new schematic database content.

Hinweis:

When the update operates on schematic diagrams that are partially or entirely built from custom queries, the process explained above only impacts the schematic features built by queries configured to be launched during the diagram building—that is, queries with the Query on Generate/Update evaluation mode. The schematic features coming from schematic feature classes with custom queries configured to be launched at the diagram loading—that is, queries with the Query on Start Editing evaluation mode—are processed during an intermediate step just after executing the rules.

Vorsicht:

For diagrams initially generated from a non-core trace result—that is, an applicative trace result—no trace parameters can be maintained in the schematic database to reexecute the trace when updating. In those cases, the update can only operate from the GIS feature set used to initially generate this diagram.

Hinweis:

If a particular layout was saved for the active diagram before its update, schematic features that are already contained in the diagram before update keep their last saved position, while new schematic features introduced in the schematic diagram during the update are positioned this way:

• At their geographic coordinates if they come from GIS features organized into a geometric network
• At their initial coordinates if they were built by custom queries and such initial coordinates are configured
• At the (0,0) location if they were built by custom queries and no initial coordinates are specified

Vorsicht:

When features used to generate diagrams come from an ArcSDE database, don't misinterpret the words original selection/trace/query. Updating a diagram using the Synchronize against original selection/trace/query option doesn't necessarily operate from the version of the GIS features on which the diagram generation was based. When working with versioned data, you can at any time change the reference version of the diagram so that the next time it is updated, the update process operates on another version of the GIS data.

Learn more about changing the schematic diagram reference version