In Tableau 2020.4, a bug was introduced that causes a calc in the VizAlertsConfig workbook to always come back as NULL instead of FALSE. This prevents any alert from being triggered via a "test_alert" comment. All admins using VizAlerts who are upgrading to Tableau Server 2020.4 will need to edit the _is_validschedule calc in the VizAlertsConfig workbook so that it reads:
[subscription_id] < 0 // this is a test alert, so that's okay
// naming pattern to recognized VizAlerts schedules. feel free to edit.
// Note that the schedules MUST be set to "disabled" in Tableau Server--this is required by the Custom SQL connection
// ... which you should NOT change.
OR CONTAINS(LOWER(schedule_name), LOWER([schedule_name_filter]))
The first line is the only thing that changed. This alteration introduces no other side effects, so it is safe to make.
A new version of the VizAlertsConfig workbook will need to be released with the next VizAlerts release.
In Tableau 2020.4, a bug was introduced that causes a calc in the VizAlertsConfig workbook to always come back as NULL instead of FALSE. This prevents any alert from being triggered via a "test_alert" comment. All admins using VizAlerts who are upgrading to Tableau Server 2020.4 will need to edit the _is_validschedule calc in the VizAlertsConfig workbook so that it reads:
The first line is the only thing that changed. This alteration introduces no other side effects, so it is safe to make.
A new version of the VizAlertsConfig workbook will need to be released with the next VizAlerts release.