Forum Discussion
Advocate IIUnable to change Parameters in Workspace semantics.
Was able to configure the reason in the M code. Able to work it out with Mass Filter.
Resident Rockstarrnola16
The user who published the latest version of semantic model to Power BI Service is the "owner" of it.
Only this user can change credentials, scheduled refresh, parameters.
Why?
Because we can have dozens and hundreds of reports built on top of this dataset.
If everyone can come and change semantic model parameters, data would be inconsistent during day (after each refresh).
If you want to change semantic model parameters, you need to refresh semantic model in order to see changes.
Summary: only one user can be the owner of dataset and control it.
For your scenario, you should use report slicers or RLS.
Report slicers (filters): each user can open report and choose specific values.
Example: user John Johnson wants to see sales only in Europe in 2024. We would provide these slicers on the report, not on dataset level.
RLS (row-level-security): our model contains sales for all continents, but i want that John Johnson can see only sales in Europe. Other continents will not be even visible for this user.
Cheers,
Nemanja
rnola16Report Slicers and RLS are good for small data sets. These tables are huge with billions of records and if a user want to query for an ID, he should be able to query for that ID and the query run should be handled by the database and not by the report server ( in other ways QueryFolding).
Hi rnola16 ,
A workaround is to embed a Power App inside the Power BI report. This Power App can collect user inputs such as dates, IDs and send them to a database. The updated values are then stored in a database table, which Power BI references as a data source. This method ensures that queries are executed at the database level, leveraging query folding to improve performance.
Hope this helps.If so, kindly accept it as solution to help others quickly.