Dataverse Connector - Display Name Change Impact

[Ksven]

Hi lovely community,

When I create a Parent / Child Reporting (one Master Report with Dataset and some Child Reports connected to Master Dataset) and someone will change some Display Names in Dataverse, it's dangerous to damage your Child Report Visualizations.

After integration of new Display Name Feature I had to change all Viz Mappings of my Child Reports... don't like this Feature so far..

Please ensure all Child Reports will work independently of Display Name Changes. In Best Case it recognized also Column Name and Source Column independently.

BR,

Sven

[Anonymous]

Hi @Ksven 

I think you may have created it in the wrong place. You still created an idea in the Issue forum. You need to mention your idea to the Ideas forum. This link below is to the Ideas forum, where you can create your requirement.

Ideas (powerbi.com)

Best Regards,
Community Support Team _ Ailsa Tao

[Ksven]

Hi @Anonymous ,

thank you for the hint!

Have created it here now:

https://ideas.powerbi.com/ideas/idea/?ideaid=cc56d52b-778a-ed11-a76e-501ac524925c

BR,

Sven

[Lucian]

Hello @Anonymous ,

I would consider this subject an Issue not an ideea because it breaks the very logic of the Power Query. And I think that "Display name support for the Dataverse connector" is a great idea, but the implementation is the worst joke from Microsoft.

Why in the world you would do something AFTER the steps I do in Power Query? Why the rename should be done in the model and not be clearly seen in the Power Query steps? Why keeping separate documents or records just to recall what was the original name and what is the new name - because for some reasons I need to rename a column I will loose the track of this changes.

Don't get me wrong - using the display name of the dataverse table is a good ideea, but I would prefer to see that change in the Power Query editor like I'm doing for ALL the other connectors, and even in Dataflows where I first saw this ideea it was a step named "Map to entity" that I could choose to delete or modify it and way more easier to track the changes.

So because it breaks all the logic of Power Query I would considerit an big issue, and the implementations of this "feature" should be modify so it would respect that Power Query logic.

Kind Regards,

Lucian