Skip to main content

#Tableau Server80 utenti parlano di questo argomento

On premise Tableau. 

 

The scheduled extract runs but does not pick upp additional csv files. 

 

I use desktop to point a datasource at a folder with csv files. The datasource is published and extract scheduled. 

 

To update the datasource with new csv files I have to run an extract from desktop. 

 

Should the scheduled extract pick upp new csv files? 

 

#Tableau Server

13 risposte
  1. 3 ago, 13:13

    Hi again Emeric, 

     

    Thank you for your suggestions earlier. I have now followed them and my system works better but one issue remains. 

     

    Current configuration: 

    1. Runas now uses a domain account "tableausa" with admin rights on the tableau server 

    2. The csv files are on the tableau server shared with

    \\tableausa\folder

    syntax. The tableausa account has permissions on the share. 

    3. 

    \\tableausa\folder\xxx

    has been added to the allowlist 

     

    I created a new datasource using tableau desktop based on one of the csv files via the fileshare, and converted to a join with a wildcard with no filtering. This works fine and if I add/remove files this is reflected in desktop workbook and datasource. 

     

    I then published the datasource without attached files. When the published datasource is opened via browser the published files are found and can be refreshed. 

     

    Then my luck ran out. I created a workbook via browser based on the new datasource. It opens and finds the published files, but I can not get it to update when files change. It can see all the data and files in the datasource as published, but refreshing to show new data does not work - I have tried F5, menu option to refresh the datasource in "sheet 1" and in the Data Source tab, and opening a new browser. 

     

    My expectation was that when opened the workbook would retrieve data from the files currently in the folder, and that the workbook user could update using menus or F5 when new files were added, but that does not work. 

     

    Do I have the wrong expectations or am I making some mistake? Is it always necessary to edit the datasource when files are added to the wildcard folder? 

     

    -Arvid

0/9000

Hi Team , 

I am brand new to Tableau , looking for some assistance on license part. I have got Tableau creator license from my team and I am able to login Tableau online/Cloud. Now I am looking for Tableau server setup, So can we use the same license to setup server also?? is my ask. 

 

Thank You 

 

#Tableau Server

2 risposte
  1. 12 ago, 00:47

    @Divya Jayachandra

     

    Hi, when you initially buy a creator license, you should be asked if you are going to use Tableau Server or Tableau Cloud.  A creator license can only be used for Tableau Server OR Tableau Cloud. It can't be used to activate at the same time Tableau Server and Tableau Cloud. 

     

    If you want to activate Tableau Server, you would need to buy another creator license, and therefore make sure to ask the Tableau Account Manager/Tableau-Salesforce partner it is a new install, and you need it for Tableau Server. 

     

    Once you have enabled Tableau Cloud or you have installed Tableau Server, you can activate Tableau Desktop and Tableau Prep Builder using LBLM 

    https://help.tableau.com/current/desktopdeploy/en-us/desktop_deploy_activate_license.htm

     

     

    On the other hand, if you are looking for the tenant portal in Tableau Cloud (Tableau Cloud Manager), your user needs to be configured as a Cloud Administrator: 

    https://help.tableau.com/current/online/en-us/cloud_manager_intro.htm

     

    https://help.tableau.com/current/online/en-us/cloud_manager_users.htm#manage-site-membership

     

     

    If you are a Cloud administrator, once you have signed in into your Tableau Cloud site, you will find a site selector in the upper left corner, just below the tableau, and the option to sign into the Cloud Manager will be enabled.  

     

    Hi, when you initially buy a creator license, you should be asked if you are going to use Tableau Server or Tableau Cloud. A creator license can only be used for Tableau Server OR Tableau Cloud.

     

    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 

0/9000

Hi, 

In my prev company we used tableau cloud and snowflake and I think automatically we had tagging on all our queries with tableau. 

Now I'm using

Tableau server with BIgQuery

, we enabled query tagging with following  command yesterday but I don't see any tag on the queries. 

tsm configuration set -k native_api.UserInfoInGeneratedSQLEnabled -v true  

Someone encountered it and know how to solve it or have suggestion to what to check? 

 

#Tableau Server

2 risposte
0/9000
SSMK A (Self Employed) ha fatto una domanda in #Tableau

Hello Everyone, 

 

I have a hierarchy table and the measure columns with labels like below keep changing their position depending on my hierarchy level. However, I want the labels to stay intact. Can someone help me here please. I attached the tableau workbook file 

 

How to retain the measure label in a hierarchy layout

 

#Tableau  #Tableau Desktop & Web Authoring  #Format Column  #Tableau Server

1 risposta
  1. Oggi, alle 14:08

    Could be the version that was attached, but after manually adjusting the custom header label like below, it appears to be 'sticking' to the columns when adjusting in the Dashboard:Could be the version that was attached, but after manually adjusting the custom header label like below, it appears to be 'sticking' to the columns when adjusting in the Dashboard: Afer selecting Edit

     

    Afer selecting Edit in Shelf, then manually inserting additional spaces as needed to push those strings apart from each other.

    Screenshot 2026-08-17 at 7.03.23 AM.png

     

     

    This then is the updated version of that effort:

    Screenshot 2026-08-17 at 7.03.43 AM.png

    Reattached your workbook.  If this isn't doing what's expected, please point us to the right sheet and/or post the version of the workbook that's the cause of your issue. 

     

    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

Hi all,  

 

Over the past few months, we've been getting sporadic data server process crashes (requiring a tsm restart to fix). We run a single node with Ubuntu 22.04 with 70GB RAM. Online research seemed to suggest data heavy live connections at the same time could cause it, however all connections have been updated to data extracts - since this, the crashes have reduced but they still occur.  

 

Any ideas on how to stop them? Logs seem to show they can reach like 22GB before they are killed. 

 

Thanks 

 

#Tableau Server

6 risposte
  1. Oggi, alle 12:05

    Hi @technical Department

     

    yes both tsm commands works together. You need to enable the limit and set the limit. Feel free to test on your sandbox or test system. But 5 GB per process is not a lot. It will apply to each process individually including VizQL, Backgrounder and Hyper for example. 

    If you want to make progress, you have first to learn to know your instance, meaning setting up some advanced monitoring. Then you can decide if you want to do vertical or horizontal scaling, or hard limit processes.

0/9000

A few of our users with Viewer site role are reasonably sure in the past they were able to create their own subscriptions and if I look at items under schedules that were setup this seems to be the case.   I am unable to find anything solid in the documentation indicating that a viewer role that was able to export/download pdf permissions on a workbook would not be able to do this, the api guide references appropriate role/permissions and it has all been setup and enabled at the site level.   The user with a viewer role can see the option and is able to do everything but select a schedule, the drop down llist is empty. 

 

It works fine for the same user if I assign them an explorer role.   

 

Currently on a Windows Server install running 2025.3. 

 

#Tableau Server

1 risposta
0/9000

i tried to upgrade our tableau server from release 2025.1.18 to 2026.2.1 , it fails on restore of the database...see log below..../opt/tableau/tableau_server/packages/scripts.20262.26.0708.1337/upgrade-tsm --accepteula 

Upgrading Tableau Server to version 20262.26.0708.1337. See log file at /var/opt/tableau/tableau_server/logs/app-upgrade.log for progress. 

Verifying that the upgrade script is running from the correct environment. 

Validating Tableau Server version. 

Verifying that the new packages have been installed on all cluster nodes. 

Verifying Active Directory connection. 

Verifying configuration is valid. 

Performing preflight checks to ensure the server is in a good state to be upgraded. 

Verifying access to backup file path. 

Reconnecting to asynchronous job... 

25% - Validating that Tableau Server Administration Controller has access to the backup file.Job id is '505', timeout is 60 minutes. 

 

50% - Installing backup services. 

75% - Validating that the Backup Restore Service has access to the backup file. 

100% - Uninstalling backup services. 

Stopping service... 

This operation will stop the server. To start server, run 'tsm start' after the upgrade is completed. Do you want to continue? 

(y/n): y 

Reconnecting to asynchronous job... 

Running - Disabling all services.Job id is '506', timeout is 30 minutes. 

50% - Disabling all services. 

100% - Waiting for the services to stop. 

Verifying Tableau Server is stopped. 

Verifying that there is only one deployed Tableau Server Coordination Service ensemble. 

Verifying that Tableau Server has been initialized. 

Verifying licensing state. 

Backing up repository. 

Reconnecting to asynchronous job... 

Job id is '507', timeout is 1440 minutes. 

8% - Starting the Active Repository instance, File Store, and Cluster Controller. 

16% - Waiting for the Active Repository, File Store, and Cluster Controller to start. 

25% - Installing backup services. 

33% - Estimating required disk space. 

41% - Gathering disk space information from all nodes. 

50% - Analyzing disk space information. 

58% - Checking if sufficient disk space is available on all nodes. 

66% - Backing up database. 

75% - Backing up configuration. 

83% - Assembling the tsbak archive. 

91% - Stopping the Active Repository if necessary. 

100% - Waiting for the Active Repository to stop if necessary. 

100% - Uninstalling backup services. 

Reconnecting to asynchronous job... 

Running - Disabling all services.Job id is '508', timeout is 30 minutes. 

50% - Disabling all services. 

100% - Waiting for the services to stop. 

Making prerequisite configuration changes prior to upgrading TSM services. 

Reconnecting to asynchronous job... 

Job id is '509', timeout is 38 minutes. 

11% - Retrieving the topology to deploy. 

22% - Retrieving the configuration to deploy. 

33% - Validating the new topology. 

44% - Determining if server needs to be started. 

55% - Updating nodes to new topology. 

66% - Waiting for topology to be applied. 

77% - Updating nodes to new configuration. 

88% - Reconfiguring services. 

100% - Waiting for services to reconfigure. 

Upgrading TSM services. 

Deploying new service packages. 

Updating Tableau Server Coordination Service. 

Updating Tableau Server Client File Service. 

Adding Activation Service. 

Updating configuration. 

Reconnecting to asynchronous job... 

Job id is '510', timeout is 60 minutes. 

 

Generating new credentials. 

Reconnecting to asynchronous job... 

Job id is '511', timeout is 63 minutes. 

7% - Generating passwords. 

15% - Generating secret keys. 

23% - Generating apigateway mutual SSL certificates. 

30% - Generating Apache Gateway Internal mutual SSL certificates. 

38% - Generating Unique Cluster Identifier. 

46% - Generating Index And Search Server SSL certificate. 

53% - Generating ActiveMQ Server SSL certificate. 

61% - Generating internal Metadata API mutual SSL certificates. 

69% - Generating key store. 

76% - Generating Hyper SSL certificate. 

84% - Generating TSIG logs service SSL certificate. 

92% - Promoting configuration. 

100% - Waiting for services to reconfigure. 

Performing post-upgrade services and configuration operation. 

Reconnecting to asynchronous job... 

Job id is '512', timeout is 30 minutes. 

50% - Disabling all services. 

100% - Waiting for the services to stop. 

Updating asset keys. 

Reconnecting to asynchronous job... 

Job id is '513', timeout is 2880 minutes. 

100% - Migrating asset keys to configuration if needed. 

Restoring repository. 

Reconnecting to asynchronous job... 

Job id is '514', timeout is 2880 minutes. 

3% - Checking backup compatibility. 

7% - Generating manifest. 

11% - Disabling all services. 

14% - Waiting for the services to stop. 

18% - Installing restore services. 

22% - Determining required files for individual nodes. 

25% - Checking available disk space on all nodes. 

29% - Validating that the Backup Restore Service has access to the backup file. 

33% - Transferring required files to remote nodes. 

40% - Restoring database failed. 

44% - Rolling back database. 

48% - Deleting temporary backup file. 

52% - Cleaning up restore data on all nodes. 

56% - Uninstalling restore services. 

 

 

This job failed due to unexpected error: 'RuntimeException' 

Running 'restore begin' failed 

 

Repository restore failed. 

This version of the upgrade-tsm script allows you to retry a failed upgrade from the last successful step. Retry the upgrade by rerunning the upgrade-tsm script. 

 

Tableau Server Upgrade encountered an unexpected error. 

 

Help us improve Tableau Server: 

 

The upgrade encountered an unexpected error. To help us improve the product, you can send us select upgrade failure log files. If you choose to do this, it will include the domain and host names of the Tableau Server. 

 

The logs may contain private information that is used only to help developers identify the issue and fix the error. 

 

Sending the select logs does not open a support case. If you require immediate assistance, please open a standard support case. 

 

For more information, see our privacy policy. 

 

Send logs (y/n): 

(y/n): n 

Not sending error logs to Tableau. 

An error occurred during installation. 

An error occurred while restoring repository. 

null 

 

any suggestions ? 

 

#Tableau Server

4 risposte
  1. 12 ago, 20:41

    Hi @richard de Swart

     

    failure occurs during the postgres backup restoring (so from postgres v15 to v17) not during software update or process configuration, so I would be you, I would look into the "pgsql" and "backuprestore" logs  (/var/opt/tableau/tableau_server/data/tabsvc/logs) for  SQL import errors. 

    Most likely you have "corrupted" or orphan records that can cause constraint violations, if for example you have been doing in place-upgrade for a long time. 

    Have a look. Fixing such records, if it is really the case, is another story.

0/9000

Hey šŸ›‘ Tableau #datafam#datafam and Salesforce  #Tableau_next#Tableau_next

 users -  

 Want to level-up your mapping game or not certain which chat type to use with your data? Help is on the way at our September 2nd virtual meeting - you just need to save a spot at 

https://lnkd.in/gkb5kNXS

 and we'll see you there -- 

All are welcome 

#Tableau Cloud #Tableau Server #Tableau Public 

 

Hey šŸ›‘ Tableau and Salesforce users - Want to level-up your mapping game or not certain which chat type to use with your data?

0/9000
M M ha fatto una domanda in #Tableau Desktop & Web Authoring

Hi, 

 

I'd like to raise a client feedback regarding Tableau's native multi-select filter behavior where user is expecting like Excel, where you can search for a value and immediately select it without having to deselect "All" first. 

 

Scenario is In a Multi-Select Filter where all values are selected by default, when a user enters a keyword into the search box, for example "Ada", Tableau narrows the list of displayed values but retains the All selection state.

Tableau Multi-Select Filter Search

The user must then first deselect All before selecting the desired values. 

 

The client's view is that the search box gives the impression that they are beginning a filtering action, similar to Excel. As a result, users expect to be able to search for a value and immediately select it. 

 

We have given the client several options based on the current capability of tableau:

  • Wildcard filter
  • Single value dropdown
  • Multi-value custom list

All of which the client has said does not resolve his original concern. 

 

I understand this appears to be Tableau's intended behavior rather than a defect, I'm unable to find any official Tableau documentation that explains the rationale behind it.

 

If anyone could share/advise any documented explanation or product guidance on:

  • Why the search box only narrows the displayed values rather than updating the selection itself
  • The design rationale behind requiring users to deselect All before selecting a subset of values

 

Thanks 

 

#Tableau Desktop & Web Authoring  #Tableau Server  #Reports & Dashboards

3 risposte
  1. 6 ago, 17:19

    I understand, so you could create an underlying text box that essentially says 'Start by filtering in the filter selection pane to the right' and/or have a distinct starting value that is always selected as a starting point.   

     

    We don't know what you're actually working with, but those would be some options to consider.  If you have the link to the idea, could you post it in this thread so that others can upvote it? 

     

    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

 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 risposta
  1. 26 lug, 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