Forum Discussion
Dataverse / Display Name persisting even after renaming column and disabling behaviour
- 1 year ago
Hi bhalicki ,
You're hitting a known issue with the Dataverse connector. Microsoft removed that EnableDisplayNames=false parameter in recent updates, which is frustrating when you're managing 300+ columns.
Here's what still works:
M code approach: Instead of UI renames, handle it in Advanced Editor:
= Table.RenameColumns(YourTable, {{"DisplayName1", "MyName1"}, {"DisplayName2", "MyName2"}})Bulk transformation:
= Table.TransformColumnNames(YourTable, each Text.Replace(_, "old_pattern", "new_pattern"))
Alternative data source: If your environment allows it, try connecting directly to the underlying SQL database instead of going through the Dataverse connector. This bypasses the Display Name behavior entirely.
Applied late in the process: Do your column renames as the very last step in Power Query. Sometimes this helps them stick better in the model.
Submit feedback: This is a legitimate workflow issue affecting many users. Consider submitting feedback through Power BI Desktop (Help > Send a Suggestion) to request the parameter be reinstated.
The M code approach tends to be more reliable than UI-based renames when dealing with Dataverse sources. Have you tried implementing the renames programmatically instead of through the interface?
If my response resolved your query, kindly mark it as the Accepted Solution to assist others. Additionally, I would be grateful for a 'Kudos' if you found my response helpful.
This response was assisted by AI for translation and formatting purposes.
Hi bhalicki ,
You're hitting a known issue with the Dataverse connector. Microsoft removed that EnableDisplayNames=false parameter in recent updates, which is frustrating when you're managing 300+ columns.
Here's what still works:
M code approach: Instead of UI renames, handle it in Advanced Editor:
= Table.RenameColumns(YourTable, {{"DisplayName1", "MyName1"}, {"DisplayName2", "MyName2"}})Bulk transformation:
= Table.TransformColumnNames(YourTable, each Text.Replace(_, "old_pattern", "new_pattern"))
Alternative data source: If your environment allows it, try connecting directly to the underlying SQL database instead of going through the Dataverse connector. This bypasses the Display Name behavior entirely.
Applied late in the process: Do your column renames as the very last step in Power Query. Sometimes this helps them stick better in the model.
Submit feedback: This is a legitimate workflow issue affecting many users. Consider submitting feedback through Power BI Desktop (Help > Send a Suggestion) to request the parameter be reinstated.
The M code approach tends to be more reliable than UI-based renames when dealing with Dataverse sources. Have you tried implementing the renames programmatically instead of through the interface?
If my response resolved your query, kindly mark it as the Accepted Solution to assist others. Additionally, I would be grateful for a 'Kudos' if you found my response helpful.
This response was assisted by AI for translation and formatting purposes.
Thanks burakkaragoz , using the SQL connector instead of the Dataverse connector works. Hope MS don't find out and update that too 🙂
Cheers,
Ben.