The issue happens because the Power BI data model maps relationship tables incorrectly or lacks unique entity keys.Why the Double Entry OccursMany-to-Many Relationship Issues: The structural element is mapped to a generic IfcType or Tag (BS03) instead of its unique instance ID.Lack of Unique Instance Binding: Power BI matches the Tag prefix "BS03" to all instances sharing that prefix (BS03.548 and BS03.572) because the relationship is evaluated at the type level rather than the individual instance level.Missing Bridge Table: A direct link between a type table and an instance table creates duplicate rows in your visuals.
How to Fix ItVerify the Key Column: Ensure your Power BI relationship links the GlobalID or a specific instance GUID, not the generic Tag or Name.Implement a Bridge Table: Create a distinct mapping table containing unique combinations of GlobalID and the specific sub-tag if your source data splits them.Filter by GlobalID: Add the GlobalID field (2bMGnb...) into your Power BI visual or table filters to force the report to display data for only one specific element.
don't forget to click the Accept Solution button
