Skip to main content
To homepage To homepage

I am having issues with decimal numbers in my Power BI model created with TimeXtender XMLA endpoint (version 7026.1).
No matter the precision of my datatype on SQL server it seems like all values are forced into a rounded 4 decimal size. Is there a setting hiding somewhere to prevent this behavior?

Below are examples or test data to demonstrate the behavior.

Inspecting the model with tabular editor it seems all decimal fields are stored as fixed decimal rather than the expected double


 

Test data

 

Result in Power BI

 

Hi,

if you look into your Power BI model is the data type a Fixed Decimal or a Decimal? Fixed decimals are rounded at 4 decimals: https://learn.microsoft.com/en-us/power-bi/connect-data/desktop-data-types

It’s shown as fixed decimal (see my first screenshot), but I don’t see any way to override that datatype through TimeXtender, directly or indirectly.

Usually 4 decimals would be sufficient, but in this case I actually need precision to be at the 6th decimal

Hi,

yeah - you can only choose a decimal formatting which just adds a presentation on top of the datapoint. It lt looks like the type chosen is DataType.Decimal (which is Fixed Decimal) instead of DataType.Double which would allow more precise values.

Good find - I never noticed this. I am not 100% sure this was always the case, but it looks like there is no way to generate more precise data in PBI.

Note that the type naming is rather confusing: DataType.Double is Decimal in PBI and the equivalent of float in SQL Server. DataType.Decimal is Fixed Decimal Number / Currency in PBI and the equivalent of decimal(19,4) in SQL Server.

Reply


Terms and ConditionsCookie settings