Skip to main content

#Tableau Server97 人正在讨论

Hello 

SnowFlake offers 2 types of OAuth  -  Standard OAuth and External OAuth with an IDP 

 

OnPrem Tableau Server 2025.1 requires user upon expiration to refresh Credentials under MyAccountSettings. 

 

Is there any configurations/alternatives  where users do

not

have to refresh tokens manually in MyAccountSettings with OAuth?  

 

#Tableau Server

3 个回答
  1. 今天,09:49

    Hi @Henry Collins

     

    is this an AI sourced answer ?  On Tableau Server 2025.1, there's nothing that stops the oauth refresh token from eventually expiring, and when it does, the user has to reauthenticate manually; no setting removes that. 

    It is nice to contribute to the Tableau Community forum but please share knowledge that you have experienced or implemented personally. 

     

0/9000

Hi Team, 

Requirement: Display data dynamically based on the selected Period Type parameter

  • Day
    • When the user selects Day in the Period Type parameter, the Order Date parameter should display all available dates.
    • The most recent available date should be selected by default.
  • Week
    • When the user selects Week, the Order Date parameter should display only the Monday date of each available week (e.g., 27-Jul-2026, 20-Jul-2026, 13-Jul-2026).
    • Upon selecting a week, the report should display data for the entire Monday-to-Sunday period corresponding to that week.
  • Month
    • When the user selects Month, the Order Date parameter should display all available months.
    • The latest available month (e.g., Jul-2026) should be selected by default.
  • Quarter
    • When the user selects Quarter, the Order Date parameter should display all available quarters.
    • The latest available quarter (e.g., 2026-Q3) should be selected by default.
  • Custom Dates
    • When the user selects Custom Dates, the following parameters should be displayed: 
      • Start Date
      • End Date
    • Report data should be filtered based on the chosen date range.
  • Lifetime
    • When the user selects Lifetime, all available data should be displayed without applying any date filters.
  • #Tableau Agent

#Tableau Desktop & Web Authoring  #Tableau Server  #Tableau Cloud  #Tableau Public  #Tableau  #Tableau Prep  #Tableau Community Updates

5 个回答
  1. 今天,07:45

    You can handle this with a Period Type parameter and calculated fields using DATETRUNC for Day, Week, Month, and Quarter. For Week, truncate to Monday and filter the data from Monday through Sunday. Use separate Start/End Date parameters for Custom Dates, and bypass date filtering for Lifetime. Dynamic parameter values can be used to default to the latest available period. 

0/9000

UPDATE: Republishing a workbook seems to make my missing dashboards reappear briefly, before disappearing again -- see below.  

 

I published a series of dashboards on Tableau Server and now can't locate any of them. After publishing the dashboards, I placed them in a Collection, then decided to move them to a Project, and shared the links with my manager. 

All of the links still work, but the collection, project, and my default space are all empty. My recycle bin contains some old dashboards, but none of the current ones. 

 

I have no idea where they're currently located. Can anyone help? I can re-publish them and distribute new links, but I'd like to avoid this kind of problem in the future.  I'd also appreciate insight into the differences between projects and collections.  

 

#Tableau Server

10 个回答
  1. 昨天,14:52

    In case anyone else runs into this:  

    I learned from our IT department that we have both  internal and public server spaces. I had originally (unknowingly) published to the internal server and later was (unknowingly) viewing content on the internal server, which is why the dashboards didn't appear. The only way to distinguish the 2 spaces is the URL. 

     

    Thanks to all who weighed in. 

     

0/9000

Hi,  

I'm trying to embed a Tableau Dashboard into a Sharepoint page. I have ironed out connection and permissions issues and all is now working well.. expcept.. when somebody first lands on the Sharepoint page instead of seeing the dashboard they see a "Sign in to Tableau" server message / button. If they press this, the dashboard is then displayed, without the need for them to enter any further credetials. So its not a huge issue, but also not a great user experience. Does anybody know a way I can prevent the Tableau sign in page stage please? 

 

#Tableau Server

2 个回答
  1. 昨天,12:31

    Hi @Nigel Smith

     

    Do you have SAML authentication with Microsoft EntraId enabled on your Tableau Server Instance?

    If yes, then try this command. 

    tsm configuration set -k wgserver.saml.iframed_idp.enabled -v true 

    If you have another use case, Trusted Authentication or Connected Apps authentication would help.

0/9000

Hi Team, 

Below is the requirement. 

 

Display data based on the user's parameter selection: 

 

  • Day: When the user selects Period type Parameters Day, Order Data Set  paramters need display all available dates. By default, the latest date should be selected.
  • Week: When the user selects Period type Parameters Week, display only the Order Data Set  paramters Monday date of each week (e.g., 27-Jul-2026, 20-Jul-2026, 13-Jul-2026). When a week is selected, display data for all days within that Monday–Sunday period.
  • Month: When the user selects Period type Parameters Month, display all available months. By default, theOrder Data Set  paramters latest month should be selected (e.g., Jul-2026).
  • Quarter: When the user selects  Period type Parameters Quarter, display all available quarters. By default, the latest quarter should be selected (e.g., 2026-Q3).
  • Custom Dates:  When the user select Period type Parameters Display two parameters:
    • Start Date
    • End Date
  • The data should be filtered based on the selected date range.
  • Lifetime: When the user selects Lifetime, display all available data without any date restrictions.

I have attached the twbx file. 

Regards, 

Venkat​‌

 

 

 

#Tableau Desktop & Web Authoring  #Tableau Cloud  #Tableau Server  #Tableau Public  #Tableau  #Tableau Community Updates

6 个回答
  1. 昨天,06:15

    Hi, 

    I hadn’t heard back from you after my previous reply — is it alright to consider that earlier question resolved? 

     

    If so, please close the previous thread (mark it as the Accepted Answer), and I’ll continue supporting you. 

     

    <Past article>  

    https://trailhead.salesforce.com/trailblazer-community/feed/0D5KX00000jAN1c0AG

     

     

     

    Looking at your current requirements, it seems that when a date is selected, a list of dates should appear, and the latest date should already be selected. In this setup, will the date be a single‑select field? 

    Hi, I hadn’t heard back from you after my previous reply — is it alright to consider that earlier question resolved?

     

     

     

     

0/9000
1 个回答
  1. 7月26日 15:53

    Hi Erik, 

     

    That error message actually tells you the real problem: Tableau Server's response is sending two different X-Frame-Options headers

    — one DENY and one SAMEORIGIN — and browsers block the frame completely when they see conflicting values like that. 

     

    Likely cause: Tableau Server adds SAMEORIGIN by default. Something else in front of it — a proxy, load balancer, or WAF — is probably now also

    adding DENY. Since this used to work, something likely changed recently on one of those layers (a Tableau upgrade/restart, or a new security rule). 

     

    Quick way to check:

    Look at the response headers in your browser's dev tools (Network tab) or run curl -I on the URL, and see how many X-Frame-Options headers come back. 

     

    Fix: Only one layer should set this header — work with your network/security team to remove the duplicate. If needed, you can turn off Tableau's own header with:

    tsm configuration set -k wgserver.clickjack_defense.enabled -v false

    tsm pending-changes apply

    One more thing worth knowing: since Salesforce and Tableau Server are different domains, SAMEORIGIN won't actually allow the embed anyway. The proper long-term fix is a Content-Security-Policy: frame-ancestors header that explicitly allows your Salesforce domain — X-Frame-Options can't do that kind of allowlisting. 

     

    Hope that helps point you in the right direction!

0/9000

 I am using a dynamic axis title controlled by a parameter (e.g., QTD, YTD) along with a subtitle (e.g., Actual, Prior, Growth). While it displays correctly in the default, unfiltered view, an issue occurs after publishing to Tableau Server version 2026.2.2 (20262.26.0625.1400). 

 

Specifically, the subtitle disappears under two conditions: 

 

When a user applies a filter. 

 

When a user with restricted access (Row-Level Security) views the dashboard. 

 

Under these conditions, only the main axis title is visible, and the subtitle is entirely missing. 

 

Axis subtitle disappears when filters or RLS are applied.

 

Filters or RLS applied.

Screenshot 2026-07-13 085908.png

  I am utilizing the MIN(0) dual-axis workaround. Could this setup be causing the rendering bug?  

 

Screenshot 2026-07-13 091706.png

 

 

 

#Tableau Server

1 个回答
  1. 7月26日 15:42

    Hi Danh, 

     

    Good catch mentioning the MIN(0) workaround — that's likely the real cause here, not a Server bug. 

     

    Why it happens: With MIN(0), the subtitle is just a text label on a hidden dummy mark, not a true axis property. If a filter or RLS reduces the data for that pane to zero rows (or the underlying calc returns NULL), Tableau simply has nothing to plot — so the label silently disappears. Your main title stays because it's likely a straight parameter reference, not dependent on a mark being drawn.

    Common triggers:

    • The subtitle calc (Actual/Prior/Growth) returns NULL once rows are filtered/RLS-restricted
    • RLS often behaves like a context filter, which can affect even FIXED LOD calcs
    • "Growth" especially needs a prior period — if that period gets filtered out, there's nothing to compare

    How to confirm:

    Reproduce the same filter/RLS condition in Desktop. If the subtitle disappears there too, it confirms it's a data issue, not a Server rendering bug. 

     

    Fixes to try:

    1. Wrap the subtitle calc in ZN()/IFNULL() so it always returns a value
    2. Check if your filters/RLS are set as context filters — this can break FIXED LOD assumptions
    3. Make sure the field driving the MIN(0) mark always has at least one row, regardless of filter/RLS state
    4. Alternatively, skip MIN(0) and insert the calculated field directly into the worksheet title — titles aren't tied to marks being drawn, so this failure mode goes away entirely

    Try it in Desktop first — that'll tell you which fix is needed.

0/9000

 

We are using a black background, and the default table scrollbar is very hard to see (almost invisible). 

 

How can I change the color of the scrollbar in a table? 

 

#Tableau Server

2 个回答
  1. 7月26日 10:00

    You can style the scrollbar with CSS so it’s more visible against the black background. Try setting a lighter color for the scrollbar thumb and a darker shade for the track using ::-webkit-scrollbar selectors. If the table is a framework component, check its theme or custom CSS options, as some components handle scrollbar styling differently.

0/9000

Hi. When working on a visualization in Tableau Public, an error suddenly appeared. I closed the visualization I was working on and tried to reopen it. However, this error keeps popping up:Error After Trying to Open a Visualization

Is there anything I could do to fix this error? 

 

 

#Tableau Server  #Tableau Public  #Tableau

2 个回答
  1. 7月26日 04:53

    Hello @Etsuro Tabata.  

     

    I'm sorry, I should have commented on this before, but after a few hours, the error message stopped popping up, and I could edit my visualizations again. Also, I wasn't using Tableau Desktop, as I was using the Tableau Public website to make visualizations. Thank you for answering though! 

     

    Nicky

0/9000

Hello Tableau Support, 

 

Our security scanning tool, has identified three Critical vulnerability findings against our Tableau Server environment: 

 

1. CVE-2025-30065 – Apache Parquet Java 

2. CVE-2026-40478 – Thymeleaf expression injection / SSTI 

3. CVE-2026-41901 – Thymeleaf expression injection / SSTI 

 

Tableau Server version: 20262.26.0603.1643 

TSM version: 20262.26.0603.1643 

 

For the Thymeleaf findings, we have confirmed that the currently running Tableau Content Exploration Service contains the following vendor-supplied component: 

 

/mnt/tableau/tableau_server/data/tabsvc/contentexploration/0/webapps/content-exploration/WEB-INF/lib/thymeleaf-spring6-3.1.2.RELEASE.jar 

 

The Content Exploration Service is configured and currently running: 

 

Tableau Server Content Exploration Service: 1 instance 

Status: Running 

 

The corresponding Tableau package is: 

 

/opt/tableau/tableau_server/packages/contentexploration.20262.26.0603.1643/content-exploration.war 

 

The deployed JAR was created or deployed as part of the current Tableau Server 2026.2 installation. 

 

Could you please assess each of the following CVEs against this exact Tableau Server version and build? 

 

CVE-2025-30065 

CVE-2026-40478 

CVE-2026-41901 

 

For each CVE, please confirm: 

 

1. Is Tableau Server 2026.2 build 20262.26.0603.1643 affected or exploitable? 

 

2. If Tableau is affected: 

   - What is Tableau's planned remediation? 

   - Will the remediation be delivered through a maintenance release, hotfix, or a new Tableau Server release? 

   - What is the expected fixed Tableau version? 

   - What is the estimated release date or remediation timeline? 

   - Is there a Tableau-supported temporary mitigation or workaround that we can apply while waiting for the fix? 

 

3. If Tableau is not affected: 

   - Could you please provide a formal written statement confirming that this Tableau Server build is not affected? 

   - Please include the technical reason, such as whether the vulnerable code path is not used, not reachable, or cannot receive attacker-controlled input. 

 

These findings are rated Critical by our security platform, so we would appreciate an impact assessment and remediation timeline as soon as possible. 

 

Looking forward your response. Thanks! 

 

#Tableau Server

2 个回答
  1. 7月24日 06:12

     I’d recommend opening a Tableau Support case with the exact build number and CVE details. Since these are bundled third-party components, Tableau Support should confirm whether they are actually exploitable in this version and provide an official statement or remediation timeline. Include your scanner report and the affected JAR paths to help them investigate quickly. 

0/9000