Hey Cody, sorry to hear you're having issues. I haven't run 1.1 against the latest build. I'll check it out and let you know if I'm able to reproduce the problem. If anything, I'm guessing it is related to Tableau Server repository database changes. We might be able to fix it simply by updating the query in your config file.
Thanks for the quick reply Matt. I look forward to hearing if you are able to reproduce the issue. We already tried rebooting the VM and restarting Tableau server just to make sure there weren't any issues a quick reboot would take care of.
So far, five alerts have processed succesfully for me, running Server 10.4 and VizAlerts 1.1.1. So there might be something specific to the alert you've built that is running into issues. If you like, email me your zipped VizAlerts folder (after removing or redacting any sensitive info you don't want me to have), and I can take a look to see what might be going on. If it literally says "Unable to render VIZ_IMAGE(/Workbook/View) with error:" in there, then it may be an issue with how you built the viz specifically, because that value would almost never work in a content reference anyway.
1 of 1 people found this helpful
The problem is not with VizAlerts and 10.4, but with your content reference. It is specified as:
Rather, it should be:
Fix that, and your alert should work.
Thank you Matt!! Those values have had the preceding forward slash since creation and had worked without issue all the way to 10.4. Removing them restored alert functionality.
Ah, thanks for confirming that! I had wondered if that was the case. I'm not sure why it would have changed with 10.4, though, as I can't get a viz to render with the double-forward slash all the way back to 9.3. Might be in combination with using trusted authentication, perhaps. Regardless, glad it's working for you now.