Inconsistent Data


Here you will find an explanation and best practices for solving Data inconsistency related synchronization errors.  

Category: Inconsistent Data

Inconsistent data refers to data that contains discrepancies or errors within a dataset. These inconsistencies can arise for various reasons and can make the data unreliable or difficult to work with.

Table of Contents

 

Duplicated data in an iModel

Duplicated data can be introduced in different scenarios and can cause duplicated data to appear in the iModel, which is not desired. 

 Error: Dgn_0199

 Error message: "Duplicate models found MasterSubject:<File name> MissingInputFile: <File path>.

Issue:
Visual fidelity issues in the model such as duplicated graphical information and properties. 

Cause:

Solution:
To avoid duplicate data processing into the iModel, please ensure that:

 

 Error: Dgn_0066, DgnV8_0142, DgnV8_0141

 Error message: File <File name> has <File path> as its documentId from the dgn file. However, the attachment data from the data source is <File ID>.

Issue:
Visual fidelity issues such as graphical and properties duplication.

Cause:
References ID had changed due to reference file migration to a different data source.

Solution:
Run a Scan References on the master file and then restart the synchronization. If the duplicate issues cannot be solved, please contact Bentley support to further diagnose this kind of error: https://bentleysystems.service-now.com/csp
Read more about why reference scanning is important. 

Error: Rvm_006

Warning message: Duplicate component name at line #n.

Issue:
The attribute file has multiple components with the same name. When this happens, the connector combines them together and values for repeated properties are updated as per the latest component set.

Cause:
The file may contain duplicate components, or there may have been an issue when exporting the .att file from the source application. 

Solution:
Rename the duplicate component in source software and then re-export and resynchronize.

 

Alert messages 

The purpose of an alert message is to convey important information. 

Error: Ifc_0020, Ifc_0021

 Error message: "An element in <File name> is re-using GlobalID <GUID>. The last seen element with this GlobalID will be present in the iModel."

Issue:

Visual fidelity issues in iModel such as missing element/s.

Cause:

Solution:

Error: Ifc_0048

 Error message: "Units of type MASSDENSITYUNIT not defined"

Issue:

Missing information in the IFC file MASS DENSITY UNIT in the iModel viewer.

Cause:
MASS DENSITY UNIT values were incorrectly exported to the IFC file from the design application and can not be converted to the iModel 

Solution:
Since IFC is an open standard for the exchange of building information models (BIM) data and not a design file format, it cannot be updated directly. Updating the units in the IFC file will typically require making the appropriate changes in the design application so that the MASS DENSITY UNIT will be updated the next time an IFC file is generated from the design application. Once the unit is correctly reflected in the IFC file, it can be resynchronized into the iModel.

Error: Rvm_007

 Error message: "Cannot process geometry for RVM Component: <ComponentName>"

Issue:

Connector failed to process geometry of the given component.

Cause:
Inconsistent geometry data for the component, for example a radius value of 0 for CYLINDER/CTORUS etc. 

Solution:
Verify the geometry data for the component in the source application. Once the geometry data is correctled, the source file can be resynchronized into the iModel.

 

Illegal Units

Warning: Revit_0032

 Error message:

<Property Name> property value <number> <unit symbol> of <unit name> dimension is ignored due to missing persistence units; perhaps the schema in the Revit model is damaged. Please contact Bentley support.

<Property Name> property value <number> <unit symbol> is ignored due to missing persistence units; perhaps the schema in the Revit model is damaged. Please contact Bentley support.

Issue:

The unit for a property can't be placed in the iModel.

Cause:

The property units are unknown in this case.

Solution:

Please contact Bentley support mentioning this warning and they will help analyze the problem and suggest a fix.

 

Geometry

Error: IfcFl_0003

 Error message: "Invalid IfcDirection <>, expected (minimal) dimension"

Issue:

An IfcDirection entity in the IFC model does not have the required number of components (for example, fewer than 3 components for 3D geometry). This makes the direction invalid and prevents correct geometry interpretation. 

Cause:

  • The authoring application exported an incomplete or invalid IfcDirection (e.g., only one or two components).
  • The IFC file has been corrupted or altered, causing the loss of direction components. 

Solution:

  1. Use the synchronization report to locate the specific IfcDirection entity referenced by #.
  2. In the source/authoring application, correct the geometry so that all IfcDirection entities have at least the required number of components (typically X, Y, Z).
  3. Re‑export the IFC file after correcting the geometry.
  4. Optionally, implement or use pre‑processing/QA scripts to validate and repair IfcDirection entities before synchronization.

Warning: IfcFl_0064

Warning message: "IFCPOLYLOOP contains identical points. Geometry may not be generated correctly."

Issue:

The IFC model contains one or more IFCPOLYLOOP entities where all (or multiple) loop points are identical. This produces a degenerate loop, so the connector may not be able to generate valid geometry (for example, a polygon requires at least three distinct points).

Cause:

  • The source application exported a polyloop where all vertices reference the same point.
  • Loops were created or modified incorrectly (for example, duplicate points left in the loop definition).

How to identify the affected element 

  1. Open the Synchronization Report and locate the entry for IfcFl_0064.
  2. The report entry will include the IFC entity ID of the affected IFCPOLYLOOP (for example, #12345).
  3. Open the IFC file (or use an IFC viewer) and search for that entity ID, for example:
    • #12345 = IFCPOLYLOOP(#22,#22,#22); In this example, all three loop vertices reference the same point #22, so the loop is invalid.  

Solution:

  1. In the authoring application, locate the corresponding geometry using the entity ID / element reference from the Synchronization Report.
  2. Correct the loop, so it has at least three distinct points, or remove/replace the invalid loop as appropriate.
  3. Re‑export the IFC file after fixing the geometry.
  4. Re‑run synchronization and verify that IfcFl_0064 no longer appears. 

 

Property Definition

Warning: Ifc_0029 

 Warning message: "Datatype mismatch found in property: <> from the current IFC file" 

Issue:

The connector detected that the same logical property is defined with different datatypes in the IFC file. This can cause inconsistency and potential data loss during mapping and synchronization.

Cause:

  • Different elements or contexts use different datatypes for the same property name within a property set (for example, string vs numeric). 
  • Misconfigured property sets, templates, or export settings in the authoring application. 

Solution:

  1. Read the error message to identify the affected property: 
    • Property set
    • Property
  2. In the source/authoring application, review how this property is defined and ensure it uses one consistent datatype for all occurrences.
  3. Correct any templates, catalogs, or libraries that define this property differently.
  4. Re‑export the IFC file once property definitions have been harmonized.
  5. If required, coordinate with the authoring application vendor or configuration owner to enforce consistent property typing. 

Warning: Ifc_0042

Warning message: "Multiple datatypes 'DataTypeName' are defined for property 'Property Name' in the property set 'Property Set Name' resulting in data loss. This inconsistency needs to be corrected by the source application for this property to be consistently synchronized."

Issue:

Data loss is observed for the element with the problematic property in the iModel (e.g. Property 'NEL_Diameter' shows an empty value in the properties section in the iModel).

Cause:

  • An element in the iModel has a problematic property that is inconsistently defined by different IFC datatypes in multiple property sets (e.g. property for one property set is defined as 'IfcText' and in other property sets it is defined as 'IfcReal') which resulted in data loss. The inconsistency causes this unpredictable behavior during synchronization.
  • The source application, configuration, or template defines or exports the same property with different datatypes across different elements or contexts.
  • Data modeling rules or templates are not aligned, so instances of the same property use inconsistent types.

Solution:

The inconsistency of datatypes for the problematic property should be fixed in the IFC File. Since IFC is an open standard for the exchange of building information models (BIM) data, it cannot be updated directly. The inconsistency in the IFC file should be corrected in the design application so that there will be no missing data for the property in the iModel. Once the IFC file has been corrected and generated from the design application, resynchronize the IFC file to the iModel. This should solve any issues with the missing data for the problematic property.

How to fix the IFC file: 

  • Identify the affected property from the error message:
    • Property set
    • Property
  • In the authoring application, standardize this property to use one consistent datatype for all elements (typically a numeric type for measurable values such as Diameter).
  • Review the entire property set for other properties with multiple datatypes and correct them as needed.
  • Re‑export the IFC file after harmonizing the property definitions.
  • Contact Bentley Support for assistance if these issues cannot be solved.