refreshData() does not invalidate client-side cache after OData call in Analytics Designer

Diana1234 — Thu, 09 Apr 2026 15:15:32 GMT

In an SAP Analytics Cloud Analytic Application built with Analytics Designer, a table widget displays records filtered to status "Not Reviewed". A button triggers an OData service call via ODataService.getEntity() which updates the status of selected records to "Reviewed" in the backend. After the OData call completes successfully, a refreshData() is executed — both at widget level (tbl_Detail.getDataSource().refreshData()) and at application level (Application.refreshData()).

The backend update is confirmed to be successful: when the full page is reloaded and filters are re-applied manually, the processed records no longer appear in the table. However, after refreshData() — whether triggered via script or via the native story refresh button — the records remain visible in the table. Only a complete browser page reload causes the records to disappear.

Re: refreshData() does not invalidate client-side cache a...

N1kh1l — Fri, 10 Apr 2026 07:35:51 GMT

@Diana1234

In SAP Analytics Cloud (SAC) Analytics Designer, refreshData() typically refreshes the widget's view based on the current client-side cache. If you change the filter selection manually does it bring the fresh data ? Unfortunately there is no scripting API to refresh the cache. Just see if removing a filter can workaround a reload of cache.

Table_1.getDataSource().setDimensionFilter("Your_Dimension", "DummyValue");
Table_1.getDataSource().removeDimensionFilter("Your_Dimension");

Nikhil

Question Re: refreshData() does not invalidate client-side cache a... in Technology Q&A

refreshData() does not invalidate client-side cache after OData call in Analytics Designer

Re: refreshData() does not invalidate client-side cache a...