The ultimate Fabric, Power BI, SQL, and AI community-led learning event. Save €200 with code FABCOMM.
Get registeredEnhance your career with this limited time 50% discount on Fabric and Power BI exams. Ends September 15. Request your voucher.
Team, I am using power bi desktop version 2.142.928.0 64-bit (April 2025).
I am connecting dataset(view) from Snowflake to powerbi via direct query mode, dataset contains Numeric(18,4). I could see the dataset in the tranform data - power quer editor.
However if I use the dataset in visual it get rounded-off.
If I use import mode, I could see the decimals. Also I have created report last month using similar dataset where decimals are diplayed in Direct Query mode.
However its causing issue with lastes Power BI desktop version.
Is there soltuion to fix it?
Solved! Go to Solution.
@v-bmanikante, Microsoft team advised it might be due to new snowflake conector implematation. As work aorund - uncheck from preview feature.
From the Power BI Desktop, navigate to Options and settings (under the File tab) > Options > Preview features, and then “unselect” the checkbox to enable the Use new Snowflake connector implementation option.
Thanks for support
I recently encountered a similar issue with the April 2025 version of Power BI Desktop (2.142.928.0) while connecting to Snowflake using DirectQuery mode.
The dataset I used includes Numeric(18,4) columns from a Snowflake view. I could clearly see the correct decimal values inside the Power Query Editor, but once I brought the data into visuals on the report canvas, those same fields appeared rounded to the nearest integer.
To verify the issue, I switched the connection mode to Import, and the decimals displayed correctly. Interestingly, I had created another report last month using the same Snowflake dataset and DirectQuery mode, and that version did not round the decimals, so this appears to be a regression or behavior change in the recent Power BI update.
Root Cause (Based on My Observations)
After investigating further, I noticed that Power BI, when working in DirectQuery mode, automatically generates a SQL query to Snowflake that casts the decimal fields as Integer, even though the source column is defined as Numeric(18,4). This transformation appears to be happening under the hood, and is unfortunately beyond our direct control.
I attempted several known fixes:
Changing the column format in Power BI to Decimal or Fixed Decimal.
Creating calculated columns and DAX measures to enforce decimals.
Using advanced ODBC parameters like:
EnableFolding=true
NoExecuteInSQLPrepare=true
Unfortunately, none of these options worked in resolving the rounding issue in visuals.
Here’s what finally worked:
Opened Power Query Editor and created a new custom column based on the original one:
This forced Power BI to treat the column as a Decimal, not as an Integer.
After this, the new column appeared as Alphanumeric (ABC123) in the data model.
In the Model View, I:
Explicitly set the Data Type to Decimal Number.
Set the Format to display up to 2 or 4 decimal places as required.
Then, I updated my DAX measures and visuals to rely on this new column instead of the original one.
And this resolved the rounding issue in DirectQuery mode.
This seems to be a behavior change in the newer Power BI version when rendering visuals via DirectQuery from Snowflake, especially for numeric fields. If you're facing this issue, I recommend trying the above workaround — recreate the column by multiplying it with 1.00 in Power Query, then rebind your visuals/measures accordingly.
Hopefully, Microsoft will address this regression in a future update. Until then, this workaround should help maintain decimal accuracy in reports.
If our response addressed, please mark it as Accept as solution and click Yes if you found it helpful.
Best regards,
Muhammad Ali Shan
Power BI Developer & Data Analyst
Hi @Shanemougham ,
We wanted to kindly follow up to check if the solution provided for the issue worked? or Let us know if you need any further assistance?
If our response addressed, please mark it as Accept as solution and click Yes if you found it helpful.
Regards,
B Manikanteswara Reddy
@v-bmanikante, Microsoft team advised it might be due to new snowflake conector implematation. As work aorund - uncheck from preview feature.
From the Power BI Desktop, navigate to Options and settings (under the File tab) > Options > Preview features, and then “unselect” the checkbox to enable the Use new Snowflake connector implementation option.
Thanks for support
Hi @Shanemougham ,
We wanted to kindly follow up to check if the solution provided for the issue worked? or Let us know if you need any further assistance?
If our response addressed, please mark it as Accept as solution and click Yes if you found it helpful.
Regards,
B Manikanteswara Reddy
Thanks @SamWiseOwl for your suggestions. I have tried those options but still its not working.
For the same view, if I change to Import Mode its working fine.
Also Last month I developed this report, it was working for Direct Mode as well.
I was requested my team test this in their power bi destop, everyone has same issue. Also this issue is not only specific a single table or view, its for all the tables and view in direct query mode.
Hello @Shanemougham ,
Thank you for reaching out to Microsoft Fabric Community Forum.
@SamWiseOwl Thank you for your quick response.
Could you please try below option?
If this post helps, then please consider Accepting as solution to help the other members find it more quickly, don't forget to give a "Kudos" – I’d truly appreciate it! |
Regards,
B Manikanteswara Reddy
Hi @v-bmanikante, Thanks for your response. Tried this option, but sill not working.
Below is Dataset when viewed in transform data panel:
I tried all possible formatting in table or matrix. However it doesnt fix this issue.
Also I have created reports using this dataset with direct query mode, it works fine. But when i try for the new report with latest power bi update its not working.
Hi @Shanemougham ,
Thank you for the update.
@Sergii24 Thank you for your response.
Please try to create new calculated column using any of the below DAX query.
If the issue still persists, I’d recommend raising a support ticket with Microsoft as @Sergii24 suggested.The support team can look into the backend and provide more in-depth assistance tailored to your environment.
If this post helps, then please consider Accepting as solution to help the other members find it more quickly, don't forget to give a "Kudos" – I’d truly appreciate it! |
Regards,
B Manikanteswara Reddy
Thanks @v-bmanikante, I tried with new column it didnt work as well. I will raise issue with microsoft.
Hi @Shanemougham, if the issue persists with a single report created using the previous version of Power BI Desktop, you might want to verify it with the Microsoft Support team:
Good luck!
Daft question but is it the visual that is doing the change?
Change the number of decimals on the column from Auto
Once you have done the column check the visual settings, for table and matrix this is specific column
Hope this helps 🙂
If you are happy with this answer please mark as a solution for others to find !
Kudos are always appreciated! Check out our free Power BI video courses.
User | Count |
---|---|
69 | |
69 | |
66 | |
54 | |
28 |
User | Count |
---|---|
112 | |
82 | |
66 | |
48 | |
43 |