Here you will find an explanation and best practices for solving Business properties-related synchronization errors.  

Category: Business Properties

In design files, element attributes, also called Business properties,  provide important information about various elements within the design. These attributes are used to define and describe elements and use this information to calculate various other parameters, such as element amount.  

 

ECSchema related issues

Read more about ECschemas and their purpose.

Error: DgnV8_0164

 Error message: "Failed to convert [Could not read v8 ECSchema XML for FileName from c:\stagingdir\A.i.dgn (ElementId: 30)"

Issue:
The business data or element information is missing in the iModel Viewer.

Cause:

• Workspace schemas are missing.
• Workspace schemas are incorrectly embedded into the i.dgn (published or packaged files). 
• The workspace schema in the source file is incompatible with the schema in the iTwin.
• The workspace schema in the source file is a different version from what is already synchronized into the iModel. 

Solution:

• Open the source DGN file in the design application, for example, MicroStation. Check the Message Center in the design application, and review the errors to identify which schema is missing and should be embedded. You can also use the key-in "ecx schema list" for the schemas imported. Read more about workspace configuration for iTwins. 
• In case the schemas are coming from the workspace, please redefine the path of all the schemas so that the design application can embed them into the DGN/i.dgn. Define the MS_ECFRAMEWORK_SCHEMAS < $(_USTN_WORKSETDATA) Schemas/ in the workset Configuration file and place the required schemas in the workspace folder location.
• Once the schema issues are resolved, resynchronize the source file into iModel.  

Error: DgnV8_0158

 Error message: "Ignoring <SchemaName> on element <...> in file because the schema failed to de-serialize."

Issue:
There is an inconsistency in the schemas between the various attachments.

Cause:
When master file and attachment or reference file contains different versions of schemas' this inconsistency causes connector to ignore loading schema.

Solution:
Either change the reference file or master file to use the same schemas' version. 

In example master file contains IntegratedStructuralModel.X and OpenPlant_3D.Z which references that  IntegratedStructuralModel.X. And other attachment in the same iModel contains OpenPlant_3D.Z which references different version of IntegratedStructuralModel.Y. This inconsistensy causes the connector to fail to properly load OpenPlant_3D.

MicroStation documentation related to EC schemas: https://docs.bentley.com/LiveContent/web/PlantWise%20Help-v4/en/GUID-57326976-317C-44C7-A554-336A840EC5DD.html

More information about schemas: https://www.itwinjs.org/bis/guide/schema-evolution/schema-customization/

How to update Schema of a DGN file: https://bentleysystems.service-now.com/community?id=kb_article_view&sysparm_article=KB0111879

OpenPlant PID Schemas upgrading: https://bentleysystems.service-now.com/community?id=kb_article_view&sysparm_article=KB0101747

 

ECClass related issues

Error: EC_0001

 Error message: "Dropping base class [Class NAME] from [Item Type= Name: Name OF Parameter Set] because the base class is defined in a schema set to be pruned in the schema read context."

Issue:
Coming soon.

Cause:
Coming soon.

Solution:
Coming soon.

Element related issues

Error: Revit_0030

 Error message: "Element cannot be included into [Element 1 Name] to follow [Element 2 Name] relation as it's already part of another Model Group [Model Group Name].

Issue:
Relationship between a Revit element and its parent Model Group cannot be set.

Cause:
Revit Model groups are a Revit feature for designers to group repeating sets of elements, such groups are not preserved in iModels, so their relationships with their elements cannot be set.

Cause:
Due to improvements in the Revit connector, the next time this model is synchronized, the group element will be removed and this warning will no longer appear.

 

Display Labels

Issue:

Display labels are not updated in the iModel properties.

Cause:

When a source file schema is updated and then re-synchronized into the iModel, the iModel connector does its best to merge the incoming changes with the existing schema. However, Display Labels (whether for schemas, classes, properties, standard values, etc.) are not updated. 

Solution:

At the moment this issue can not be resolved by yourself. If you need to force the update of a display label, please contact Bentley Support. A flag can be set on your project that will allow updating of the display labels.