Alert on in anaysis calculated field

We are having issues with alerts in Quick Sight analyses.
If the alert is related to a calculated field within the analysis,
it is automatically disabled repeatedly.
If the alert is related to a calculated field in the dataset, it works fine.
Unfortunately, not all calculations are possible in the dataset.
Do you have any tips for us on how to solve this problem?

Hi @JuliaFee

When you create a calculated field in the dataset, row-level calculations are physically stored in SPICE memory if the dataset uses SPICE. This means the calculations are precomputed and stored. Calculated fields created within an analysis are dynamically computed in real time each time the analysis is loaded. They are not pre-stored. Because analysis-level calculated fields are dynamic and may change, if you remove, edit, or save changes to such a calculated field, any alerts depending on it may become disabled.

When you create an alert in Quick Sight, the service monitors your data for threshold breaches based on your dataset’s refresh schedule. For SPICE datasets, alerts are evaluated after each successful SPICE data refresh.

Please refer to the below documentations this might be helpful for you.

2 Likes

Does that mean, warnings cannot be set on gadgets with analysis-level calculated fields at all?

Hi @JuliaFee

Yes, this is a current limitation. Alerts on visuals that use only analysis level calculated fields are generally not supported. This is because analysis-level calculated fields are dynamically computed at runtime, which makes alerts on them unreliable.

To ensure stable and reliable alerts, we recommend moving your calculations to the dataset level. Dataset-level calculated fields are precomputed and stored, allowing alerts to function as expected.

Hi @JuliaFee,

Following up here as it’s been awhile since last communication took place on this thread; did you have any additional questions regarding your initial post?

If we do not hear back within the next 3 business days, I’ll close out this topic.

Thank you!

Hi @JuliaFee,

Since we have not heard back further, I’ll go ahead and close out this topic. However, if you have any additional questions, feel free to create a new post in the community.

Thank you