As OpenBuildings Designer datasets are updated with new versions, the Catalog schema (known as the DataGroup Schema in V8i) is modified to support new/changed features and content.
When files are migrated forward to a newer version of the application and datasets existing building elements in DGN file may be out of synchronization with the active dataset schema. An upgrade process is required to synchronize such files with the active dataset. This can also be required when custom Catalog content is created/modified or if additional IFC Property Sets are added to a project.
Another scenario is if models created with one regional dataset have to be used with another, say US to CN. The same synchronization would be required to ensure correct behaviour and display of building elements.
This solution only needs to be applied to DGN files that contain elements that carry DataGroup data, e.g. Walls, Slabs, Mechanical components, Spaces, etc., and standard MicroStation elements that have had DataGroup Instance Data attached to them.
In addition to these design files, the BB_FloorMaster.dgnlib for the project will need to be upgraded, the elements contained within this file that stored the floor and other reference plane properties must also be synchronised with the dataset schema.
Files that do not contain any DataGroup carrying elements do not contain anything that needs to be upgraded.
Typically this utility would be used after:
It is highly recommended that this utility and any other related processes are run after backups have been taken; either just after a regular scheduled backup or after an unscheduled backup of the specific files involved.
CONNECT Edition - File > Utilities > Data Utilities > Upgrade (Schema Upgrade Utility)
V8i - Utilities menu > Building Designer Utilities > DataGroup Upgrade Utility > Upgrade.
Important: note that if properties exist on existing elements that are no longer defined in the schema, running this utility permanently deletes those properties and their corresponding values from the elements. If you wish to keep those properties, you must map them to another remaining property with the DataGroup Transformation Utility, before running the DataGroup Upgrade Utility.
The utility is also available via key-in:
mdl load Bentley.Building.Datagroup.Upgrade; dg upgrade
These key-ins can be applied by a batch process with the additional command 'dg processfile'.
The command file to use would contain the lines:
mdl load Bentley.Building.DataGroup.Upgrade; dg upgrade
The following sequence should ideally be used when none of the referenced files are in use so all files can be processed. File that are not processed will be listed so can be upgraded individually or by a repeat run.
This will process all of the attached files. The time required for this to complete will vary according to project size and complexity. For larger projects it may be appropriate to work with sequential groups of files rather than attaching all files.