https://community.fabric.microsoft.com/t5/Developer/Blank-issue/m-p/2508219#M36036 <P>There are a lot of pages dedicated to explaining how to solve this issue (blank in slicer), but non about why it needs to be solved in the first place.</P><P>&nbsp;</P><P>therefore, why do you need to solve the blank issue? i.e., What problems does / can it cause? (E.g., does power BI gets slower when due to it?)</P> Wed, 11 May 2022 15:34:50 GMT Dylandejong 2022-05-11T15:34:50Z https://community.fabric.microsoft.com/t5/Developer/Blank-issue/m-p/2508219#M36036 <P>There are a lot of pages dedicated to explaining how to solve this issue (blank in slicer), but non about why it needs to be solved in the first place.</P><P>&nbsp;</P><P>therefore, why do you need to solve the blank issue? i.e., What problems does / can it cause? (E.g., does power BI gets slower when due to it?)</P> Wed, 11 May 2022 15:34:50 GMT https://community.fabric.microsoft.com/t5/Developer/Blank-issue/m-p/2508219#M36036 Dylandejong 2022-05-11T15:34:50Z https://community.fabric.microsoft.com/t5/Developer/Blank-issue/m-p/2515386#M36105 <P>It's not actually an issue.&nbsp; At least not technically. Maybe an eyesore to some, but very helpful to others (especially when doing whitespace reporting)</P> <P>&nbsp;</P> <P>It's linked to the implementation of the Vertipaq engine when it comes to representing different join types. Happens when you link tables via a key that may not be fully covered on both sides of the link.&nbsp; (similar to a left or right join versus a "regular" inner join.</P> Sat, 14 May 2022 23:27:06 GMT https://community.fabric.microsoft.com/t5/Developer/Blank-issue/m-p/2515386#M36105 lbendlin 2022-05-14T23:27:06Z