Synchronize Drainage Data

Synchronize Drainage Prototypes and Support Elements from a Source File to a File, or a Folder of Files.

Functionality of the Synchronize Drainage Data is as follows.

Select a source file typically a Dgnlib but could be any design file that has a Drainage and Utilities project.
Select the “Default” as a model name.
The Support elements (e.g. catalogs, storm data, etc.) and Prototypes that in the source file are shown in the dialog.
Note: Only the elements that exist in the source file are shown. For example, if you don’t have a gutter catalog, it will not be shown in the dialog.
Select the Destination File or Folder containing multiple files.
Select Synchronize Button to Update the Content.
A log file is written; you can review to see details of what is synchronized.
Note: Only Drainage Data is updated- Utilities data does not use prototypes or support elements.

Synchronize Behaviour

Changes to a prototype are not automatically applied to existing elements (e.g. nodes and links) in the destination
Changes to a prototype are applied when new elements are created, or when the feature definition of an existing element is changed
Changes to support elements (catalogs and storm data) will affect the destination either when a Compute is performed, or when a new element is placed that uses a catalog (for example if a size in a conduit class is removed)

If "Synchronize Drainage Data" is run backstage (so a Civil product is running), then the active design file cannot be updated, because it's already open and the data within it is therefore locked.

The command can be run without a Civil product running, so that the destination design file is not open, and can be synchronized.

To run command without a Civil product running, double click Haestad.DataSynchronizer.App.exe, from the Civil installation\Subsurface folder (e.g. C:\Program Files\Bentley\OpenRoads Designe2023.00\OpenRoadsDesigner\Subsurface).

Alternatively, if a Civil product is running, then create a new design file, so that neither the source or destination files are open. If ProjectWise integration is needed, then you need to use the OpenFlow’s functionality for this.

This involves editing the ProjectWiseIntegrationLocalOptions.xml file, located in Program Data - for example C:\ProgramData\Bentley\SUDA\23.0. Be aware that this path changes, depending on the version of the Civil product being used. The xml file contains instructions for the changes that need to be made. Note that Civil products are 64-bit.