Relationship troubleshooting guidance
This article targets you as a data modeler working with Power BI Desktop. It provides guidance on how to troubleshoot specific issues that you might encounter when developing models and reports.
Note
An introduction to model relationships is not covered in this article. If you're not completely familiar with relationships, their properties or how to configure them, we recommend that you first read the Model relationships in Power BI Desktop article.
It's also important that you have an understanding of star schema design. For more information, see Understand star schema and the importance for Power BI.
Troubleshooting
When a report visual is set up to use fields from two (or more) tables, and it doesn't present the correct result (or any result), it's possible that the issue is related to model relationships.
In this case, here's a general troubleshooting checklist to follow. You can progressively work through the checklist until you identify the issue(s).
- Switch the visual to a table or matrix, or open the See Data pane—it's easier to troubleshoot issues when you can see the query result.
- If there's an empty query result, switch to Data view—verify that tables have been loaded with rows of data.
- Switch to Model view—it's easy to see the relationships and quickly determine their properties.
- Verify that relationships exist between the tables.
- Verify that cardinality properties are correctly set—they could be incorrect if a "many"-side column presently contains unique values, and it has been incorrectly set as a "one" side.
- Verify that the relationships are active (solid line).
- Verify that the filter directions support propagation (interpret arrow heads).
- Verify that the correct columns are related—either select the relationship, or hover the cursor over it to reveal the related columns.
- Verify that the related column data types are the same, or at least compatible—it's possible to relate a text column to a whole number column, but filters won't find any matches to propagate filters.
- Switch to Data view, and verify that matching values can be found in related columns.
Troubleshooting guide
Here's a list of issues and their possible reasons.
| Issue | Possible reason(s) |
|---|---|
| The visual displays no result | • The model is yet to be loaded with data. • No data exists within the filter context. • Row-level security (RLS) is enforced. • Relationships aren't propagating between tables—follow checklist above. • RLS is enforced, but a bi-directional relationship isn't enabled to propagate—see Row-level security (RLS) with Power BI Desktop. |
| The visual displays the same value for each grouping | • Relationships don't exist. • Relationships aren't propagating between tables—follow checklist above. |
| The visual displays results, but they aren't correct | • Visual is incorrectly set up. • Measure calculation logic is incorrect. • Model data needs to be refreshed. • Source data is incorrect. • Relationship columns are incorrectly related (for example, ProductID column maps to CustomerID). • It's a relationship between two DirectQuery tables, and the "one"-side column of a relationship contains duplicate values. |
| BLANK groupings or slicer/filter items appear, and the source columns don't contain BLANKs | • It's a regular relationship, and "many"-side column contain values not stored in the "one"-side column—see Model relationships in Power BI Desktop (Regular relationships). • It's a regular one-to-one relationship, and related columns contain BLANKs—see Model relationships in Power BI Desktop (Regular relationships). • An inactive relationship "many"-side column stores BLANKs, or has values not stored on the "one" side. |
| The visual is missing data | • Incorrect/unexpected filters are applied. • RLS is enforced. • It's a limited relationship, and there are BLANKs in related columns, or data integrity issues—see Model relationships in Power BI Desktop (limited relationships). • It's a relationship between two DirectQuery tables, the relationship is set to assume referential integrity, but there are data integrity issues (mismatched values in related columns). |
| RLS isn't correctly enforced | • Relationships aren't propagating between tables—follow checklist above. • RLS is enforced, but a bi-directional relationship isn't enabled to propagate—see Row-level security (RLS) with Power BI Desktop. |
Related content
For more information related to this article, check out the following resources: