bug: Filters are not updating with force update if cache is enabled for some time

[pankajsoni22]

When the dashboard has a filter and responses are cached for let say 24 hours, even after force refreshing the entire dashboard, list of values in the filter do not update (considering there are new values in filter)

How to reproduce the bug

1. Go to dashboard that has dropdown filter
2. Force refresh the entire dashboard
3. If you expect new value in the filter, it will not be there.

Expected results

Updated filter value should be there.

Actual results

Updated list of values.

Environment

Caching the data for 24 hours. Using superset 3.0.1

[rusackas]

@michael-s-molina @kgabryje do either of you happen to know if the cache of the native filters is tied to the linked of the dashboard? Or if there's another way to clear/refresh the cache for the native filters?

[michael-s-molina]

@rusackas Using master, I can see that the query to retrieve the filters values is being fired but is not using the force=true parameter and will return cached values.

Screen.Recording.2024-04-05.at.14.38.09.mov

[jwdalton]

This patch seems to have fixed it for me. Now when I click "Refresh Dashboard", the refresh calls for the filters also have force=true set.

diff --git a/superset-frontend/src/dashboard/components/nativeFilters/FilterBar/FilterControls/FilterValue.tsx b/superset-frontend/src/dashboard/components/nativeFilters/FilterBar/FilterControls/FilterValue.tsx
index 5041fa3c97..2e626636c7 100644
--- a/superset-frontend/src/dashboard/components/nativeFilters/FilterBar/FilterControls/FilterValue.tsx
+++ b/superset-frontend/src/dashboard/components/nativeFilters/FilterBar/FilterControls/FilterValue.tsx
@@ -174,7 +174,7 @@ const FilterValue: React.FC<FilterControlProps> = ({
       setIsRefreshing(true);
       getChartDataRequest({
         formData: newFormData,
-        force: false,
+        force: shouldRefresh,
         ownState: filterOwnState,
       })
         .then(({ response, json }) => {

[ka-weihe]

#21234

[ka-weihe]

I have opened a PR for fixing this:
#29291