Forum Discussion

Mahesh_Kumar_S's avatar
Mahesh_Kumar_S
Regular Visitor
3 months ago
Solved

Filtering Issue PowerBI Report with Metric Views

Hello everyone,

I have a metric view in Databricks that contains a Date column, several dimension columns, and three calculated measures. I have connected this view to Power BI and created one card visual and two table visuals.

 

The issue I’m facing is with filtering. When I select all months or Multi Select in the date slicer, the visuals display results as expected. However, when I select a single month from the slicer, the visuals return no results and an error is thrown.

 

Could someone please help me understand what might be causing this issue and how to fix it? I have attached the .pbix file for reference.

   


Thanks in advance for your help.

Regards,
Mahesh

 

  • Thank you for your time and support. The suggested solution did not resolve the issue in our case. However, after modifying the query on the Databricks side, the problem was resolved and the visuals are now working as expected.

    Appreciate the help.

    Regards,
    Mahesh

7 Replies

  • Thank you for your time and support. The suggested solution did not resolve the issue in our case. However, after modifying the query on the Databricks side, the problem was resolved and the visuals are now working as expected.

    Appreciate the help.

    Regards,
    Mahesh

  • Please copy and paste the text of the error into the question. Cannot see the image of the error msg.

    • Mahesh_Kumar_S's avatar
      Mahesh_Kumar_S
      Regular Visitor

      Hi Thomaslleblanc ,

       

      Thanks for your time and Please find the error message.


      OLE DB or ODBC error: [DataSource.Error] ADBC: An unexpected error occurred while fetching results. 'One or more errors occurred.: (1)
      [MISSING_ATTRIBUTES.RESOLVED_ATTRIBUTE_MISSING_FROM_INPUT] Resolved attribute(s) "Year Month" missing from "Monthly Redemption", "MonthlyAUM", "fund_dim", "share_class_dim", "advisor_dim", "org_dim", "territory_dim" in operator !Aggregate [named_struct(col1, max(YearMonth#13456)) AS _internal_window_measure_Current Month Redemption#13469, named_struct(col1, max(YearMonth#13456)) AS _internal_window_measure_Prior 11M Redemptions#13470, named_struct(col1, max(YearMonth#13456)) AS _internal_window_measure_Current Month AUM#13473, named_struct(col1, max(YearMonth#13456)) AS _internal_window_measure_Prior 12M AUM#13474, named_struct(col1, max(YearMonth#13456)) AS _internal_window_measure_Current Month Redemption#13469, named_struct(col1, max(Year Month#13456)) AS _internal_window_measure_Prior 11M Redemptions#13470, named_struct(col1, max(YearMonth#13456)) AS _internal_window_measure_Current Month AUM#13473, named_struct(col1, max(YearMonth#13456)) AS _internal_window_measure_Prior 12M AUM#13474]. SQLSTATE: 42704; line 1 pos 69".

       

      Regards,

      Mahesh

      • Thomaslleblanc's avatar
        Thomaslleblanc
        Super User

        The core issue is your query references a column called “Year Month” (with a space) that does NOT exist in any of the listed tables, while the engine does find a column named YearMonth (no space).

  • Column name mismatch, your model references both YearMonth and Year Month, which are treated as different columns.

    During aggregation, the engine cannot find Year Month in the input tables, causing the query to fail.

  • v-prasare's avatar
    v-prasare
    Community Support

    Hi Mahesh_Kumar_S,

    We would like to confirm if our community members answer resolves your query or if you need further help. If you still have any questions or need more support, please feel free to let us know. We are happy to help you.


    mh2587 & Thomaslleblanc ,Thanks for your prompt response

     

     

    Thank you for your patience and look forward to hearing from you.
    Best Regards,
    Prashanth Are
    MS Fabric community support

  • v-prasare's avatar
    v-prasare
    Community Support

    Hi Mahesh_Kumar_S,

    Thanks for sharing that you were able to resolve the issue with a workaround, glad to hear it’s working now

    If you face any similar issues in the future, feel free to raise a question here in the Fabric Community. The community is always happy to help!

     

    Thanks,

    Prashanth