We have a customer who claims filter changes applied for a table visualization are persisting, but then reverting at a later time. • ‘Primary’ filter is for the lowest grain of the table, and is used to refine the list. Last checked, it had approximately 105 items selected to display • There are other filters in the visualisation, but they all only have one item selected • User says that on multiple occasions they updated the filter - i.e. checked additional items - then saved, then confirmed in the visualization and the dashboard that the filter changes were working as desired • Then at a later time - the next day - the visualisation had reverted the filter selection, or at least did not include the most recently added items • This user is the only one editing this visualization - any changes were applied by them only Does this look like a limitation in how the GoodData engine applies the filter(s)? Is there any way to evaluate how this could be happening?

Based on the information in the knowledge sources, there are several factors and known behaviors in GoodData Cloud that could explain why filter changes for a table visualization appear to persist initially but then revert at a later time: 1. Saved Views and Filter Persistence - If the user is using Saved Views, these are personal and tied to the dashboard and user. When a Saved View is set as default, it should persist the filter state across sessions. However, if "Auto-save last state" is enabled, it takes priority over the default Saved View, and the dashboard will open with the filters as they were last left by the user. If neither is working as expected, it could be a bug or a configuration issue. Also, Saved Views do not include cross-filters, and adding new filters to a dashboard can reset filter values to "All" when a Saved View is applied, which may cause confusion if the dashboard structure changes after the view is saved [Saved Views](https://www.gooddata.com/docs/cloud/create-dashboards/filters/saved-views/). 2. Local Storage and Filter State - Filter selections are saved in the browser’s local storage. If the user clears their browser cache, uses a different browser or device, or if local storage is otherwise cleared, the filter state may revert to the dashboard default or the default Saved View [Add Filters to Dashboards](https://www.gooddata.com/docs/cloud/create-dashboards/filters/). 3. Recent Bugs and Backend Fixes - There have been recent bugs where Saved Views or filter states were lost after workspace updates or API changes, but these have been addressed in backend updates. If the issue persists, it may be worth checking if the workspace is up to date and if any recent updates or API calls (such as layout uploads) could be affecting the persistence of filter states [Slack thread on Saved Views loss](https://gooddataconnect.slack.com/archives/C01UR5BGAHY/p1736371710679099?thread_ts=1736371710.679099&cid=C01UR5BGAHY). 4. Known Issues with Filters and Views - There are known issues where filter context or attribute filter IDs are not set correctly (e.g., using a label instead of the primary attribute ID), which can cause Saved Views or filter states to behave unexpectedly. If the filter context is not referencing the correct attribute, the view may revert or not apply as expected [Slack thread on filter context IDs](https://gooddataconnect.slack.com/archives/C01UR5BGAHY/p1752090833644959?thread_ts=1752090833.644959&cid=C01UR5BGAHY). 5. No Out-of-the-Box Persistence for Embedded Dashboards - If the dashboard is embedded (e.g., via React SDK), there is no out-of-the-box functionality to persist filter state per user between sessions. Custom logic is required in the embedding application to store and reapply filter selections [Slack thread on embedded filter persistence](https://gooddataconnect.slack.com/archives/C04S1MSLEAW/p1715943560687789?thread_ts=1715943560.687789&cid=C04S1MSLEAW). Recommendations: - Confirm whether the user is relying on Saved Views, local storage, or another mechanism for filter persistence. - Check if any dashboard structure changes (e.g., adding/removing filters) occurred between sessions. - Ensure the filter context is referencing the correct attribute IDs. - If the issue persists, it may be a bug or a backend issue—recent fixes have addressed similar problems, so updating to the latest backend and SDK versions is recommended. - If the dashboard is embedded, custom logic may be needed to persist filter state. If none of these scenarios match the user's workflow, or if the problem continues despite following best practices, it may be necessary to escalate the issue to GoodData support with detailed reproduction steps, as there have been recent bugs and backend fixes related to filter and Saved View persistence. Let me know if you need more specific troubleshooting steps or want to share additional details about the dashboard setup or embedding method.

Hi Eoghan, The response from our AI assistant seems accurate. However, if this does not help resolve the issue , kindly share some more details on this like screenshots, steps to reproduce and a direct link to the report to help us investigate this further. Thanks.