Embed for your customers scenario (auth by app). How to emulate persistent filters ?

[EduardD]

Persistent filters is a great feature that can be used in Embed for your organizaiton scenario. It stores user filters, bookmarks, sorting order, etc. applied between sessions. 

I am looking for guidance on how to emulate persistent filters ( for the 'Embed for your customers' scenario, where the app is responsible for authenticating users.
Is it technically possible? 
Thank you in advance. 

[SaiTejaTalasila]

Hi @EduardD ,

You can refer this article -https://learn.microsoft.com/en-us/javascript/api/overview/powerbi/enable-persistent-filters

I hope it will be helpful.

Thanks,

Sai Teja 

[rohit1991]

Yes, it is technically possible to emulate persistent filters in the "Embed for your customers" scenario. Since the app handles user authentication, you can implement a backend service to store user-specific filter settings, bookmarks, and other preferences.

Here’s how:

1. Capture Filters: Use the Power BI JavaScript API to capture the applied filters and states when the user interacts with the report.
2. Save Settings: Store these settings in your database, mapped to the authenticated user's ID.
3. Apply Filters: Retrieve and apply the saved settings during subsequent report loads using the JavaScript API.

This approach effectively mimics persistent filters for embedded scenarios.

[EduardD]

@rohit1991  Can we use bookmarks instead? so every 5 minutes bookmark the state of page user is on and save it to the database? also create bookmark when user is exiting page?
Then apply bookmarks when user navigates to specific page?

Can we track through using JavaScript API when user is navigating between pages to apply the rigth bookmark from database?

[EduardD]

@rohit1991 thank you. 
We predominately use slicers in the dashboard not filters, I have 10 pages in the report. 
if you know, how should the solution to be designed: javascript code to visit [for each user openned the report] all 10 pages slicers every 5 min to collect the slicers' states and save it to the database? So when user opens next time all that slicers to apply to all the pages during report openning? Can we catch in the code what page is open in the UI for specific user to save only those slicers states?