Forum Discussion

Evogelpohl's avatar
Evogelpohl
Icon for Helper V rankHelper V
11 years ago

Q&A Filter for Today or Yesterday

In the Q&A UX, it's possible to 'ask':  "Your_Value by DateTime for Today (or Yesterday)" and the Filter UX will note "DateTime is today (or yesterday)".  But, you can't select this type of filter fr...
PowerBiLearner1's avatar
PowerBiLearner1
New Member
10 years ago
Evogelpohl wrote:

In the Q&A UX, it's possible to 'ask':  "Your_Value by DateTime for Today (or Yesterday)" and the Filter UX will note "DateTime is today (or yesterday)".  But, you can't select this type of filter from the filter drop down.  Will dynamic filters like 'latest value', 'today' or 'yesterday' be added to the pick list?

 

Also, after you pin that visual to the dashboard, and then click it to go back to the QA editor, the "DateTime is today" filter disappears.  It's as if it doesn't know how to reproduce it.  

 

Some bugs here.

I would like to add a filter to remove items AFTER let's say Jan.1/2000 How woild I do that?

 

greggyb's avatar
greggyb
Icon for Resident Rockstar rankResident Rockstar
10 years ago

With the any date included as a filter you can use the advanced filter dialog to specify Before <date>.

 

As for the concept of "Today" filters, right now the best workaround is to create helper flag fields in your date dimension which are true or false based on the criteria you'd like, and refreshed as part of your model nightly. So TodayFlag's filter could be set to True. Then every day, since the date dimension has been refreshed, TodayFlag would be true on ... today.

 

 

  • scottbell's avatar
    scottbell
    Regular Visitor
    9 years ago

    Still no solution to this. It feels like a fundemental flaw.

     

    I've got a Direct Query connection to avoid pulling down Gigabytes of useless data when want to see Today and Yesterday. The problem I have is there is no way todo this without going in every day and editting this for my users. 

     

    If I derive a col that uses data diff and then filter to = 0. It still has to pull everything todo this. I can define a month or year and make my life a little less repetative. But come on Power BI its such a simple feature.

     

    Edit- It doesn't have to pull everything down but it does cast have to cast the date and then do the calculation before returning the subset. This has quite an impact on my instances CPU usage, so several users trying to refresh this simulatously would probably lock thing up for a while. If i nest this inside a year page level filter it doesn't nest it properly in the sql statement I believe.