Could you ensure that your field names in the viz have leading spaces? We'll be making this a non-requirement in the future, but for now it's just one of those "gotcha" behaviors people run into from time to time.
Yes my field have space.
If I put only ' Email To *' vizAlert - show advanced settings.
If i put ' Email To *' and other dimension : ' Email To *', ' Email Body *', ' Email Subject *' - vizAlert shows simple alert.
In attachment i send my twbx file, log from vizAlert and vizAlert.py file.
Thank you for your help
Thanks for attaching those. I took your workbook and altered the email address for To, added the other required columns, so that it looks like this:
I then published to Tableau server, and tested the alert, and got the expected result:
I attached my version of your workbook that ran successfully. Does it work for you?
cp.twbx 906.0 KB
I went through the same steps as Matt and I also see all the emails being sent on my server. Would it be possible for you to share the .\temp\20160324075342_cp-mail.csv that was written out as part of the run that you sent? I suspect that there's something in the file that is causing VizAlerts to miss it as an Advanced Alert.
Unfortunately, for me, it is still wrong.
I published your twbx file - just changed email address to my address and still is send as simple alert ;(
In attachment i send log file, csv ,png file and install_guide - based on the instructions in attachemnt I installed everything.
My version of python is 2.7.9:
Can You send me your vizallert.py file - maybe my file is bad ?
Thank you for your help
Your fields are getting merged into a single column in your CSV. That's bizarre...it's semicolon delimited rather than comma delimited. I'm not sure why that would be? What version of Tableau Server are you running? Have you customized your configuration in any way?
Also, I already diffed your .py file with the current version on GitHub. There were just the logging changes you made plus the smtp port change, so it looks fine. Something is causing your system to use semicolons rather than commas though, that's the part we need to figure out...it seems as though Tableau Server might be exporting it that way for some reason.
Today I installed version 9.3 - yesterday I had a 9.2
Matt I changed list separator in regional settings in all users on registry from ; to , and now is ok.
Works as Advanced settings.
But in Poland list separator default is ; and this ; shoud by setting in regional settings to other programs run currect.
Is possible to You change , upgrade vizAlert to works with ; and with , ?
1 of 1 people found this helpful
Well that's good to know! Makes total sense now.
As to how to make this work for users in countries where the standard delimiter is semicolon, I'm not sure I have a quick answer. I created an issue to investigate it.
One way might be to edit the code where we read / write CSV files and pass in an explicit delimiter character to use, e.g. on line 114:
self.csv_reader = csv.reader(f, delimiter=';', **kwargs)
I doubt that's all you would have to change, and I haven't tested that at all so it will probably break things, but it might be a start.
Matt I upgrade py file - 114 line i repleace this line to : self.csv_reader = csv.reader(f, delimiter=';', **kwargs) and is work fine.
Tomorrow, I check it thoroughly - I think that will be ok after this change.
Thank you very much for your help.
I am too facing this problem.
On the dev server 9.3 we installed vizalerts and it works fine with advanced alerts.
We then installed a new server 9.3 and installed vizalerts and tried the same vizalerts advanced alert but it does not work.
The same trigger view is working in dev but does not work in SIT.
I am getting the trigger view itself in email.
What should I be doing different?
Hard to say without seeing your viz, Shelly...but usually this is because the " Email Action *" field is missing the leading space, or the field is missing entirely. Can you share the CSV (just the headers) so I can see what fields are there?