Forum Discussion
visual interaction across report pages
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
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