Forum Discussion

PowerBIkalaimo's avatar
PowerBIkalaimo
Helper I
7 years ago
Solved

Issues with using a Date Dim table

I have a Fact table with a DateKey as one of the fields.  I added a DateDim table, and linked the 2 tables with the DateKey in the model.  My issue is, when I do a CountRows of the Fact table, and it is linked to the DateDim table via the date key, the row count is off by about 2000 (of 3500000) records.  If I remove the link to the DateDim table, the row count is correct.  

To troubleshoot, I re-created the DateDim table with just the DateKey and linked that to the Fact table.  The row count was correct.

I added all my other DateTable fields back (MonthYear, Quarter, etc), and row count worked for all of the fields EXCEPT when I added Date.  

So if I create the DateDim table with DateKey and Date and link to the Fact table on DateKey, the row count is incorrect.  If I create the DateDim table with DateKey and MonthYear & Quarter only (and leave out Date) and I link to the Fact table on DateKey the row count is correct.

I do need the date field for my slicer.  Any thoughts as to what is wrong here?

Thanks for any help!

Need Help
  • PowerBIkalaimo's avatar
    PowerBIkalaimo
    7 years ago

    After researching, someone had added a hidden slicer to the report that was being used to "slice a slicer" and remove certain record choices from the main slicer.  Once the edit interactions with these slicers was fixed, everything worked as expected.

2 Replies

    • PowerBIkalaimo's avatar
      PowerBIkalaimo
      Helper I
      7 years ago

      After researching, someone had added a hidden slicer to the report that was being used to "slice a slicer" and remove certain record choices from the main slicer.  Once the edit interactions with these slicers was fixed, everything worked as expected.