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 dateJoin us for an expert-led overview of the tools and concepts you'll need to become a Certified Power BI Data Analyst and pass exam PL-300. Register now.
Hi , I have created custom date range picker . Filtering across report pages works fine . I have a problem to keep state of pressesd button across report pages. In my custom visual I have few custom buttons in a row and at the end two input fields for custom date (start and end date range). The button pressed on any page should be the same while moving between pages mean visually should be pressed ( different background) . Thanks for any advice . Bart.
Solved! Go to Solution.
Hi @Anonymous,
Filters are the only visual types that can persist their state across pages, and this is filtering information only. For anything such state that doesn't relate to the filtering criteria directly, you don't have a standard way of sharing this information. This is because all visuals are functionally separate from each other and should not be able to communicate with their other instances for security reasons; the two current exceptions are filter criteria if you're supporting slicer sync and using the local storage API.
Bear in mind the limitations with the local storage API, if you're considering it: the main ones being that you must request that your visual be whitelisted by the custom visuals team and that your visual is certified in AppSource.
Regards,
Daniel
Proud to be a Super User!
On how to ask a technical question, if you really want an answer (courtesy of SQLBI)
Hi @Anonymous,
Filters are the only visual types that can persist their state across pages, and this is filtering information only. For anything such state that doesn't relate to the filtering criteria directly, you don't have a standard way of sharing this information. This is because all visuals are functionally separate from each other and should not be able to communicate with their other instances for security reasons; the two current exceptions are filter criteria if you're supporting slicer sync and using the local storage API.
Bear in mind the limitations with the local storage API, if you're considering it: the main ones being that you must request that your visual be whitelisted by the custom visuals team and that your visual is certified in AppSource.
Regards,
Daniel
Proud to be a Super User!
On how to ask a technical question, if you really want an answer (courtesy of SQLBI)
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 |
---|---|
8 | |
7 | |
2 | |
2 | |
2 |
User | Count |
---|---|
6 | |
5 | |
4 | |
4 | |
4 |