Here you will find an explanation and best practices for solving issues around filtering in synchronization.
Category: Filtering
Warning message: No physical components were detected in the source file. Perhaps the source file contains only references to other files, or its 3D views don't show any components.
Issue:
No physical element were converted.
Cause:
No physical 3D elements found in the file
Solution:
To resolve the issue, open the Revit file in a supported version of Autodesk Revit (Supported File Formats - KB0098377) and verify that it contains physical elements such as walls, floors, or structural components. Next, ensure that at least one 3D view is defined within the project. This 3D view must include visible physical elements rather than being empty or limited to annotations. If no 3D view exists, create a new one or modify an existing view to display the relevant geometry. This ensures that the connector can properly recognize and process the physical elements in the model.
Info message: <count> drawing(s) of <total> were ignored as they're not used in <total> sheets. The "2D sheet processing" option is set to none. If you wish to have the sheets synchronized, turn on the all options for "2D sheet processing" in the connection for this model.
Issue:
One or more 2D views were not synchronized.
Cause:
When the option "2D sheet processing" in the connection is enabled, only 2D views in any sheets are converted. The rest are excluded.
Solution:
Set the option "2D sheet processing" to all in the connection info to convert all 2D Views and re-synchronize the model.
Info message: Unmapped <model> in <file> not owned by <connector>
Issue:
During a multi-connector synchronization, the connector reports that it discovered a model belonging to another connector while walking the reference-attachment tree, and it is un-mapping (removing) the empty placeholder it temporarily created for it.
Cause:
In workflows where more than one connector (or more than one masterfile/job) contributes to the same iModel, every source file/model is assigned to exactly one owning channel. As a connector traverses the reference attachments, it can reach files that are not assigned to it and, as a side-effect of that traversal, create empty models for them before it realizes they belong to another job. In these situations, the connector reverses that side-effect by delteting the empty, non-owned model so it is not left as a duplicate in this connector's channel. DgnV8_0131 records each such cleanup. It is expected/normal behaviour in multi-connector or shared-reference scenarios (for example, a Default design model referenced by a sheet job but owned by a different connector).
Solution:
No action is required — this is informational and indicates correct filtering. The affected model will be (or has been) converted by the connector that owns its file.
If the model appears to be missing from the iModel when you expected it: