Skip to main content
cancel
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.

Reply
Anonymous
Not applicable

Column header name changes in SQL server therefore error in loading data

Hi All, 

 

Issue: Column header name changes in SQL server, therefore, breaking query steps

 

My PowerBI query is connected to a SQL server on-premise (Dynamics CRM) and the issue here is that sometimes the column name changes in the database. (for e.g., accountid_name changes to accountidname) thereby breaking my query steps. I am guessing that this happens when Microsoft pushes updates and makes minor changes to the columns in the database. Question is, is there something i can do to prevent this from happening? perhaps i am not modelling my data correctly.... 

 

Any advice is appreciated. 

 

Thanks alot

1 ACCEPTED SOLUTION
CNENFRNL
Community Champion
Community Champion

As long as the position of the referred column in a table is fixed, say accountid_name is the 4th column of #"Some Table", here's an alternative,

= Expression.Evaluate("#""Some Table""[" & Table.ColumnNames(#"Some Table"){3} & "]", #shared)

 


Thanks to the great efforts by MS engineers to simplify syntax of DAX! Most beginners are SUCCESSFULLY MISLED to think that they could easily master DAX; but it turns out that the intricacy of the most frequently used RANKX() is still way beyond their comprehension!

DAX is simple, but NOT EASY!

View solution in original post

3 REPLIES 3
CNENFRNL
Community Champion
Community Champion

As long as the position of the referred column in a table is fixed, say accountid_name is the 4th column of #"Some Table", here's an alternative,

= Expression.Evaluate("#""Some Table""[" & Table.ColumnNames(#"Some Table"){3} & "]", #shared)

 


Thanks to the great efforts by MS engineers to simplify syntax of DAX! Most beginners are SUCCESSFULLY MISLED to think that they could easily master DAX; but it turns out that the intricacy of the most frequently used RANKX() is still way beyond their comprehension!

DAX is simple, but NOT EASY!

Anonymous
Not applicable

Would you say this is best practice - is this what you usually do? 

Not best practice but an alternative for the robust of code in the scanrio you mentioned.

Another point is that the use of Expression.Evaluate() might push you wrap your head around "evaluation context" in the M language.

Enjoy M, enjoy PQ!


Thanks to the great efforts by MS engineers to simplify syntax of DAX! Most beginners are SUCCESSFULLY MISLED to think that they could easily master DAX; but it turns out that the intricacy of the most frequently used RANKX() is still way beyond their comprehension!

DAX is simple, but NOT EASY!

Helpful resources

Announcements
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

PBI_APRIL_CAROUSEL1

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.

Top Solution Authors
Top Kudoed Authors