The ultimate Microsoft Fabric, Power BI, Azure AI, and SQL learning event: Join us in Stockholm, September 24-27, 2024.
Save €200 with code MSCUST on top of early bird pricing!
Find everything you need to get certified on Fabric—skills challenges, live sessions, exam prep, role guidance, and more. Get started
When I try to use Direct Query, an error occurs like "OLE DB or ODBC error: [Expression.Error] We couldn't fold the expression to the data source. ".
It's a third ODBC Driver which can run when using Import mode.
Hi, I am having the same issue when using snowflake to direct query, any suggestions?
I would suggest to connect through Snowflake connector in Power BI and put the custom query in the advanced section (Select * from TABLE) of loading new data source. See if that helps.
Thank you, thats what we are currently doing. Everything was working fine then all of a sudden it flags that error now. Since you are so responsive lol, I have another question, not many people use snowflake and power bi, and I cannot get support from either end. When connecting in desktop mode everything works great but when I publish I continue to get a credentials error, did this ever happen to you?
It didn't happen to me. But some of things to check is the how is the gateway connection configured and always suggest to use organizational authentication. Other way is to turn off the gateway connection and enter in the snowflake credentials in the data source setting and select following options for authentication methods.
In case of direct query, if you are using snowflake credentials method, all your users will need to be set up as "users" in Snowflake as well.
Thank you so much! I have tried all of the above :(. Still no luck! I will try to reach out to support once again! I greatly appreciate your help.
It's the latest version. When Power BI trace turned on, it output like:
DataMashup.Trace Warning: 24579 : {"Start":"2018-01-29T03:14:27.6225607Z","Action":"OdbcQuery/FoldingWarning","HostProcessId":"8744","ErrorMessage":"Data Type of column cntnum with searchable property UNSEARCHABLE should be SEARCHABLE or ALL_EXCEPT_LIKE. You can override the supported data types from ODBC driver using SQLGetTypeInfo.","ProductVersion":"2.54.4970.961 (PBIDesktop)","ActivityId":"7e8bcd2a-e17e-4d3f-a592-a2b2c71080cd","Process":"Microsoft.Mashup.Container.NetFX40","Pid":15572,"Tid":1,"Duration":"00:00:00.0003110"}
And Power BI does not call SQLGetTypeInfo at all.
Join the community in Stockholm for expert Microsoft Fabric learning including a very exciting keynote from Arun Ulag, Corporate Vice President, Azure Data.
Check out the August 2024 Power BI update to learn about new features.
User | Count |
---|---|
113 | |
83 | |
75 | |
51 | |
42 |
User | Count |
---|---|
140 | |
113 | |
73 | |
64 | |
62 |