Populating parameters on report before query executes

[heilamckinley]

I have a Power BI report using Direct Query to a SQL Server database.  Users will access this report via an app.  On the report is a table with a number of columns.  I want the user to open the report and populate some parameter values (e.g. "Date from", "Date to", "Customer name", "Status") and those values to be used as input to the query before it runs.  In other words the table must be empty until the user has populated the parameter fields and clicked on a button to trigger the query execution.  Is this possible in Power BI?

[v-nmadadi-msft]

Hi @heilamckinley 

I wanted to check if you had the opportunity to review the information provided. Please feel free to contact us if you have any further questions.

Thank you.

[heilamckinley]

Hi @danextian 

Thank you for the informative article.  I have two questions:
1. I don't want to create a table with possible values for my parameter, I want the user to type in a value.  Is this possible?

2. The article states Dynamic M query parameters aren't supported on Power BI Report Server.  Does this mean I cannot use this functionality in an app?

[v-nmadadi-msft]

Hi @heilamckinley  ,

Power BI doesn’t currently allow users to type in parameter values directly in the report view the way you might in traditional tools (like SSRS). Dynamic M query parameters require the values to come from a field or slicer in the data model.

Dynamic M query parameters are supported only in Power BI Service  when using DirectQuery mode. They are not supported in Power BI Report Server.

So if you’re publishing to an app that’s based on the Power BI Service (workspace - > app), then yes, you can use dynamic M parameters there. But if your environment uses Power BI Report Server, this functionality won’t work.


I hope this information helps. Please do let us know if you have any further queries.
Thank you

[rohit1991]

Hi @heilamckinley 

This is expected right now ,OneLake folder-level security is still in preview, and it doesn’t fully work inside OneLake Explorer for Windows. Even if you’ve assigned folder-level RBAC roles, users will see blank folders unless they have read access at the Lakehouse level. The RBAC permissions do work correctly within Fabric (for example, in notebooks, pipelines, and the Lakehouse browser), but Explorer doesn’t yet honor those fine-grained permissions. Also, users with broader roles like Member, Contributor, or DefaultReader may override folder-level rules.

Colud you please try below steps:-

• Enable OneLake Security (Preview) for your Lakehouse.

• Give users Lakehouse-level Read access if they need Explorer visibility.

• Use Fabric RBAC for now ,full folder-level access support in Explorer will come in future updates.

[danextian]

Hi @heilamckinley 

If the data is imported, it isn't possible. This is somehow possible with dynamic M query parameters if the storage mode is Direct Query - Dynamic M query parameters in Power BI Desktop