Check your eligibility for this 50% exam voucher offer and join us for free live learning sessions to get prepared for Exam DP-700.
Get StartedDon't miss out! 2025 Microsoft Fabric Community Conference, March 31 - April 2, Las Vegas, Nevada. Use code MSCUST for a $150 discount. Prices go up February 11th. Register now.
On my report, I have a slicer that determines which metric is displayed on the line graph. All other visuals on the page are set for "No Interaction" using the edit interactions function. Upon report reload, the visuals that should not be interacting, are being filtered by the slicer. changing the selection in the slicer will enable all visuals to display appropriately. After which, you are able to change your slicer to the preffered option, and everythings works accordingly.
Img 1: report launched
Img 2: Toggled 2nd option in slicer
Img 3: All options selected in slicer
Img 4: Limited to 1 selection in slicer
Img 5: Interaction setup (there are many shapes placed as backgroup components and multiple card visuals, hence the multiple interaction options for a metric)
Solved! Go to Solution.
Hi @andrew_wellman ,
It sounds like you're encountering an issue with how the slicer interacts with the parameter in your Power BI report. Here are some of my personal thoughts:
1. Parameters in Power BI can sometimes behave differently compared to direct measures, especially when it comes to interactions and filtering. Since your primary metric is stored in a "Metric" parameter that switches between measures, this could be causing the unexpected behavior upon report reload.
You can look at this document:
Solved: Dynamic Parameter is not working with the slicer w... - Microsoft Fabric Community
2. Even though you've set the visuals to "No Interaction," the parameter might still be influencing the visuals indirectly. This could be due to how parameters are processed during the report's initial load.
If you want to learn more about it, I think you can look at this document:
Solved: Default value for parameter, connected with slicer... - Microsoft Fabric Community
Best Regards
Yilong Zhou
If this post helps, then please consider Accept it as the solution to help the other members find it more quickly.
Hi @andrew_wellman ,
It sounds like you're encountering an issue with how the slicer interacts with the parameter in your Power BI report. Here are some of my personal thoughts:
1. Parameters in Power BI can sometimes behave differently compared to direct measures, especially when it comes to interactions and filtering. Since your primary metric is stored in a "Metric" parameter that switches between measures, this could be causing the unexpected behavior upon report reload.
You can look at this document:
Solved: Dynamic Parameter is not working with the slicer w... - Microsoft Fabric Community
2. Even though you've set the visuals to "No Interaction," the parameter might still be influencing the visuals indirectly. This could be due to how parameters are processed during the report's initial load.
If you want to learn more about it, I think you can look at this document:
Solved: Default value for parameter, connected with slicer... - Microsoft Fabric Community
Best Regards
Yilong Zhou
If this post helps, then please consider Accept it as the solution to help the other members find it more quickly.
I should also add that this is a single data source in play - no relationships.
The primary values are stored in a "Metric" parameter that switches between measures. The Compare to and Variation values are a multi-card that is also based off of the selected "Metric", but is a combination of several measures (compare value, difference, % difference)
It is interesting that the multi-card metrics are not impacted by the slicer (as expected) but the primary metric is.
Could this be because I am using a parameter to switch between the measures and should rather be using the measure itself?
March 31 - April 2, 2025, in Las Vegas, Nevada. Use code MSCUST for a $150 discount! Prices go up Feb. 11th.
Check out the January 2025 Power BI update to learn about new features in Reporting, Modeling, and Data Connectivity.
User | Count |
---|---|
144 | |
85 | |
65 | |
51 | |
45 |
User | Count |
---|---|
217 | |
88 | |
81 | |
65 | |
56 |