Skip to main content
cancel
Showing results for 
Search instead for 
Did you mean: 

The Power BI Data Visualization World Championships is back! Get ahead of the game and start preparing now! Learn more

Reply
clock84
Frequent Visitor

October 2025 PBI Version - Snowflake Connector Issue

Power BI desktop has started rolling out October 2025 to users and we are experiencing an issue when using Direct Query to connect to Snowflake.  

 

Connections include ,[Implementation="2.0"] in the source line and once you toggle to the Navigation line in Power Query, you are still met with the prompt that you need to switch to Import mode.   

 

Removing ,[Implementation="2.0"] remedies this problem and allows users to continue their connection with Direct Query. 

 

,[Implementation="2.0"] was included in previous versions of Power BI Desktop, but wasn't giving us this issue until today with the new version.  

1 ACCEPTED SOLUTION

Thank you for the update!  I had to uninstall and reinstall to get it.

View solution in original post

20 REPLIES 20
v-tsaipranay
Community Support
Community Support

Thank you for the update.

v-tsaipranay
Community Support
Community Support

Hi @clock84 ,

 

Thanks for the update. Glad there’s a workaround and a fix planned for November 2025 and appreciate you sharing this.

 

We have also encountered this issue. Very happy to hear this is a known issue with an impending fix.

Microsoft released an update October 29 in version 2.148.1226.0 and after doing some initial tests the issue with the Snowflake Connctor in DirectQuery mode seems to have been solved (Yes, I also tested import mode).
I will continue with more tests. but for now it looks fine.
Download Microsoft Power BI Desktop from Official Microsoft Download Center
and No, there are nothing mentioned in the Change log, Change log for Power BI Desktop - Power BI | Microsoft Learn.

Thank you for the update!  I had to uninstall and reinstall to get it.

ch_pbi
Frequent Visitor

We are still getting errors with the 2.0 connector, specifically about precision from the source system.

Are you talking about Int128 data types?

Here is the error: "Decimal's scale value must be between 0 and 28, inclusive. Parameter name: scale"

Admittedly, we do allow 29 decimals in the data source, but before the initial update to the 2.0 connector last week we did not experience issues with this data or receive this error. 

Ah, so not Int128 related (at least not directly).  I'd suggest you raise a ticket.

 

If you have a Pro license you can open a Pro ticket at https://admin.powerplatform.microsoft.com/newsupportticket/powerbi
Otherwise you can raise an issue at https://community.fabric.microsoft.com/t5/Issues/idb-p/Issues .

Actually, I received word yesterday through my support ticket that they would be implementing an update to the October 2025 version soon(I guess that could be days or the next week or two?).  This is already fixed on the November 2025 version as well.

 

Root Cause:
The problem is due to a regression in the October 2025 Power BI Desktop version related to the Snowflake connector’s 2.0 ADBC implementation. Missing query folding capabilities and changes in the query plan prevent certain transformations from functioning in DirectQuery mode, which leads to the error.

Hi @clock84  ,

Thank you for the detailed update.

v-tsaipranay
Community Support
Community Support

Hi @clock84 ,

Thanks for reaching out to the Microsoft fabric community forum. 

Thanks for the update. Good to know you’ve already raised a support ticket with Microsoft. Could you please confirm if the issue has been resolved? If yes, it would be great if you could share a brief summary of the insights or steps provided by Microsoft Support this would be very helpful for other members who might face the same issue.

Thank you.

@v-tsaipranay  - No problem and just wanted to get ahead of the issue with my Power BI users.  It would seem that any fix will not be implemented until the Nov 2025 release at the earliest.  With as frequent as they are updating the desktop(monthly), I understand this makes more sense when there is a workaround in place.

Not resolved

jonathantied
New Member

We had the same issue. Removing [Implementation="2.0"] solved it for us. We are also in touch with Microsoft report. They are aware of the issue and it is expected to be solved in the November release. 

Braggilicious
Frequent Visitor

Same Issue. Please fix. 

nleclercq
Regular Visitor

Same issue here..

lbendlin
Super User
Super User

If you have a Pro license you can open a Pro ticket at https://admin.powerplatform.microsoft.com/newsupportticket/powerbi
Otherwise you can raise an issue at https://community.fabric.microsoft.com/t5/Issues/idb-p/Issues .

Thank you and I entered a ticket to work with Microsoft.  I would assume something has changed with the version from September to October and hope we don't have to wait until November.

Hi, can you share a ticket number ?.
We created an ticket (2510231420003086) and Microsoft support says this is an unknown issue.

Helpful resources

Announcements
Power BI DataViz World Championships

Power BI Dataviz World Championships

The Power BI Data Visualization World Championships is back! Get ahead of the game and start preparing now!

December 2025 Power BI Update Carousel

Power BI Monthly Update - December 2025

Check out the December 2025 Power BI Holiday Recap!

FabCon Atlanta 2026 carousel

FabCon Atlanta 2026

Join us at FabCon Atlanta, March 16-20, for the ultimate Fabric, Power BI, AI and SQL community-led event. Save $200 with code FABCOMM.

Top Solution Authors