Forum Discussion
Community AdminShare your thoughts on the New Power Query experience in Power BI Desktop (Preview)
Many thanks for the opportunity to feed in!
I am in the process of building a custom connector and testing across both experiences. This is highlighting some differences/issues that I suspect will impact certified connectors as well.
1, For Parameters the new experience does not surface in-line guidance that the original experience does. It seems to miss it for drop-down parameters but works for input box parameters.
New Experience
Same Connector in old experience
2, The behaviour for dropdowns is also different in the classic experience, in classic parameters load with null option, for the new experience they load with the first option as default. This can be accounted for in the connector but will change the experience of existing connectors that have accounted for null values or have built optional parameters that should only be selected when override behaviour is desired.
3, The honouring of Formatting.IsMultiLine is not right in either experience. In classic it's not honoured in the collapsible optional features, in the new experience it's not honoured anywhere.
4, The Advanced options are defaulted collapsed in the new experience, that's great, I couldn't get it working in the classic experience.
5, In the classic experience the connector I've built can be triggered from within PBI Desktop, generates a preview and option to Load/Transform, allowing me to never enter Power Query (by choosing Load). The same connector in the new experience pushes me to Power Query everytime.
6, The new experience doesn't seem to match to existing global credentials that could be used forcing more Oauth validation.
Within the Navigation Table option
7, The current experience allows for a function with parameters to be shown in the right panel of the naviation table. Values can then be entered and there's an apply button which means this can be created directly from the Get Data query, this is great. In the new experience the apply button doesn't exist which means this approach fails with errors. It does however show the documentation that currently fails to show in classic experience!
Classic
New experience (no apply button)
It's mentioned elsewhere but the ability to favourite connectors would be hugely useful.
- miguel
This is absolutely fantastic. Thank you for taking the time to report these issues.
#1, #2, #3 and #7 are things that we are tracking and hope to address in the coming months.
For #5, is your connector using a Nav table? or is it simply creating a single query where the Table Preview is not shown and you just land in the query editor?
We have an existing bug that we're trying to fix which could be related to #6 in which connectors that rely on OAuth do not have their credentials automatically matched to the credential that you have stored for the same path provided. This is what's causing the overall behavior where you have to re-enter your credentials for the same resource path over and over again.
Great to hear those are already on the radar. 😀
ON #5 I'm testing both mechanisms at the moment
1, Just using the basic parameters without ever showing the navigation tree.
2, Having a navigation table then using functions to catch parameters
I'm seeing the behaviour of getting pushed straight to Power Query from Get Data in Desktop using the first option (the basic parameters screen). I don't know what the navigation table path will do as the missing Apply button (#7) means it's erroring earlier so can't test. Let me know if any other info needed on this.
That definitely sounds like the issue I'm having on #6.
