Power BI is turning 10, and we’re marking the occasion with a special community challenge. Use your creativity to tell a story, uncover trends, or highlight something unexpected.
Get startedJoin us for an expert-led overview of the tools and concepts you'll need to become a Certified Power BI Data Analyst and pass exam PL-300. Register now.
Hi,
I have an strange behaviour which I dont unterstand, I also searched for the problem and watched a few videos but I cant find a solution.
I have two tables (I already reduced data due to find the problem)
- ticketitems
- datetable
tickeitems has two columns: PKEY and StartDate
datetable has a few 'normal' columns for a date dimension
So this is a distinct select to my ticketitems table
As you can see, there are a few dates.
I also limited my datetable to contain only the date of taxticketitem
So in my model I created a one-to-many relationship between them
But now, if I create an visual or slicer of the date column of my date table I see the (blank)-Row
If I delete the relationship the (blank) is gone.
Additional info:
- the semantic model is in direct lake mode on an fabric warehouse
- both columns are created as DATE-columns
- As you can see, there are no null values in the tables and they have the same data
Solved! Go to Solution.
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.
Hi @tkiwi,
Thanks for reaching out MS Fabric community support.
@Deku thanks for your prompt response. please select below check box to disable blanks.
Thanks,
Prashanth
MS Fabric community support
If this post helps, then please consider Accept it as the solution to help the other members find it more quickly and give Kudos if helped you resolve your query
Thanks but as @Deku said, this is not an option (for me) because
" If this selected but there isn't RI, you will see differences between sub totals and totals."
May I ask if you have gotten this issue resolved?
HI @tkiwi ,
we would like to follow up to see if the solution provided by the super user resolved your issue. Please let us know if you need any further assistance.
If our super user response resolved your issue, please mark it as "Accept as solution" and click "Yes" if you found it helpful.
Regards,
B Manikanteswara Reddy
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?
Yes, this what I have said. Press the referential integrity button when creating the relationship to confirm no duplicates or blanks
This is your chance to engage directly with the engineering team behind Fabric and Power BI. Share your experiences and shape the future.
Check out the June 2025 Power BI update to learn about new features.
User | Count |
---|---|
61 | |
55 | |
54 | |
36 | |
33 |
User | Count |
---|---|
81 | |
75 | |
49 | |
45 | |
43 |