on
RE:
Agreed, I have a report that combines data from the ERP and CRM, and I rely on bookmarks for tailored slicer panes and button behavior for each page. This limit forces me to limit the number of pages and split the report into several files.
RE:
Very necessary for the scenarios where we need to move steps around, and risk breaking references that are hard to debug in an already very-hard-to-debug language. Since order of operations is intrinsic to power query, relativising references would make it far easier to work with code rather than the restrictive GUI.Would be good to be able to traverse multiple steps backwards in cases where the step before is not the table you intend to operate on, but retrieves some value you need, e.g.:let Step1 = loadData(...), Step2 = ([params...]) => [function definition], Step3 = Table.AddColumn(# - 1, "NewColumn1", each Step2([params...]))in Step3
RE:
Have you tried using the Advanced Query View?It allows you to see the entire code of the transformations you've made. If you copy all the code from there, go to a new query, open its Advanced Query Editor, and paste the code, it will apply all the steps automatically to the new query!Here's a link to Microsoft's documentation that explains more about it: https://learn.microsoft.com/en-us/power-bi/transform-model/desktop-query-overview#advanced-editor
RE:
Yeah, this would be so much nicer. Maybe have a flag in the UI to only show fields used in relationships, so that you can actually see them. Then have the lines going to the fields themselves, or be annotated at each end with the field name.
RE:
This is already present in the underlying data model, and editable from tabular editor. Surfacing it in the PowerBI field selector UI would be awesome.
RE:
The new concept of Perspectives really would help here. Let's hope that matures properly and actually becomes useful.
RE:
This is already in the underlying data model, and you can edit it in tabular editor; however it is not shown in the field selector/data model in power BI. Adding as a tooltip it would be awesome.
RE:
WHT = withholding tax, forgot to point that :)
RE:
*The title says Page.Run(), but that's not the case. Page.Run() does show the filter pane, but then again we cannot use it as a lookup
RE:
This something that drives me crazy - I have managers asking me to run a manual refresh, because they have made multiple changes to sales pipelines and need to see the impact immediately due to an upcoming call. I already have the latest refresh time/date stamped on each report, and have a manual refresh button - but the only person this works for is me. Being able to authorise specific users to run the refresh would speed up the process for the managers and give me some time back!