I'm sorry to have to be the negative nilly in the room, but I am sorely dissapointed in this feature implementation. I can understand wanting to alleviate the renaming people have been suffering and to leverage the column Display Names from the DV schema... great. But executing this as an automatic transformation with no control options to turn it off, opt out on refresh or apply it selectively to columns:
- Leaves the column name representations in the visual builder mixed, some with display names and others with logical names. Ugly and messy.
- Begins to negate transformations made in Power Query and removes the option to choose where they occur.
- Breaks existing DAX queries being passed via the Power Automate query action.
- Assumes Power BI designers are the kinds of users who need the 'simplistic' nanny-approach. Seriously?
We use models to build visualisations that benefit from friendly naming, yes, but we also use them to drive sophisticated dynamic querying features in conjunction with flows, canvas app, Azure functions etc. that work at the logical level. Satisfying the needs of one audience therefore risks disadvantaging another, and shifts the burden of model renaming to those having to change them back, in our case by the hundreds.
Please take a serious look at the implications before unleashing these kinds of things on your customer base. Im sure we would all prefer these kinds of changes to be considered and thorough, even if it takes longer to get them out. And please, let's see some options control over this get updated soon.
