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

The FabCon + SQLCon recap series starts April 14th at 8am Pacific. If you’re tracking where AI is going inside Fabric, this first session is a can't miss. Register now

Reply
Anonymous
Not applicable

Decimal Type Join Columns in Modeling

Hi All,

 

In our project, we are using decimal(not fixed decimal) type Key columns for creating the relationship between dimensions and facts when we do modeling.

 

do we face any problems if we follow the above approach?

 

Thanks

Venkat

4 REPLIES 4
TomMartens
Super User
Super User

Hey,

 

I never heard of this before, I guess there will be some good reasoning for this kind of design decision.

 

Nevertheless, I guess as long as your decimal keys match the capabilities of the decimal (number) data type

https://docs.microsoft.com/en-us/sql/analysis-services/tabular-models/data-types-supported-ssas-tabu...

you are good to go.

 

Hopefully this is what you are looking for.

 

Regards,

Tom



Did I answer your question? Mark my post as a solution, this will help others!

Proud to be a Super User!
I accept Kudos 😉
Hamburg, Germany
Anonymous
Not applicable

The problem we are having in our case is, our key columns are drive keys, means it is a combinition of multiple columns, when we are derive these drive keys, their size is more than the normal whole number(bigint in sql server), to accomadate the same, we coverted all these drive key columns types to decimal number(not fixed decimal), which is equal to decimal(38,0) in sql server. We want to know the problems, we may face when we do like this.


@Anonymous wrote:

The problem we are having in our case is, our key columns are drive keys, means it is a combinition of multiple columns, when we are derive these drive keys, their size is more than the normal whole number(bigint in sql server), to accomadate the same, we coverted all these drive key columns types to decimal number(not fixed decimal), which is equal to decimal(38,0) in sql server. We want to know the problems, we may face when we do like this.


I assume by drive keys you mean "derived" keys. If this is the case then using the decimal data type is a really bad idea. The decimal data type in tabular models is a floating point number, so it is not precise and this could cause two keys to possibly round differently and not match. Or worse still if could cause 2 different keys to round to the same value. You should use either a string or integer number for your keys.

Hi @Anonymous ,

 

If you'd like to know the limitation when using decimal type in power bi model, here're blogs for yourreference:

 

https://www.sqlbi.com/articles/understanding-numeric-data-type-conversions-in-dax/

https://www.qumio.com/Blog/Lists/Posts/Post.aspx?ID=50    

 

Best regards,

Dina Ye

Community Support Team _ Dina Ye
If this post helps, then please consider Accept it as the solution to help the other members find it more
quickly.

Helpful resources

Announcements
New to Fabric survey Carousel

New to Fabric Survey

If you have recently started exploring Fabric, we'd love to hear how it's going. Your feedback can help with product improvements.

Power BI DataViz World Championships carousel

Power BI DataViz World Championships - June 2026

A new Power BI DataViz World Championship is coming this June! Don't miss out on submitting your entry.

Join our Fabric User Panel

Join our Fabric User Panel

Share feedback directly with Fabric product managers, participate in targeted research studies and influence the Fabric roadmap.

March Power BI Update Carousel

Power BI Community Update - March 2026

Check out the March 2026 Power BI update to learn about new features.