Missing Data


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

Category: Missing Data

Missing data errors are a common issue in Synchronization. Understanding the missing data errors requires a knowledge of what data is being synchronized into the Model. This highly depends on the file format being synchronized. 

This data can be synchronized into the Model along with the main design file:

Table of Contents

Missing References

Error: Dgn_0214, DgnV8_0132

 Error message: "Reference attachment (.dgn) is missing from reference or master model .dgn"

Issue:
Reference attachments cannot be found in the defined location and can not be synchronized. As a result, the iTwin doesn't show all the input files (Master or References) in iModel Index or visibility tree in Desing Review. 

Cause:

Solution:

Image 1

Warning: DgnV8_0133

 Warning message: "Reference model <File_Name> is ignored because its display is turned off in the master model."

Setting the reference file's display off in the master file is a common practice in various software applications, especially in computer-aided design (CAD) and 3D modeling environments. This is often done to simplify the view, optimize performance and file size, and reduce visual distractions. The synchronization logs this information and provides it for any potential issues analysis in the synchronization report. 

Issue:
Reference files are missing in the iModel. 

Cause:
The reference file's display is turned off in the master model.

Solution:
Open the source file in the Power Platform application where the source file was created (MicroStation, OpenBuildings Designer, or other). Go to Home -> References. In the opened References dialog notice that some references do not have a checkbox selected in the Reference Display column. (Highlighted in green in the below image.) This means that the display is turned off. 

If you need these references to be synchronized to the iModel, update the display setting in the source file, save the changes, and reprocess them to the iModel.

If you do not want to process the disabled references to the iModel, please ignore this warning.  

Missing Materials

Materials in drawing files are the digital representations of real-world materials that can be assigned to objects within your models. For example, you can apply a wood material to a model of a table to make it look like it's made of wood. So materials can contain information about the texture, color, reflectivity, transparency, and other visual properties of a surface. They can be custom-made or delivered with material libraries. 

There can be multiple reasons why material information is not visible in iModel Viewer, for example, Design Review.  

One of the reasons is that iModel Connector continues to increase the support for additional materials. However due to current limitations, this new material information will not be processed into existing iModels, but they are with newly created iModels.

Please find more reasons why material information is not visible and how to solve this below. 

Warning: Revit_0002

 Warning message: "Missing image file: <File name>. Please place the texture file next to the source Revit file. If you run publishing locally, you may also install the recent Autodesk Material Library for standard textures.

Issue:
Visual fidelity issues in iModel such as missing textures in elements.   

Cause:
The design model has defined Autodesk materials, but materials files are not provided in a way that synchronization can access them.

Solution:


Missing Fonts

Non-default fonts using in iModels

While working with connectors a user might want to choose a non-default font for drawings but font iModel embedding is working differently between various integrations. This will help them to place fonts correctly, make that fonts would be embedded properly and avoid errors related to missing fonts. In this article, we will see where to place font files that they would be visible in iModels.


Fonts using in Connect Portal Files Share or iTwin Desktop Synchronizer documents synchronization

 Non default font file can be simply placed to the same directory as design file, and it will be embedded to the iModel.

 

Fonts using in Connect Portal and Bentley Infrastructure Cloud Portal ProjectWise documents synchronization  

When a non-default font file cannot be found in iModel, placing font file to the same directory as a design file or trying to Scan References in ProjectWise would not help.  Font file should be supplied via WorkSpace, it should be placed to directory, where used workspace variable MS_FONTPATH is pointing. Configuration variable MS_FONTPATH specifies a list of directories that are searched to locate fonts. Usually default font location is: C:\Program Files\Bentley\MicroStation CONNECT Edition\MicroStation\Default\Fonts. Configure variable by additionally inserting another location where non default font is placed, and connector will use that font for iModel.

You can access Configuration Variables dialog in MicroStation from the following:

Ribbon: File>Settings>Configuration>Configuration Variables



MicroStation CONNECT EDITION documentation about using fonts: https://docs.bentley.com/LiveContent/web/MicroStation%20Help-v19/en/GUID-EA4472D6-C3D4-F8CB-1D63-517F1E3B7575.html

Warning: Revit_0025, NWD_0012

 Warning message: "Missing font: <Font name>. Please place missing font file(s) next to the source Revit file."

Issue:
Visual fidelity issues in iModel such as wrong font, missing font characters, and incorrect font display size. 

Cause:
The synchronization environment contains only a limited amount of Windows default fonts, that can be used during synchronization to Model. In case a unique, non-standard Windows font is used, a default system font will be used instead. 

Solution:
All non-default Windows fonts need to be provided to Synchronization manually for those fonts to be used. If fonts are placed in the same location as the design file, they will be picked up by synchronization and the missing fonts messages will no longer be reported. Fonts can be copied from C:\Windows\Fonts.  

Error: Dgn_0000

 Error message: "Could not locate font Courier New. Please place the font file(s) in the same directory as the design file."

Issue:
Visual fidelity issues in iModel such as wrong font, missing font characters, and incorrect font display size. 

Cause:
The synchronization environment contains only a limited amount of Windows default fonts, that can be used during synchronization to Model. In case a unique, non-standard Windows font is used, a default system font will be used instead. 

Solution:
All non-default Windows fonts need to be provided to Synchronization manually in order for those fonts to be used. If fonts are placed in the same location as the design file, they will be picked up by synchronization and the missing fonts messages will no longer be reported. Fonts can be copied from C:\Windows\Fonts.  


Element

Warning: Dgn_0188

 Warning message: "X Element(s) are skipped as these elements are invisible."

Issue:
Elements are made as invisible in the main model, so the connector does not process these elements.

Cause:
Due to better performance some elements can be made invisible in the model and since the user has chosen to make this not visible in the model, the iModel connector does not import these into the iModel.

Solution:
If you are expecting to do not see the invisible elements in the iModel, then please ignore this warning message.

If you would like to make elements visible, you need to find those elements in the model and change the hidden property value.

How to check if there are hidden elements on a particular level:

Status bar:

In this example there are one level and total 8 elements. After comparing the status bar and Level Manager results we can see that 4 of them are not visible.

 

Line Style

Warning: DgnV8_0046

 Warning message: "Could not find definition for line style [<Name>]. Some elements may not display properly."

Issue:
The custom line style definition is missing from the resource (.rsc) file.

Cause:

This can happen if the required line style definition is not available in the resource file.

Solution:

Make sure all the line styles present in the resource file should have definition associated with it.

Point Cloud File

Warning: DgnV8_0068

 Warning message: "PointCloud file <FileName.pod> attachment is missing."

Issue:

The reality attachments like Point Clouds are not visible in iTwin Reality Data widget.

Cause:

Solution:

Missing Dependency

Info: Civil_0004

 Info message: "No alignment found for source corridor 'Alignment Name'"

Issue:
There is a missing alignment for the processed Corridor element. This results in Corridor components being processed as generic graphical components, not as Physical Civil Corridor elements.

Cause:

Solution:

Warning: Civil_0010

 Warning message: "Bridge with name 'Name' and ID number could not find its associated alignment. As a result, this bridge and its parts will be processed as generic graphics instead of physical bridge elements. This can affect what properties are available in the iModel and prevent other tools from working properly (such as clash detection). To fix this issue, please ensure that this root model references the model that contains the appropriate alignment(s) and that those alignments are visible."

Issue:

Missing alignment associated with the Bridge component. Hence the bridge components would be processed as generic graphical components, not as Physical Civil Bridge elements.

Cause:

Solution:

Open the file in the Bentley Civil application and identify if there are missing references. In the design application used for the master file creation, go to the References dialog and fix any attachments that are missing. Items that need to be fixed are indicated in red. Read more about attachment fixing in design applications. Reference Manager dialog can be launched using Ribbon: Modeling > Home > Primary > Attach Tools split buttoning MicroStation application.

Info: Civil_0003

 Info message: "No alignment found for 187 additional source corridor(s)." 

Issue:
Coming soon.  

Cause:
Coming soon

Solution:
Coming soon

Invalid Input Data

Error: Ifc_0027

 Error message: "Object does not have attribute Name" 

Issue:
Missing information for the attribute for an object in the imodel viewer. (e.g. In properties tab > IFC Attribute section, the attribute "Name" could be blank because it doesn't have any value from the IFC source file)

Cause:
The attribute for the object could not be identified in the IFC source file (Note: some attributes are optional).

Solution:
The missing information for the mentioned attribute in the IFC file can be updated in the design application that generated the IFC. Once the IFC file has been updated and generated from the design application, resynchronize the IFC file to the iModel.
NOTE: Some attributes are optional. Please refer to this documentation on optional and required attributes: https://ifc43-docs.standards.buildingsmart.org/IFC/RELEASE/IFC4x3/HTML/lexical/IfcObject.htm

Warning: Ifc_0034

 Warning message: "IfcSite.<Attribute Name> is not set in the IFC model. (where Attribute Name can be RefLatitude, RefLongitude, etc.)" 

Issue:
The IFCConnector failed to read the IfcSite Attribute Name mentioned in the error.

Cause:
The IfcSite Attribute Name mentioned in the error is not set in the source IFC model.

Solution:
This is an issue with the source application that generated the IFC model and needs to be corrected by the application that is generating this IFC model. Please refer to the buildingSMART documentation on IfcSite attributes.

Error: Ifc_0038

 Error message: "Missed name attribute for a property in property set ‘<PropertySet Name >’."

Issue:
The IFC Connector failed to read the property name mentioned in the property set.

Cause:
The mentioned property name is missing in the property set of the source IFC model.

Solution:
Since this is caused during the generation of the IFC model from the source application, please fix the missing property name in the source application to address this issue.

Missing Geometry

Info:Dwg_0103

 Info message: "No geometry created for entity [Name], ID=XX."

Issue:
Normally, a graphic object in a model is displayed unless the object is on a layer which is frozen, turned off, or the object is set to invisible by the source CAD application. When a connector sees a visible graphic object which is not on a frozen or turned off layer, it tries to get the displayed geometry. If it does not get the geometry for any reason, it logs an informational message about geometry not found from the object.  

Cause:
Causes to this message vary, with some legitimate and others potential errors. A block reference (aka an INSERT entity in AutoCAD) that contains no displayable child entity, a Civil 3D object that is not displayed in the model per its style display control, or a polyline that has insufficient points, etc. are examples that may be considered as legitimate because the same objects are not displayed in the source CAD application. A custom object whose object enabler is missing, yet has no bounding box, can also cause this message, albeit with a separate message Dwg_0209 which shows detailed information about the missing object enabler. This may or may not be a concern, and the message may help the user to make the right call. If an object is displayed in the source editor but not seen in the iTwin, it is potentially an error in the connector and this message serves for diagnostic purposes.

Solution:
As causes may vary from case-to-case solutions may also vary. If an object is not displayed in the source product, you can ignore the message. If an object is displayed in the source product but not in the iTwin, please report the issue tos Bentley support for further investigation.

Named Group

Info:DgnV8_0126

 Info message: "No BIS grouping created for v8 Named Group element (x) because the Named Group was not converted.."

Issue:
BIS grouping was not created for Named Group element. 

Cause:
Named Group element was not converted.

Solution:
When there is related issue to element (x), after resolving issue for that element Named Group should be created. – Please check Synchronization Report for other error that contains same element (x) issue, this might be root cause why Named Group was not converted.  Refer to root error on Communities, solve issue with provided solution, re-run synchronization and this error should be resolved.

About Base Infrastructure Schemas (BIS): https://www.itwinjs.org/bis/guide/intro/overview/