Forum Discussion
(Blank) in slicer
- 1 year ago
Please see this article on blank row and limited relationships
"The blank row is created for regular relationships that are invalid – that is, when there is at least one row on the many-side that does not have a matching row on the one-side of the regular relationship"
In directlake or direct query since the data is remote it has to assume a limited relationship. To remove the blank row select the assume referential integrity button when creating the realtionship. If this selected but there isn't RI, you will see differences between sub totals and totals.
Please see this article on blank row and limited relationships
"The blank row is created for regular relationships that are invalid – that is, when there is at least one row on the many-side that does not have a matching row on the one-side of the regular relationship"
In directlake or direct query since the data is remote it has to assume a limited relationship. To remove the blank row select the assume referential integrity button when creating the realtionship. If this selected but there isn't RI, you will see differences between sub totals and totals.
"The blank row is created for regular relationships that are invalid – that is, when there is at least one row on the many-side that does not have a matching row on the one-side of the regular relationship"
Hi, thanks for your answer, but as I said the fact table and the date table have the exact row-values. There are no null values or other values.
So the only possible explanation is that my model is in direct lake mode and pbi assumes that there could be invalid values/invalied relations?
- Deku1 year ago
Super User
Yes, this what I have said. Press the referential integrity button when creating the relationship to confirm no duplicates or blanks