-
Notifications
You must be signed in to change notification settings - Fork 91
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
The Advanced function data into VIZ_CSV() report #170
Comments
Hi, This is expected behavior. The VIZ_CSV() content reference is pulling down all the fields used in the visualization (everything on Columns, Rows, Pages, and the Marks card) so that includes the Email fields. What you need to do is build two views: one that has the email fields and is subscribed, and the second that has the content for the VIZ_CSV() content reference with just the fields you want included in the attachment. I'm sorry this wasn't clear in the documentation, if there's something that you can point at to help us clarify that distinction for Advanced Alerts we'd be glad to add it! Jonathan |
Hi Jonathan, Thanks |
Take a look at the VizAlertsDemo workbook test alerts https://github.com/tableau/VizAlerts/blob/master/docs/install_guide.md#put-vizalerts-through-its-paces-test... The VizAlertsDemo/AdvancedAlerts view shows a number of Advanced Alerts that have been configured. This view has the Email fields and then the content references are pointing at other views (which happen to be in this workbook, but could be entirely other workbooks). Jonathan |
Hi Jonathan, Thanks |
Hi Jonathan, 2020-10-19 10:32:14 - [ERROR] - HTTP error getting vizdata from url Thanks |
Hi, a 404 error in this case means that the VizalertsDemo workbook either hasn't been published, or was published under a different name, or there aren't sufficient permissions to access the workbook. A good test is to a) copy the URL from the log, b) in your web browser log into Tableau Server using the VizAlerts run-as user, and c) then paste the URL in to go to that. If you can't log in or see the URL from your web browser using the Vizalerts run-as user then VizAlerts won't be able to either, and you'll need to diagnose what's going on. Jonathan |
re: your earlier post with the screenshots there's too little information for me to see what's going on and help you. For example I can't see the values of the Email Action, Email Subject, Email Attachment, etc. fields. So let me try to give you an example from our production configuration of VizAlerts: For one of our projects the use case is to email out a set of dashboards as PDFs on a monthly basis to some users. The configuration is as follows:
The VIZ_PDF() content reference that is in the Email Attachment District 2 field is pointing to views in another workbook in the site, in this case the full content reference is something like VIZ_PDF(ZambiaMalariaReportingDashbords/Risk-Overview-District?District=ce%20%Chibombo%District).
I hope this helps! My suggestion for you from here would be to:
Regards, Jonathan |
The 404 link is https://xxxxxx.edu/views/VizAlertsDemo/Product?Region=West&:format=pdf&:refresh=y. But I can open the demo file in tableau with the below link: https://xxxxxx.edu/#/views/VizAlertsDemo_15955180561540/DataForDownload?:iid=3 I see the difference between these two links is the #/ before the views missing in the error link Any thoughts? Thanks |
The VisAlertsDemo is under the Explore / Default |
Hi, The two URLs you gave are actually different views (first is Product, second is DataForDownload) from different workbooks (first is VizAlertsDemo, second is VizAlertsDemo_15955...). For VizAlerts to run and pull content references the referenced workbook/viewname has to match exactly. My guess is that the Viz Alerts Demo workbook was already published (and perhaps removed?) from Tableau Server, and then the one that you are accessing now was published at a later time because the added _########### to the end is standard behavior for Tableau when two workbooks are published with the same name. (The first workbook with that name uses the workbook name, the second workbook gets a unique # appended to the name). There are a couple of options here to use the VizAlertsDemo workbook: One is to make sure that you have access to the original VizAlertsDemo workbook, the other would be to update the content references in the trigger view of the VizAlertsDemo workbook to point to it's new workbook name of VizAlertsDemo_15955... Jonathan |
Hi Jonathan, |
It seems the VIZ_CSV() didn't point the correct view. |
Hi, the VIZ_CSV() reference is just the workbook/viewname, so VIZ_CSV(PreBillingDEV102120/Pre-billEstimatedBill) or something like that (I'm not sure if the =Pre-billEstimatedbill is actually part of the view name or an attempt at adding a URL parameter as a filter). |
I tried the reference name get from the tableau view link which is PreBillingDEV102120/Pre-billed_Estimated_Bill?:iid=2 that worked. Thank you so much for your help. |
The additional question: |
Hi,
When I set up the advanced email, the Email Action, Email Subject, Email body, and Email Attachment are in the details with the report data on the same page. (see screenshot #20). If these Advanced tabs do not in the details then the Advanced alerts don't work.
In the tableau report, the data is fine. (see screenshot #21).
When I received the vizalerts notification email with the attached CSV file, the CSV file report data include Email Action, Email Subject, Email body, and Email Attachment data. How did this happen?
Please advise.
Thanks
The text was updated successfully, but these errors were encountered: