Upon expanding the use of field parameters - I have discovered a limitation to the 'extended field parameter controls' that I believe would be of great benefit to anyone designin dashboards and packs that are intuitive and highlighy customisable with the 'reader' in mind.
For exable - say you have either a Budget or Forecast data set, controlling several elements on the page and being run viw data parameters - the functionality itself if great however the LABEL is only as dynamic as to the point where the report is LOADED into view .. and NOT based on the selections then made within the dashboard by the reader.
This means that dynamic labelling (such as Actual, Budget, Variance as opposed to Actual, Forecast, Variance or any derivative of the comparator column, or other things such as rolling months etc can't be done, and stuck with headers that aren't explicit.
My suggestion is to make the LABEL portion of the field parameter as dynamic as the rest of the field parameter mechanics. It honestly feels like a 'bug', but only in as far that I'm using field parameters in some highly complex scenarios to make the dashboard really clean and slick - so has likely been an oversight on the controls.
miguel
on:
Disable a Single Query inside a Dataflow Gen2
on:
Feature Request: Python notebooks should support c...
on:
Page-Level Conditional Formatting Rules in Power B...
on:
Data Source Connections - Display Created Time and...
on:
Replace All that are Not a Value