Forum Discussion
report builder parameters "select all"
Good day!
I am using Report Builder v.15.7.1814.616.
I have several multi-value parameters which I've established in my main DataSet Query Designer.
I have researched online and recommended suggestions for the parameters to default to "All" have been something like this:
- Open Parameter Properties: In the Report Data pane, expand Parameters, right-click the desired multi-value parameter, and select Parameter Properties.
- Ensure Available Values are Set: In the Available Values tab, make sure you are pulling values from a dataset (e.g., GetParameters dataset) and that you have a "Value" field (e.g., ID) and a "Label" field (e.g., Name).
- Set Default Values:
- Click on the Default Values tab.
- Select the Get values from a query radio button.
- Select the exact same dataset used in the "Available Values" tab.
- Select the Value field (e.g., ID).
This (and other suggestions) do not work.
I attribute it to the fact that I have created the parameters in Query Designer as opposed to custom SQL (which I am not able to use). Other than the values being pre-populated, the parameters behave as expected (eg; cascading effect, etc.)
Any other suggestions or recommendations?
Thanks!
~San
Hו sanpanico
The issue you are encountering is likely a Circular Dependency or a Query Designer Metadata Mismatch. When parameters are created via the Query Designer (especially for Power BI Datasets or Analysis Services), the designer often links the dataset and the parameter in a way that prevents the "Default" list from initializing before the "Available" list is filtered.
1. The Root Cause: Dependency Loops
In the Query Designer, if your dataset MainDataSet generates the parameter Param1, and you then try to use MainDataSet (or a dependent child dataset) to populate the defaults for Param1, the report engine encounters a logic loop: it cannot fetch default values for a parameter from a dataset that is itself waiting for that parameter to be defined.2. The Solution: Independent Helper Datasets
To resolve this without writing custom SQL, you must create a dedicated "Helper" dataset for each parameter's default values that does not share filters with the main query.Create a New Dataset: Right-click Datasets -> Add Dataset.
Use the Query Designer: Open the Query Designer for this new dataset.
Isolate the Dimension: Select only the field you need for the parameter (e.g., ID or Name). Do not add any filters or related dimensions that would link this query to your existing parameters.
Map the Defaults:
Go to Parameter Properties -> Default Values.
Select Get values from a query.
Choose this new, isolated "Helper" dataset.
Set the Value field to the unique ID.
3. Synchronization Check (Internal Query Designer)
The Query Designer has its own internal parameter mapping that can override Report Builder settings.Open your main dataset in the Query Designer.
Click the Parameters icon (usually a small filter icon with a subscript 'p' or a specific button in the toolbar).
Ensure that the "Multiple Values" checkbox is checked inside the Query Designer table, not just in the Report Builder Parameter properties. If these are out of sync, the "Select All" instruction from the Default Values tab is ignored.
4. Data Type Validation
Query Designer often defaults values to Text (String) even if the underlying data is Integer.Check the Data Type in the General tab of Parameter Properties.
If your "Available Values" dataset returns Integers but the parameter is set to Text (or vice versa), the "Select All" match will fail silently. They must match exactly.
If this post helps, then please consider Accepting it as the solution to help the other members find it more quickly
5 Replies
Hו sanpanico
The issue you are encountering is likely a Circular Dependency or a Query Designer Metadata Mismatch. When parameters are created via the Query Designer (especially for Power BI Datasets or Analysis Services), the designer often links the dataset and the parameter in a way that prevents the "Default" list from initializing before the "Available" list is filtered.
1. The Root Cause: Dependency Loops
In the Query Designer, if your dataset MainDataSet generates the parameter Param1, and you then try to use MainDataSet (or a dependent child dataset) to populate the defaults for Param1, the report engine encounters a logic loop: it cannot fetch default values for a parameter from a dataset that is itself waiting for that parameter to be defined.2. The Solution: Independent Helper Datasets
To resolve this without writing custom SQL, you must create a dedicated "Helper" dataset for each parameter's default values that does not share filters with the main query.Create a New Dataset: Right-click Datasets -> Add Dataset.
Use the Query Designer: Open the Query Designer for this new dataset.
Isolate the Dimension: Select only the field you need for the parameter (e.g., ID or Name). Do not add any filters or related dimensions that would link this query to your existing parameters.
Map the Defaults:
Go to Parameter Properties -> Default Values.
Select Get values from a query.
Choose this new, isolated "Helper" dataset.
Set the Value field to the unique ID.
3. Synchronization Check (Internal Query Designer)
The Query Designer has its own internal parameter mapping that can override Report Builder settings.Open your main dataset in the Query Designer.
Click the Parameters icon (usually a small filter icon with a subscript 'p' or a specific button in the toolbar).
Ensure that the "Multiple Values" checkbox is checked inside the Query Designer table, not just in the Report Builder Parameter properties. If these are out of sync, the "Select All" instruction from the Default Values tab is ignored.
4. Data Type Validation
Query Designer often defaults values to Text (String) even if the underlying data is Integer.Check the Data Type in the General tab of Parameter Properties.
If your "Available Values" dataset returns Integers but the parameter is set to Text (or vice versa), the "Select All" match will fail silently. They must match exactly.
If this post helps, then please consider Accepting it as the solution to help the other members find it more quickly
Miss Fainshtein, thank you for the solution.
Especially the "Isolate the Dimension..." part, was quite helpful!
I was not able to implement all aspects of Step 3 unless I switched form DAX to MDX, which impacted other things, but all in all, this solution worked! Many thanks!
~San
This has worked for me and the thing that stands out to me is your comment of "I attribute it to the fact that I have created the parameters in Query Designer".
Normally how i would achieve what you are describing is that ill create a dataset that comes up with the parameter values. I then create a parameter (which you'll see in the folder parameters when its made) that uses the dataset much like your screenshot.
Now inside the dataset that is building your records that you want on the report, inside the query designer you create the filter at the top as normal but click the left checkbox where it says "Parameters". After clicking ok, in the left menu of the dataset properties, go to "Parameters". You should see the filter condition now appearing in this list and from the "Parameter Value" dropdown menu, you should be able to link it to the parameter you created earlier.
Hi sanpanico,
Thank you for reaching out to Microsoft Fabric Community.
Thank you Anonymous and Ritaf1983 for the prompt response.
As we haven’t heard back from you, we wanted to kindly follow up to check if the solution provided by the user's for the issue worked? or let us know if you need any further assistance.
Thanks and regards,
Anjan Kumar Chippa
Hi @sanpanico,
We wanted to kindly follow up to check if the solution provided by the user's for the issue worked? or let us know if you need any further assistance.
Thanks and regards,
Anjan Kumar Chippa
