Skip to main content

Tableau Feed

Conecte con colegas Trailblazers. Haga y responda preguntas para mejorar sus habilidades y crear una red.
Vinh Ton ha preguntado en #Tableau Server

I tried looking in Tableau Server Repository with the following postgreSql but it only has  

an "Update Schedule" = historical_events.historical_event_type_id 

when I change the settings of the schedule. 

 

There is no new event recorded when I change the name of the schedule 

 

select h.id, historical_event_type_id, details, created_at, hist_actor_user_id, hist_schedule_id

,hs.*

,e.*

FROM historical_events AS h

LEFT JOIN hist_schedules AS hs ON h.hist_schedule_id = hs.id

LEFT JOIN historical_event_types AS e ON h.historical_event_type_id = e.type_id

 

 

 

#Tableau Server  #Repository  #Administrator

1 respuesta
  1. 12 oct, 21:08

    Hi @Vinh Ton

     

    you won't find such change history or level of detail. Tableau writes name change directly in the schedules table and that's it. 

     

0/9000

I am using the Tableau table viz extension and when I click on the "Format Extension" button, the "Show Column Filters" option does not appear. Below is what I see and I have also attached a test workbook to show this. I am on the latest version 2026.2.3.  

Tableau tableau viz extension column filter option not appearing

 

This is what I would expect to see based on everything I have looked at online.  

image.png

 

Is there something else I am missing or has this functionality been removed? 

 

Thank you in advance for your help. 

 

 

 

#Tableau Desktop & Web Authoring

1 respuesta
  1. 12 oct, 19:44

    @Christie Smith looks like it's been moved to Table Settings.  Click on the icon for Table Settings, just above the column headers and you'll see the dialog box containing the function you're looking for:looks like it's been moved to Table Settings.If this response answered your question, please mark it as an Accepted Answer? 

    This way, others searching for similar solutions will find the answer faster in the future. 

    Best, Don Wise (Tableau Ambassador)

0/9000

Hello everyone 

 

I am developing a data visualization project using Tableau with a hotel dataset that contains booking records for city and resort type of hotels, and related data such as guest details, pricing, and cancellations, to name a few. 

 

I have drafted 4 visualizations which will eventually be consolidated into a single dashboard. 

 

Please visit the visualization link here. 

 

The visualizations were developed to answer these research questions (in the same order):  

 

Q1. How do cancellation rates differ by market segment and deposit type for City Hotel and Resort Hotel? 

 

Q2: How do booking volume and average length of stay change throughout the year, and does the pattern differ by distribution channel and customer type? 

 

Q3: What geographic patterns can be identified in cancellation rates across guests’ countries of origin, and what booking characteristics are associated with these patterns? 

 

Q4: What booking profiles can be identified based on lead time and waiting-list duration, and how do they differ by room assignment, customer type, repeat-guest status, and number of special requests?  

 

For each research question (visualization), may I request your feedback on (one or more of) based on these questions?: 

 

A. Is the chart type appropriate? If not, could you please recommend a more appropriate one along with what measures to use? 

 

B. Do any of the colors/color scheme need to be changed? 

 

C. Do you recommend mark labels? If so, for all, or for high/low only? 

 

D. Hovering over the visualization shows more details but does it look like cognitive overload? Would you recommend splitting the visualization into two or more instead? 

 

E. Do you have (any) other feedback or best practice using data visualization principles to improve this? 

 

Thank you very much in advance! 

 

#Tableau Public  #Tableau Desktop & Web Authoring  #Best Practices  #Reports & Dashboards

 

#Trailhead Challenges  #Trailhead

0/9000
Hanh Le ha preguntado en #Tableau Public

Hi, we are graduate students working on a draft dashboard for a data visualization course. 

  • The data cover 156 countries’ Happiness Scores (0–10) and six explanatory factors from the World Happiness Report 2019. 
  • Our research questions are: which countries are happiest and least happy, which factors are most strongly associated with happiness, and how freedom differs between the top and bottom 10. 
  • We would appreciate specific feedback on the clarity and design of our current visualizations before finalizing the dashboard.

Link:  

https://public.tableau.com/views/WorldHappiness2019WhatGoesAlongwithHappiness/Dashboard-WHR2019Overview?:language=en-US&:sid=&:redirect=auth&:display_count=n&:origin=viz_share_link

  1. Is it clear that the three scatter plots should be compared with each other (strong → moderate → weak), or does the layout need a stronger visual cue? 
  2. Do the chart types make the main findings easy to understand, or would you recommend a different visualization for any of them?
  3. Are the titles, captions, labels, and color choices clear without creating unnecessary visual clutter?
  4.  Does the sequence of the six charts create a logical story, or would you change their order before combining them into a dashboard?
  5. In the last worksheet, we compare the average Freedom to Make Life Choices score for the top 10 and bottom 10 happiest countries using a two-bar chart.      

    Is the two-bar comparison sufficient for communicating the difference, or would showing the individual country distribution with a dot plot or box plot provide more useful context without making the visualization too complex?  

Thank you for your time!

#Tableau Public

0/9000

Currently RMT is running on a separate server (Windows 2019) and whenever it's restarted the RMT statistics fail to update, sometimes restarting the MQ and RMT services works to get the statistics coming through 

 

#Tableau Server

0/9000

I have a very large workbook that has several hyper files as data sources.  I have checked each worksheet in this workbook and I do not have context filters in place.  However, every time I filter a specific hyper file by academic year, it appears to add that to context and will not change the filter when I try to change to another year.  It is also filtering other workbooks connected to that same hyper file.  For example, if I filter my large workbook to academic year 2023 and then try to show all academic years in a completely separate workbook referencing the same hyper file, it will still only show the 2023 year.  I don't understand why this is happening and I don't know how to correct it.  Has anyone else seen this behavior?  Do you know a way to correct it? 

 

#Tableau Desktop & Web Authoring

5 respuestas
  1. Ayer, 4:16

    3. **Check Live Connection Shared Paths:** 

       - If multiple workbooks are connecting live to a shared `.hyper` file on a network drive, any structural or data source modification can cross-contaminate. 

     

    I hope this helps point you in the right direction to isolate and fix the filter scope! 

0/9000

Hello All,

I’m using Tableau Desktop 2025.3 on an Apple Silicon Mac and connecting to our Tableau Server at:

https://mytableau.nameoforg.org

Issue summary:

Expected behavior:

Observed behavior:

  • fs.nameoforg.org appears to be treated as the Tableau Server during workbook open
  • Connection fails at that step

Environment:

Repro steps:

  1. Open Tableau Desktop
  2. Sign in to Tableau Server at https://mytableau.nameoforg.org
  3. Authenticate through the NYU login flow (https://fs.nameoforg.org)
  4. Return to Tableau Server and view available workbooks
  5. Select a workbook and click Open
  6. Tableau prompts for server sign-in again, showing https://fs.nameoforg.org
  7. Error appears: “Cannot connect to Tableau Server. Please check the server name and port and try again.”

I tried using agentforce to address this issue, and recommended using default browser to auth. I did the change and now this is the error that I'm getting:  

 

Unable to complete action 

Authentication failed. 

Error Code: 84223ADA 

Tableau received an OAuth error from your request.  Please see the error message for more information: Use JsonReader.setStrictness(Strictness.LENIENT) to accept malformed JSON at line 3 column 1 path $ 

See

https://github.com/google/gson/blob/main/Troubleshooting.md#malformed-json

. 

 

Can't seem to get tableau to work on macOS. I can use it on a VDI on windows but I rather use my own hardware since it is faster.  

 

#Tableau Desktop & Web Authoring

4 respuestas
  1. 10 oct, 23:59

    This looks like an SSO or OAuth configuration issue, especially since the login redirects to a different domain when opening workbooks. It may be worth checking the server’s authentication settings and redirect URLs with the Tableau admin. Hopefully, there’s a fix that lets you use Tableau Desktop on your Mac without relying on the Windows VDI.

0/9000
James Jeeves ha preguntado en #Tableau Next

My team has been testing out some Tableau Next features in an SDO and has been looking at the out of the box Individual Engagement Dashboard. We're having issues with null campaign and asset names, and because we're locked out of editing the dashboard, its component and the semantic model that it's built on, it's incredibly hard to troubleshoot the problem. The dashboard looks like this:Issues with Individual Engagement Dashboard

 

The Campaign DMO is populated and the Bulk Message Union logical view has Campaign IDs in it which map to the Campaign DMO, so they appear connected properly. I have no idea what the asset name is even meant to reference. 

 

Can anyone please give any suggestions on how to troubleshoot this or why there would be nulls here if you've experienced this issue before? It would be enormously helpful. 

 

#Tableau Next

1 respuesta
  1. 9 oct, 18:10

    @James Jeeves That dashboard and its semantic model are managed in the SDO, so you won't be able to open them and fix the join. A populated Campaign DMO doesn't mean the viz is reading that name.

    The nulls show up when the engagement row's key doesn't match the record the model uses for the name. Asset name here is the marketing content, the email or message, not a file. Check that those rows point at a campaign and an asset that actually have names. If you need a different join, build your own semantic model and dashboard. The packaged one stays locked.

0/9000

Environment:

  • Product: Tableau Server 2026.2 (20262.26.0912.1023)
  • Operating System: Windows Server
  • Deployment: 4-node Tableau Server cluster
  • Nodes 2 and 3 are configured to run Backgrounder services. Before the upgrade, each node had one Backgrounder instance. Following the upgrade, we added one additional Backgrounder instance to each node, bringing the total to two Backgrounder instances per node.

Issue Description:

The issue started immediately after upgrading Tableau Server to version 2026.2 and adding a fifth server (node5) configured as a Tableau Server Independent Gateway (TSIG) load balancer.

Node5 was subsequently removed and no longer appears in tsm topology list-nodes. However, the errors continue.

As part of the changes, we also increased the number of Backgrounder instances on nodes 2 and 3 from one to two per node. Both Backgrounder instances on each node are running normally.

The ZooKeeper client running inside the Non-Interactive Microservice Container on nodes 2 and 3 repeatedly fails TLS hostname verification when connecting to all three Coordination Service nodes.

The following error appears continuously:

java.security.cert.CertificateException: No name matching tableau-c0X found

On the Coordination Service side, the failures appear as SSLHandshakeException: certificate_unknown, occurring approximately 600 times per minute per ensemble node.

Investigation and Troubleshooting Performed:

  1. Executed tsm security rotate-coordination-service-secrets on October 2, 2026, at 20:01 UTC. The newly generated ensemble certificate is self-signed, has CN=*, and does not contain Subject Alternative Names (SANs).
  2. Confirmed that the ZooKeeper server process (appzookeeper) runs with -Dzookeeper.ssl.hostnameVerification=false.
  3. Compared the ZooKeeper client configurations used by Backgrounder and Non-Interactive services on the same node. Both have equivalent TSM-generated configurations, but Backgrounder connects successfully while Non-Interactive continues reporting hostname verification errors.
  4. Executed tsm security regenerate-internal-tokens. The command completed, but the issue persists.
  5. Confirmed that there are no pending TSM changes and that NTP synchronization is working correctly.
  6. No PKIX certificate chain validation errors have been observed.
  7. No manual modifications have been made to Tableau-generated keystores, certificates, or configuration files.

Current System Status:

All Tableau Server services are operational.

Running tsm status -v shows that all services are in the Running state. Dashboards, extracts, background jobs, and other Tableau functionality appear to be working normally.

Both Backgrounder instances on nodes 2 and 3 are functioning correctly.

However, despite all services running successfully, the TLS errors continue to be generated continuously in the background.

Impact:

The main impact is excessive log generation and disk space consumption:

  • noninteractive_node3-0.log has grown to approximately 51 GB as a single log file.
  • The appzookeeper services are generating approximately 48 GB of logs per day.
  • The continuous errors are creating unnecessary disk I/O and increasing the risk of disk space exhaustion.

Although there is currently no visible functional impact on Tableau Server, the abnormal log growth is a significant operational concern.

Assistance Requested:

We need Tableau Support's assistance to identify and permanently resolve this issue.

Specifically, we would appreciate your guidance on the following:

  1. Root cause: Why does the Non-Interactive Microservice Container fail ZooKeeper TLS hostname verification while Backgrounder, using an equivalent TSM-generated configuration, connects successfully?
  2. Supported resolution: Is there a supported TSM configuration key, documented workaround, hotfix, or patch for Tableau Server 2026.2 that resolves this behavior?

The log looks like:  

2026-10-08 22:10:28.037 +0000 13552 nioEventLoopGroup-4-29 : ERROR org.apache.zookeeper.server.NettyServerCnxnFactory - Unsuccessful handshake with session 0x0 

2026-10-08 22:10:28.038 +0000 13552 nioEventLoopGroup-4-29 : WARN  org.apache.zookeeper.server.NettyServerCnxnFactory - Exception caught 

io.netty.handler.codec.DecoderException: javax.net.ssl.SSLHandshakeException: Received fatal alert: certificate_unknown 

at io.netty.handler.codec.ByteToMessageDecoder.callDecode(ByteToMessageDecoder.java:515) 

at io.netty.handler.codec.ByteToMessageDecoder.channelRead(ByteToMessageDecoder.java:296) 

at io.netty.channel.AbstractChannelHandlerContext.invokeChannelRead(AbstractChannelHandlerContext.java:444) 

at io.netty.channel.AbstractChannelHandlerContext.invokeChannelRead(AbstractChannelHandlerContext.java:420) 

at io.netty.channel.AbstractChannelHandlerContext.fireChannelRead(AbstractChannelHandlerContext.java:412) 

at io.netty.channel.DefaultChannelPipeline$HeadContext.channelRead(DefaultChannelPipeline.java:1357) 

at io.netty.channel.AbstractChannelHandlerContext.invokeChannelRead(AbstractChannelHandlerContext.java:440) 

at io.netty.channel.AbstractChannelHandlerContext.invokeChannelRead(AbstractChannelHandlerContext.java:420) 

at io.netty.channel.DefaultChannelPipeline.fireChannelRead(DefaultChannelPipeline.java:868) 

at io.netty.channel.nio.AbstractNioByteChannel$NioByteUnsafe.read(AbstractNioByteChannel.java:171) 

at io.netty.channel.nio.NioEventLoop.processSelectedKey(NioEventLoop.java:796) 

at io.netty.channel.nio.NioEventLoop.processSelectedKeysOptimized(NioEventLoop.java:732) 

at io.netty.channel.nio.NioEventLoop.processSelectedKeys(NioEventLoop.java:658) 

at io.netty.channel.nio.NioEventLoop.run(NioEventLoop.java:562) 

at io.netty.util.concurrent.SingleThreadEventExecutor$4.run(SingleThreadEventExecutor.java:1007) 

at io.netty.util.internal.ThreadExecutorMap$2.run(ThreadExecutorMap.java:74) 

at io.netty.util.concurrent.FastThreadLocalRunnable.run(FastThreadLocalRunnable.java:30) 

at java.base/java.lang.Thread.run(Thread.java:840) 

Caused by: javax.net.ssl.SSLHandshakeException: Received fatal alert: certificate_unknown 

at java.base/sun.security.ssl.Alert.createSSLException(Alert.java:131) 

at java.base/sun.security.ssl.Alert.createSSLException(Alert.java:117) 

at java.base/sun.security.ssl.TransportContext.fatal(TransportContext.java:370) 

at java.base/sun.security.ssl.Alert$AlertConsumer.consume(Alert.java:293) 

at java.base/sun.security.ssl.TransportContext.dispatch(TransportContext.java:209) 

at java.base/sun.security.ssl.SSLTransport.decode(SSLTransport.java:172) 

at java.base/sun.security.ssl.SSLEngineImpl.decode(SSLEngineImpl.java:736) 

at java.base/sun.security.ssl.SSLEngineImpl.readRecord(SSLEngineImpl.java:691) 

at java.base/sun.security.ssl.SSLEngineImpl.unwrap(SSLEngineImpl.java:506) 

at java.base/sun.security.ssl.SSLEngineImpl.unwrap(SSLEngineImpl.java:482) 

at java.base/javax.net.ssl.SSLEngine.unwrap(SSLEngine.java:679) 

at io.netty.handler.ssl.SslHandler$SslEngineType$3.unwrap(SslHandler.java:308) 

at io.netty.handler.ssl.SslHandler.unwrap(SslHandler.java:1486) 

at io.netty.handler.ssl.SslHandler.decodeJdkCompatible(SslHandler.java:1377) 

at io.netty.handler.ssl.SslHandler.decode(SslHandler.java:1428) 

at io.netty.handler.codec.ByteToMessageDecoder.decodeRemovalReentryProtection(ByteToMessageDecoder.java:545) 

at io.netty.handler.codec.ByteToMessageDecoder.callDecode(ByteToMessageDecoder.java:484) 

... 17 more 

 

 

 

  

 

#Tableau Server

1 respuesta
0/9000

Our security team raised one vulnerability in our tableau 2024.2.13 linux server and solution require the java version to be greater than 11.0.32.0.9-1.el8. Can someone please confirm if Tableau server upgrade to version 2025.3.8 will resolve this. 

 

#Tableau Server

4 respuestas
  1. 9 oct, 10:59

    Hi @Nitesh Kumar KUSHWAHA

     

    Try v. 2025.3.10, so the september release. That's your best shot currently. It should fix a majority of these CVEs, but most likely not all at some are still impacted at Java v.17.0.16-17.0.19. Have a try. And in doubt you can always write to Salesforce InfoSecurity. Flagging doesn't mean vulnerable. 

     

0/9000