Forum Discussion

sofia_pc's avatar
sofia_pc
Regular Visitor
2 years ago
Solved

OLE DB or ODBC error with Boolean Column Filter

I keep getting the error "OLE BD or ODBC error: [Expression.Error] We couldn't fold the expression to the data source. Please try a simpler expression."

 

This is happening across multiple reports. They are all connected using DirectQuery to Snowflake.

 

I figured out this happens when I try to filter my report with a TRUE/FALSE column (no specific field, this happens with different columns in different tables). It's not because of a complex query, I've tested creating a blank file with only one table connected, and adding a card and the TRUE/FALSE filter. Still returned an error.

 

I've tried using a slicer, a report level filter, a calculated column and measure. All of these return the error in the viz. The columns are TRUE/FALSE in PowerBI and Boolean in Snowflake so the data type is correct.

 

This only started happening recently (I opened a few reports months later and suddenly all of them are returning an error) but only on Desktop app. All vizs are fine in the online service.

 

I've tried uninstalling and reinstalling the desktop app and nothing changed.

 

I'm not sure what to try next, almost all my reports and vizs use at least one TRUE/FALSE column filter.

5 Replies

  • vanessafvg's avatar
    vanessafvg
    Community Champion

    what are you doing with a calculated column?   so do you have a combined model?  i would try and push the calculated column to direct query if you can, if you have a platform what is the value of creating a calculated column in power bi?  Please can you provide an actual example of what the data looks like andd the error you get, as well as your measure code, with what you expect to get.

    • sofia_pc's avatar
      sofia_pc
      Regular Visitor

      I only created a calculated column as a workaround for this issue, since I saw that suggested in other posts. The fields are already in TRUE/FALSE type from the source (Snowflake), and I first attempted to filter the report directly with that field. 

      Any time a boolean field is being used in my reports, I am receiving the error I mentioned.

  • Hi,

    Did you manage to resolve this issue?  I am facing the similar issue and wondering if you had a solution for it?

    Regards

    Nav

    • sofia_pc's avatar
      sofia_pc
      Regular Visitor

      Yes, seems like there was a bug in the latest release. I rolled back to the May version of the app and it worked fine.