VizAlerts

@Toby Erkson​ 

Hi, what if you go to your content and check if there is any subscriptions or alerts:

If this post resolves the question, would you be so kind to "Select as Best"?. This will help other users find the same answer/resolution and help community keep track of answered questions. Thank you.

Regards,

Diego Martinez

Tableau Visionary and Forums Ambassador

Hi,

This is a use case for Advanced alerts... assuming there are 50 PDF exports to 50 different people here's what you'd do: build a trigger view with 50 rows where the Email Attachment field has a VIZ_PDF() content reference that has the filter condition in the URL parameter and the Email To field includes the recipient(s) for that country. Then subscribe that trigger view to one of the VizAlerts subscriptions.

Jonathan

Hi @Sunitha Pratipati​ There is very limited information in your post, but the first thing I would suggest is duplicating your view as a crosstab. Whatever that crosstab looks like is what you'll get when you export. If you need additional assistance, please provide the workbook where this issue is occurring.

Hope that helps!

Esther Aller

If I helped, please mark the question as answered :D

Hi,

There's nothing in the toolbar that's going to create this interaction automatically for you, there are just too many ways the interactivity might go.

The reason why most of your searches would turn up filter actions is because a) that's all we had for a long time with Tableau for actions and b) filter actions can do two things: filter the data in the target view (worksheet or dashboard or specific sheets on a dashboard)) and if the target view is different from the current view then jump to that view.

Tableau has since added set actions, parameter actions, go to sheet actions, multiple map layers, and more that provide multiple possible solutions. To help you find the "best" one for your use case (data & desired display & interactivity) I have some questions:

1) What is the source of your spatial data? Are you using your own province & sub-province shapes, are you using Tableau's geocoding, or a combination of both?

2) Are the province & sub-province data in the same Tableau data source or different data sources?

3) When a user clicks on a province and drills to the sub-province level does that need to jump to an entirely separate dashboard or separate worksheet (that would have its own separate URL) or are you wanting a "drill in place" option where the click filters the map and the sub-province level is displayed?

4) What is the desired interactivity if the user does a click&drag and selects multiple provinces?

5) Once the user is at the sub-province level what can the user do next? For example do you want to enable the user to go "back" to the province level to choose another province to drill into?

Jonathan

Hi,

FYI VizAlerts comes with both an executable version and the raw Python code. That is described in the VizAlerts documentation along with answers to your other questions at https://github.com/tableau/VizAlerts. You'll start with the Install Guide and then once VizAlerts is up and running then use the User Guide to build alerts.

I'll add a word of caution: VizAlerts is not a point & click tool, it was built by Tableau Server admins for Tableau Server admins & power users. Also VizAlert is a free/open source tool and there is no support guarantee so VizAlerts admins & users need to be able to be self-guided and make use of the available resources. In addition Tableau Server admins need to be comfortable editing config files and working across multiple pieces of software (Tableau Server, Tableau's authentication environment, VizAlerts, Tableau's PostgreSQL, Tableau workbooks, the mail server). If that doesn't seem like a fit for you & your team then I'd suggest looking at other options.

Jonathan

Hi, the Tableau 2023.1 release made a couple of changes that are affecting VizAlerts, here they are:

https://github.com/tableau/VizAlerts/issues/203 (probably the one you're experiencing, you can change the SQL in the VizAlerts trigger view per the comments)

https://github.com/tableau/VizAlerts/issues/208 (a separate issue w/trusted tickets)

Jonathan

That's the gist, but let me expound a bit and add some caveats!

1. One thing to do first is use the trusted tickets test to repro the issue you are having. This gives you basis for engaging Support, who will reject any ticket that has to do with VizAlerts (as it is community-supported, not Tableau-supported). This also sets you up to test your changes in non-prod to ensure it solves the issue (ideally you'd upgrade non-prod and have a repro there too), and make sure it's resolved after the change.
2. I would not reset to default as your command example would do. I would try and make sure you have the right value from what it was before (if you set it yourself at some point). The value may still actually exist in your config, so simply using tsm configuration get for the same config key would be a good way to check the existing value. Ideally you would be recording config changes you make that you could use to refer back to what the original setting was--if you do, I definitely recommend you use that value.
3. I would, during an outage window (and ideally having tested the change in a non-prod environment) do the tsm config change and simply re-specify the same value that's already in there / the value you know it was set to previously. Use the tsm config set command to do so, and you'll have to apply changes and then restart, of course. Then use the trusted tickets test page from Step 1 to test the connection again. If successful, VizAlerts should work at that point.
4. If your trusted tickets test still fails, I would recommend engaging Support to assist (and again, don't mention VizAlerts, focus on the trusted auth failing).