Power BI is turning 10! Tune in for a special live episode on July 24 with behind-the-scenes stories, product evolution highlights, and a sneak peek at what’s in store for the future.
Save the dateEnhance your career with this limited time 50% discount on Fabric and Power BI exams. Ends August 31st. Request your voucher.
Hi Team,
We have one requirement to select value in slicer from URL Query string parameter .
as per current functionality , we can have URL query string paremeter which will apply page level filter on report and based on that values will be populated in Slicers and other visuals.
Is there any workaround or any process available in which , from URL query parameter we can have slicer selection instead of applying page level filter.
Thanks
Hi @Anonymous ,
Sorry to disturb you...
But did I answer your question ? Please mark my reply as solution. Thank you very much.
If not, please upload some insensitive data samples and expected output.
Best Regards,
Eyelyn Qin
Hi @Anonymous ,
URL filtering is applied to report pages. So I’m sorry to tell you that your requirement might not be achieved currently...
Did I answer your question ? Please mark my reply as solution. Thank you very much.
If not, please upload some insensitive data samples and expected output.
Best Regards,
Eyelyn Qin
Hi. You can't change that functionallity. I'm sorry but query filtering is for page level filter only. In Power Bi Service you can't. Maybe Power Bi embed have something for that, I'm not sure.
Regards,
Happy to help!
Thanks @ibarrau for your response.
It will be good if we have feature like this in power BI services to have selection in slicer based on Query string parameter. Because if it is achivable then lot of use cases can be achivable.
Or if we can do other operations apart from filtering from query string parameter.
Thanks
Check out the July 2025 Power BI update to learn about new features.
This is your chance to engage directly with the engineering team behind Fabric and Power BI. Share your experiences and shape the future.
User | Count |
---|---|
30 | |
19 | |
19 | |
13 | |
13 |
User | Count |
---|---|
30 | |
20 | |
19 | |
18 | |
16 |