Forum Discussion
Feature Request: UI to set Parameters in Report Settings or via a Visual
In PowerBI desktop it is possible to set a parameter using Transform Data->Edit Parameters
These can be useful in essense creating global variables that are not set through DAX or that don't have to be loaded in tables. Presumably they could be set via URL in the right context as well.
Right now, in the PowerBI Service to change a parameter you have to go into PowerBI Settings and then go to semantic models and expand the sematic model for a given report and then there's a parameters section.
That is a fairly obscure place to put parameter editing/setting for a report.
If the parameters could be settable at a per report that uses a model level (that is overriding what is set in the model) then having the ability to set the report level overrides in the Report Settings panel would be an easier place to set the parameter values.
For more dynamic parameter setting, in order to allow more dynamic user interaction to set the parameters, having a parameter editor visual that provides inputs (with defaults set) for the parameters would be useful for run-time (Read-View) parameter setting.
The parameter tech as it stands is interesting but feels under-supported especially in the PowerBI Service.
It should be possible to set parameters within a Report as easily as it can be done in the PowerBI desktop environment.
You need to distinguish between static parameters and dynamic parameters.
Static parameters are designed to be only used by the report developer and the semantic model owner, mostly for Import Mode sources. Most of the time they are used to change the data source. These parameter changes will only take effect after the next refresh.
Dynamic M Query parameters are filtered report columns that reach back into the data source query but only in Direct Query Mode. The developer binds the parameter to a column, and the report user is unaware of that.
Giving report users access to parameters in Import mode is pointless as these report users should never be allowed to initiate a semantic model refresh.
Giving report users access to parameters in Direct Query mode is mostly duplicating existing functionality.
1 Reply
- lbendlin
Super User
You need to distinguish between static parameters and dynamic parameters.
Static parameters are designed to be only used by the report developer and the semantic model owner, mostly for Import Mode sources. Most of the time they are used to change the data source. These parameter changes will only take effect after the next refresh.
Dynamic M Query parameters are filtered report columns that reach back into the data source query but only in Direct Query Mode. The developer binds the parameter to a column, and the report user is unaware of that.
Giving report users access to parameters in Import mode is pointless as these report users should never be allowed to initiate a semantic model refresh.
Giving report users access to parameters in Direct Query mode is mostly duplicating existing functionality.