When an error occurs...
The "Applied Steps" in Query Editor will help you find the solution for an error. Go to each step and look the query. Delete the unnecessary step(s). You can rename each applied step for future reference.
Duplicate the table where the error occurs and delete unnecessary columns to test the error. Dealing with a smaller dateset will help with solving errors.
Un-checking the box for "Enable load" helps to speed up the refresh time for the new data preview.
Bidirectional Relationships
Rule of thumb: DO NOT use bidirectional relationships in the model.
- The relationship between a fact table and a dimension table is usually many to one. The direction should be from the dimension to the fact.
- Watch for null/blank values
Relationship troubleshooting guidance (from Microsoft site)
- SQLBI blog: bidirectional relationships and ambiguity in DAX
- Guys in a Cube video (around after 4 minutes)
Slicers
When slicers don't interact with each other, there is a way to make it work. Do NOT use bidirectional relationship to fix the issue.
- Create a simple measure in the fact table, such as COUNTROWS(table)
- Add the measure in the Filters pane with a condition, such as "is greater than or equal to 1." Lock and make it invisible, and then apply filter. Do the same to each slicer.
- Other Resources:
- SQLBI article: Syncing Slicers in Power BI
- Guy in a Cube video:
Table Relation
Attachments:
image2020-6-29_15-54-3.png (image/png)
image2020-6-29_16-5-54.png (image/png)
image2020-7-1_16-13-25.png (image/png)
image2020-7-1_16-17-38.png (image/png)
image2020-7-1_16-18-0.png (image/png)
image2020-9-8_9-54-32.png (image/png)
image2020-9-9_10-10-43.png (image/png)
image2020-9-9_10-12-22.png (image/png)
image2020-9-9_10-19-55.png (image/png)
image2020-9-9_10-21-17.png (image/png)
