 |
| M code generated based on renaming from the data pane |
Did you know? Where you rename columns can potentially create or avoid last-minute rework.
Ideally you should have semantic model names locked down before you build out a report interface. But even then, you sometimes get requested changes when you are nearing the end of development.
- Changing a column name directly in Power Query can* break references to the column in the UI and in measures.
- Renaming the column in the data pane retains all references and automatically adds a new renaming step to the end of the Power Query query that created the underlying table.
* From testing, it seems like Power BI can absorb a simple change, like renaming one column in a table and leaving the number and order of columns the same, but making many changes at once confuses Power BI, and visuals and calculations start to break.