#Tableau Server100 discussing

It is possible through dynamic zone visibility. you need to set up a calculation which assigns a value (number) to the group your user A or B belong to. Like Manager or Employee group.  

Say Manager group is assigned value 1 and employee group Value 2. manger sees Dashboard A and Employee see Dashboard B. Put Both Dashboards in separate containers  inside another dashboard and then use this Boolean calculation to operate in DZV mode.  

Value=1 and set it up in dashboard under Layout to control visibility.  

what will happen, Manager logs in value is set to 1 he sees Dashboard A. 

When employee logs in the calculation turns false as Value=2 and it not equal to 1 so Employee will see Dashboard 2. Try. :-) 

@Rami Reddy Jaggavarapu

Yes! Use a public trusted CA certificate on the proxy/load balancer for external users, and use TLS again from the proxy/load balancer to Tableau Server. Tableau documents this as a supported pattern. It also says internal or self-signed certificates can be used to encrypt traffic between Tableau Server and internal computers: 

The important part is that the proxy/load balancer must trust the backend Tableau certificate. If you use a self-signed cert, import that cert or its internal CA/root cert into the proxy/load balancer trust store. Do not disable backend certificate validation in production.

Best practice is to use an internal CA-issued certificate instead of a one-off self-signed certificate. It is easier to rotate, audit, and manage across nodes.

Also confirm these Tableau settings are correct when running behind a proxy/load balancer:

gateway.public.host = public Tableau URL 

gateway.public.port = 443 

gateway.trusted = proxy/load balancer IP or CNAME 

gateway.trusted_hosts = proxy/load balancer hostnames/aliases

If SSL is used from the proxy to Tableau Server, Tableau SSL must be configured on Tableau Server as well: https://help.tableau.com/current/server/en-us/ssl_config.htm

For SAML/OIDC setups, make sure the proxy preserves the correct forwarded headers, especially X-Forwarded-Proto: https, otherwise authentication redirects or SAML validation can fail: https://help.tableau.com/current/server/en-us/saml_requ.htm

Avoid exposing Tableau Server directly to the internet. Tableau’s hardening guidance recommends keeping Tableau Server inside the corporate network and using a reverse proxy for internet clients: https://help.tableau.com/current/server/en-us/security_harden.htm

Hi @Willys Jimenez

if you are Tableau Server Admin, it is something you already know because you get frequently user complains, as well as notifications that processes were down. 

 But if you want to go into details and have facts, if you do not have any OS / Hardware level monitoring in place (for example Grafana), which would be ideal, then have a look at this tableau utility "Logshark" to audit your instance, based on logs activity: 

https://tableau.github.io/Logshark/

I'm sorry I'm not aware of the existence of a clear health check guide. All my knowledge comes from fragmented pieces of information over the years as well as on-the-job experience. 

Maybe you can watch

Hi @Willys Jimenez

If you mean right now, then with 2025.3 you can only use Tableau Agent to help you build your viz https://help.tableau.com/current/pro/desktop/en-us/desktop_einstein.htm or design your flows https://help.tableau.com/current/prep/en-us/prep_einstein.htm

Based on the product roadmap calls I attended, Bring Your Own LLM and Dashboard Narratives (so Ask questions about your data through Agent) are in the queue for TS v. 2026.2 / 2026.3.

Hi @Hasan Mustafa

, 

Sorry for the delay in answer but.... 

Your hints are obviously helpful but it took me a couple of days to prove it. 

At first I created a card with tableau support team, why not? 

Tableau support team verified our configuration and pinpointed that snowflake odbc driver version is wrong. How come? I have verified BOTH servers provide the same output: 

~

-q -d -n "SnowflakeDSIIDriver" 

[SnowflakeDSIIDriver] 

... 

DriverODBCVer=03.52 

... 

RTM leads to a different driver and different output.... 

I am still not 100% sure if that works as my complaining user is coming back next week. 

Keep fingers crossed. 

Hi @Praveen Pandey

Do you really have a previous installation attempt / existing instance ? 

But as a side note, it seems that you are using a Linux user called "tableau" with sudo access for the installation. "tableau" is per default a reserved user name that the installation will try to create so that's not going to work directly. 

So some context would be nice.

@Rashmi Punde

Hi, as explained before this is a cache problem. 

What you can do besides what has already been explained?  

a. If working directly into Tableau Server/Cloud UI: 

You can add to the end of your url the option :refresh=yes. E.g:

Then you can add to bookmarks the link in your browser, and you will avoid to pushing the refresh button. 

b. If you are working with an embed scenario, then you can add a custom parameter to the embed code:

<tableau-viz id="tableauViz"       
  src='https://my-server/views/my-workbook/my-view'>
<custom-parameter name=":refresh" value="yes"></custom-parameter>
</tableau-viz>

If this post resolves the question, would you be so kind to "Accept this Answer"?. 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 Tableau Ambassador 

Hi there Veera,

The issue of the "Export All" extension working on Tableau Desktop but failing on Tableau Server with a blank Excel file is likely due to data size limitations, server permissions, or performance constraints. Since the dataset contains 21 columns and over 76,000 records, Tableau Server may be hitting memory or timeout limits, preventing the export. To troubleshoot, first, try reducing the number of records using filters and test if the export works. If a smaller dataset exports successfully, the issue is likely related to server resource constraints. Additionally, ensure that the extension is enabled in Tableau Server settings, and check if the Trusted Sites List includes the domain hosting the extension. Server security policies may also restrict data exports, so verifying the Data Interactivity permissions is essential. Another possible cause is browser cache issues, so testing in a different browser or clearing the cache might help. If the problem persists, checking Tableau Server logs for errors related to export failures could provide insights. As an alternative approach, you can use Tabcmd to export data programmatically, bypassing the extension's limitations. If you need further assistance in debugging Tableau Server logs, I can guide you through the process.

tabcmd export "WorkbookName/SheetName" --csv -f "output.csv"

Thanks

Deepak

If it Helps, Please mark it Best and upvote to help others

Hi @Adams Ali

Tableau Server stores master data, meta data and events within its own internal Postgres Repository. 

Access this database is allowed if enabled. So you can mimic the admin views or create your own custom views. Here is the help page.  

For example you can look at table public.historical_events to the most recent activity using a type of your choosing. You can also join with workbooks, views, projects tables etc... 

it is a pretty common topic so you will find also lot of additional information online. 

Have a look.