Forum Discussion

BrentDC's avatar
BrentDC
Regular Visitor
4 years ago
Solved

DATE filter problem in combined dashboard

Hi,

 

I have created a combined dashboard with a direct query source (Powerbi Dataset) and a DATE table with hierarchy created in Dax.

They are connected with a 1 to many cardinality.

 

When I want to use the DATE filter in the dashboard it does nothing. So the filter does not work, despite the connection and the matching dates.

 

Probably something in the settings is not right?

The latest version of BI desktop is installed.

 

The connection

The connection

 

Without filtering

Without filtering

 

With filtering

With filtering It doesn't show anything...

 

Thanx !

  • Hi BrentDC ,

    Do you have any access to the original dataset you're connecting to? 

    My suspision is that it the Date_Order column actually contains times as well as dates eg 10/08/2021 11:55:31 for example. However in the model is set to format them all just as dates.

     

    You can either create a pure date column in your remote dataset or:

     

    If you install Tabular Editor (free version 2 is fine) and connect to your local model try doing:

     

    1) Expand Relationships and click the relationship in question.

    2) In the properties pane change the "Join On Date Behaviour" to "DatePartOnly"

     

     

9 Replies

  • bcdobbs's avatar
    bcdobbs
    Icon for Community Champion rankCommunity Champion

    I'd check that the columns involved in the relationship are both set as Dates. It looks like when you filter your date table there are no matching values on the other end. This could happen if one was still text or if one was a date time not date.

    • BrentDC's avatar
      BrentDC
      Regular Visitor

      Hi,

      They are both marked as Date/Time columns, I cannot modify the date_order column from the Direct query  It is marked from the source as date column.

       

      • bcdobbs's avatar
        bcdobbs
        Icon for Community Champion rankCommunity Champion

        Put the date fields from the two ends of the relationship into separate table visuals and have a look at their contents. I'm guessing one end has time parts that don't match.