Hello,
I’m running into an issue where a parameter that’s linked to a field in my dataset (not static list) is not updating automatically after my SPICE dataset refresh (full and incremental). The dataset is refreshing successfully, and the field values are definitely there but the parameter still only reflects the old values. I need to MANUALLY refresh the parameter at the BI level for the changes to take effect. I don’t believe the responsibility to manually update the parameter should fall on the user every time the dataset refreshes.
As a workaround, I tried using a direct query dataset with a SELECT DISTINCT to feed the parameter control but I’m not sure this will actually work and to be honest it isn’t a viable long-term solution and won’t work if I have multiple parameters linked to a field.
Is there a proper way to force the parameter to sync with the dataset field upon refresh?
Would like to hear if anyone has found a sustainable workaround or if this is something the QuickSight team plans to address in the near future.
EDIT: I think this issue is related to all filters, not just parameter based filters
Hi @shirley,
I just ran a simple test of this scenario; I took a sample dataset and using the ‘country’ field, I added a couple additional rows with data assigned to new countries that were not in the dataset. After updating the dataset in QuickSight, and reloading the analysis, the new values populated in my parameter control.
So it seemed to work in my testing scenario, do you have any type of cascading filter setup on the control? Or any other specific details you may be able to include? Is the parameter setup on the dataset or analysis?
Thanks, but your test doesn’t reflect the issue. It seems you either manually refreshed the analysis and/or used direct query - in both cases, the new values would appear immediately.
The issue I’m raising is specific to SPICE datasets:
Even after a full or incremental refresh, parameters (in this case in the analysis level) linked to dataset fields do not update automatically. The new values are present in the data, but the parameter control stays outdated until I manually refresh it at the BI level. This defeats the purpose of dynamic filters and puts unnecessary burden on the dashboard author.
This happens across multiple dashboards and is very reproducible. Would appreciate a solution that doesn’t rely on manual workarounds or switching to direct query.
Hi @shirley,
Apologies for missing your last response; I’ll keep this tagged as a feature request to promote visibility to the AWS support team; hopefully this is something that can be implemented soon!
