Share
ReportI’m running into inconsistent behavior between environments when renaming a Dataverse column inside a Power BI semantic model.
In UAT, I manually rename a column in Power Query using
Table.RenameColumns(...)
The rename is honored; the column name change is returned to the model with the same manually changed name.
However, when I point the same report to PROD, the rename is ignored.
After data are returned to the model, the column name switches to the Dataverse display name, even though the Power Query step explicitly renames it.
In short:
Same M code, same semantic model, same transformation steps.
Only difference is the environment (UAT vs PROD).
In UAT, Table.RenameColumns(...) is successful in the query, and the column name change is confirmed in the data returned to the model.
In PROD, Table.RenameColumns(...) is successful in the query, but something overrides it when data are returned to the model, and the Dataverse display name is returned instead.
Has anyone seen the Dataverse override Power Query column names in certain environments?
Looking for guidance on why PROD would force the display name even after an explicit rename.
All responses (
Answers (
84
