Forum Discussion

Anonymous's avatar
Anonymous
Not applicable
2 years ago
Solved

Fiscal Year Calendar Filtering

I created a fiscal year calendar to use so that I can filter both SharePoint and Dataverse columns. When I use it with SharePoint, it works perfectly. However, when I duplicate the same features for Dataverse, nothing is returned, and I don't know enough about Power BI to determine what I am doing wrong.

 

This is what the relationship looks like for both SharePoint and Dataverse tables.

 

  • It should work as long as both columns are set to "date" type and there are actually values for everything in the date table that exist in the related table. Does your date table go all the way to FY24? 

4 Replies

  • christinepayton's avatar
    christinepayton
    Most Valuable Professional

    It should work as long as both columns are set to "date" type and there are actually values for everything in the date table that exist in the related table. Does your date table go all the way to FY24? 

    • Anonymous's avatar
      Anonymous
      Not applicable

      Thank you for your reply. 

       

      I checked and both columns are of [date] type. Because we recently just moved away from SharePoint to Dataverse, our Dataverse db only has 33 items all which were entered after 9/1/23, so what I should see when I click on the slicer are 33 items for FY 24. My relationship between my fiscal calendar and Dataverse is shown below, and the filters I am using below that. Do you think these are incorrect?

       

       

       

      • christinepayton's avatar
        christinepayton
        Most Valuable Professional

        Ohhh I understand what you're saying - the thing with date tables, is if you use the date table field in the slicer, it will automatically show all values in the date table regardless of what's in your data. You'd need to set the relationship to bidirectional and potentially add a filter of "<your measure> not equals blank" on the slicer. 

  • Anonymous's avatar
    Anonymous
    Not applicable

    You were correct. The date type was missing, and I didn't catch it. Thank you for your help!