Dataverse connector - multiple issues: Display Names, errors because "relationship columns"

[Lucian]

Hello,

Is just me that I have the feeling that using Dataverse connector became a more and more hard to use?

Issue1: Forcing autorename columns to Dataverse Display names - good idea but the worse implementation ever. Why?... because what Microsoft did break all the logic of Power Query where I should see ALL the transformations. Instead Microsoft choose to force changing columns to Dataverse display names, and if I have to rename one I shoud rename it in the "model section" not in Power Query, so this way loosing any posibility to keep track of the original name of the column. So in Power Query I see one thing, but in data model something else... and this is NOT funny.

Original idea that still need votes, posted by @Benjamin Bootz:  Make the new dataverse "Display Names" feature an opt-in feature instead of forcing it over

Issue2: Cannot transform data without manually edit the query.

Well couple of days ago I had to open an support ticket because I cannot get data from a simple Dataverse table like Account, Opportunity or Systemuser because of an error: "Preview.Error: The type of the current preview value is too complex to display."

Usually, for the well known tables I don't wait for preview to finnish and go directly to "Transform data", but here is the same error.

Finally the Support Technician came with a workaround, to manually edit the query, adding an option that would exlude the "relationship columns":

Source = CommonDataService.Database("msdefault.crm.dynamics.com", [CreateNavigationProperties=false])

For me, because I was using Power Query enough, is ok, but I think it would be way more easier if the Dataverse connector would have an option like the SQL Sever to let the user choose to include or not these "relationship columns". 

So here is the initial ideea that will need votes: Dataverse connector should have an checkbox for "Include relationship columns" as SQL have

Kind Regards,

Lucian

[Anonymous]

Hi @Lucian ,

Thanks for the feedback on the product, the idea forum is the right place to post it. issue forum can only give feedback on temporary bugs for now.

If you would like to suggest  feature improvements, you may  vote the idea and comment here  to improve this feature. It is a place for customers provide feedback about Microsoft Office products . What’s more, if a feedback is high voted there by other customers, it will be promising that Microsoft Product Team will take it into consideration when designing the next version in the future.

Best Regards,
Community Support Team _ Caitlyn