Forum Discussion
Visual shows blank row when in Direct Query mode
It is the expected behavior. If you don't include a column of the fact table, the only way to avoid the blank row is to join the fact table - which could be expensive. So the assumption is that there could be a blank row if you didn't specify "assume referential integrity" - checking the presence of the blank for every query on the dimension would be extremely expensive. DirectQuery is already slow enough this way.
Hi, thank you for your reply.
So I checked what happens when I would add fields from the fact table to my table visual. So interestingly the blank row still appears when I add the fact table value column, but it disappears when I also add the dimension key column of the fact table. See below images.
I checked the DAX queries for the import and direct query visuals and they are both the same. So I don't know about the Auto-Exist issue..
What I also found was that when I choose the option 'Assume referential integrity' in the relationship properties, the blank row also disappears. However, this does not solve the issue when Dual mode tables are used (which is the case for me). So I updated the model with a Dual mode table to show you what happens.
Note that for both relationships going to the Direct Query fact table, the 'assume referential integrity' option has been chosen.
Now I maybe am even more confused about this behavior.
This is exciting. I would have not expected the queries to have the same query plan. Maybe time for marcorusso to have a look at this.
