Unable to load - filter default values not available

Q&A
,
1

Hi, I have an analyses with about 7 visuals and 2 datasets. There’s a ‘date’ filter and it has been working fine for over half a year. Now I changed the ‘from’ date to ‘dynamic’ (start of this year) The analyses is still working fine but when I publish it, I get this error. (Unable to load - filter default values not available) When I press (on the desktop) the refresh/F5 button, it works fine. Does anyone have an idea ? Kind regards, Derk

2

Hi @Derk, welcome to the Quick Sight Community, here are a few steps you can try to resolve the “Unable to load - filter default values not available” error you’re experiencing upon publishing:

  1. Check Dataset Configuration: Ensure that your datasets have the necessary date fields available and that they cover the dynamic date range you’ve set (from the start of this year to the present). Sometimes, if the dataset doesn’t have entries for the entire range, it can cause issues with dynamic defaults.

  2. Validate Filter Settings: Double-check the filter settings in Quick Sight. Make sure that the dynamic date setting is correctly configured to reflect “start of this year” and that it aligns with the data available in your datasets.

  3. Clear Cache and Refresh: Sometimes, Quick Sight might have issues due to cached data. Try clearing your browser cache or using the Quick Sight application in incognito/private browsing mode to see if the issue persists.

  4. Re-publish the Dashboard: After making the necessary adjustments, try republishing the dashboard. Sometimes, re-publishing helps reset any configuration issues.

  5. Inspect Permissions: If the dataset or any related resources have changed, ensure that the necessary permissions are still in place for Quick Sight to access all the data it needs.

  6. Use Static Dates Temporarily: If the dynamic date continues to cause issues, try reverting to static dates temporarily to identify if the dynamic setting specifically is causing the problem.

  7. Contact Support: If none of these steps resolve the issue, consider reaching out to AWS support. They can provide more detailed guidance and might be able to identify issues specific to your account or setup.

It’s crucial to ensure that the dynamic date filter is not only set correctly but also compatible with the way your datasets are structured and updated. This type of error typically relates to how the data is being accessed and whether all necessary data points are available for the dashboard to function correctly.

Did this solution work for you? I am marking this reply as, “Solution,” but let us know if this is not resolved.

Thanks for posting your questions on the Quick Sight Community!

3

Hi, thanks for response. I’ve tried all of the above several times last week, nothing worked. The analyses works fine, but as soon as I publish it, it goes wrong. Incognito, fixed date, another dynamic date, filter only on 1 visual, filter only on 1 dataset, didn’t help. The last one was selecting ‘custom select visuals’ on the filter in stead of ‘default all’, this solved the issue. (for now :slight_smile: )

4

Thank you for letting us know. I would recommend filing a case with AWS Support where we can dive into the details so that we can help you further. Here are the steps to open a support case. If your company has someone who manages your AWS account, you might not have direct access to AWS Support and will need to raise an internal ticket to your IT team or whomever manages your AWS account. They should be able to open an AWS Support case on your behalf. Hope this helps!