Power BI is turning 10! Tune in for a special live episode on July 24 with behind-the-scenes stories, product evolution highlights, and a sneak peek at what’s in store for the future.
Save the dateEnhance your career with this limited time 50% discount on Fabric and Power BI exams. Ends August 31st. Request your voucher.
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
Solved! Go to Solution.
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! |
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! |
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! |
Check out the July 2025 Power BI update to learn about new features.