Unable to change Parameters in Workspace semantics.

[rnola16]

Hi all,

I have a semantic model that uses parameters on a report that is published to a workspace. As an admin I'm able to make changes on the parameter values and run them. I'd like to have users access the same report and change parameter values ( dates, ID, regions) in workspace.

Issue:

- Except me every other user sees the options to change the parameters grayed out, it asks you to 'Take Over' the report from the original creator.

How can these reports be made avaiable to 300+ users, so that they can run their own parameter values ? 

Haven't found a solution to this anywhere. Appreciate if anyone had similar situations ( bet there are ).

Thanks.

[v-pagayam-msft]

Hi @rnola16 ,
May I ask if you have gotten this issue resolved?
If it is solved, please mark the helpful reply or share your solution and accept it as solution, it will be helpful for other members of the community who have similar problems as yours to solve it faster.

Thank you.

[rnola16]

Basic query:

Select   A.ssn, A.birth-dt

From  Emp A where A.ssn in ( '"&param_ssn&"') and A.birth_dt between '"&Start_dt&"' and '"&End_dt&"'.

This is using teradata as data source, custom SQL, direct query and the table has 15bill records.

I'd like the query to have the user input parameters and running it on the dat source. Haven't found any solutions, can Power BI handle large datsets and user defined input parameters ?

[rnola16 · Accepted solution]

Was able to configure the reason in the M code. Able to work it out with Mass Filter.

[lbendlin]

Only if all possible values of your query parameters are known and loaded in import mode. Sounds like your scenario is not allowing that 

[rnola16]

I do not want to load 'all possible values'. Its a simple 'where' clause with user defined inputs.

[lbendlin]

If this is important to you please consider voting for an existing idea or raising a new one at https://ideas.fabric.microsoft.com

[v-pagayam-msft]

Hi @rnola16 ,
Thanks for sharing the additional details. Since you have already explored options like Dynamic M Query Parameters and report slicers, and are still running into limitations which didn't provided the resolution.I would recommend you to raise a support ticket for Fabric and Power BI, kindly follow the steps outlined in the following guide:

How to create a Fabric and Power BI Support ticket - Power BI | Microsoft Learn

Hope this helps.If so,consider acceptin git as solution.

Thank you for being a part of Microsoft Fabric Community Forum!

Regards,
Pallavi.

[nandic]

@rnola16 
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

[rnola16]

Report 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).

[v-pagayam-msft]

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.

[v-pagayam-msft]

Hi @rnola16 ,
I wanted to check in on your situation regarding the issue. Have you resolved it? If you have, please consider marking the reply that helped you or sharing your answer and Accept it as Solution. It would be greatly appreciated by others in the community who may have the same question

Thank you for being a valued member of the Microsoft Fabric Community Forum!

[v-pagayam-msft]

Hi @rnola16 ,
Thank you for reaching out to the Microsoft Fabric Community Forum about the issue you are encountering.

Thank you @lbendlin and @Deku for the prompt response.As @lbendlin suggested, Yes,Dynamic M Query Parameters allows users to dynamically change parameter values.Users may not need to "Take Over" the report to make parameter changes.Refer the link for detailed undersatnding

If this post helps, please give us Kudos and consider Accept it as a solution to help the other members find it more quickly.

[lbendlin]

Issue:

- Except me every other user sees the options to change the parameters grayed out, it asks you to 'Take Over' the report from the original creator.

That is not an issue, that is a security feature.  You do not want anyone else but the semantic model owner to mess with that.

[Deku]

 If you have 300 users, you wouldn't want them to all to constantly changing parameters. Unless direct query a refresh is required to see the changes. What are you trying to achieve?

[rnola16]

We have a some templates designed for users and we would like users to use them with their choice of parameters

[lbendlin]

That's what .pbit and template apps are for.

Also consider dynamic M query parameters.

Service settings are off limits to non-developers.

[rnola16]

But pbit cannot be published in workspaces. Was able to create dynamic M query parameters but the same issue persists once I have them in PBI workspace.

[Deku]

Tabular editor 

Power BI API

[rnola16]

Can users be able to change the parameters dynamically ?