Forum Discussion

tkiwi's avatar
tkiwi
Icon for Helper I rankHelper I
1 year ago
Solved

(Blank) in slicer

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

  • 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.

6 Replies

  • Deku's avatar
    Deku
    Icon for Super User rankSuper User

    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.

    • tkiwi's avatar
      tkiwi
      Icon for Helper I rankHelper I

      "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?

      • Deku's avatar
        Deku
        Icon for Super User rankSuper User

        Yes, this what I have said. Press the referential integrity button when creating the relationship to confirm no duplicates or blanks 

  • v-prasare's avatar
    v-prasare
    Icon for Community Support rankCommunity Support

    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

    • tkiwi's avatar
      tkiwi
      Icon for Helper I rankHelper I

      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."

      • Anonymous's avatar
        Anonymous
        Not applicable

        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