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

Register now to learn Fabric in free live sessions led by the best Microsoft experts. From Apr 16 to May 9, in English and Spanish.

Helper II
Helper II

Naming fields in analytics



Could you please advise a good method to name fields in analytical data modeling?


For example, I have CustomerID in Customers and Orders tables.


In production database these names are the same (CustomerID in Customers and the same in Orders).


In analytical datamodel I want to differentiate these Ids, because it gets very confusing (at least to me).


For example, several approaches.


Customers-CustomerID and Orders-CustomerID


Another approach


CustomerID.Customers and CustomerID.Orders


In another words, I want to preserve the table name (full resolution), and in some cases even database name, like CustomerID.Customers.Accounting and CustomerID.Customers.Marketing


Otherwise it is getting pretty confusing in reports to understand to what database, table or file this field is from.


Maybe I'm on a wrong path here? Any suggestions or links to common practice would be appreciated.








Memorable Member
Memorable Member

Memorable Member
Memorable Member

Hi @vyacheslavg


This video from Ruth Puzuelo might help..



Hi Dave, 


this is great.

It shows that PBI master is using the same technique for something in her workflow.

And there is even the M function to simplify this stuff.

Very useful indeed, thanks.

Helpful resources

Microsoft Fabric Learn Together

Microsoft Fabric Learn Together

Covering the world! 9:00-10:30 AM Sydney, 4:00-5:30 PM CET (Paris/Berlin), 7:00-8:30 PM Mexico City


Power BI Monthly Update - April 2024

Check out the April 2024 Power BI update to learn about new features.

April Fabric Community Update

Fabric Community Update - April 2024

Find out what's new and trending in the Fabric Community.