#Tableau Server70 人がディスカッション中

@Antoine Maugirard

If it helps, starting with version 2026.1, if your dashboards contain Viz extensions, or Dashboard extensions or Tableau Pulse object, then image exports might not render via PDF or Powerpoint download.  Please see below for more detail.  Not sure if this is your situation or not. 

Starting in Tableau version 2026.1, image exports in Tableau Cloud support Viz Extensions, Dashboard Extensions, and Pulse dashboard objects. 

This applies to image downloads, subscriptions, and image exports via the REST API. PDF and PowerPoint exports don't support these objects and will appear blank. 

• Tableau Trusted vs. Network-enabled extensions: Only Tableau Trusted Extensions and Pulse objects (governed by Tableau/Salesforce) are included in exports. Network-Enabled extensions won’t be rendered in the export.
• Tableau Desktop: In Tableau Desktop, dashboard extensions are supported in image exports, but Viz Extensions aren’t.
• Render state: Exports reflect the published state or a saved Custom view. Manual selections or temporary highlights made during the session aren’t retained in the export.

If you’re using Web Authoring, you must save the workbook before these objects will appear in a download. Image export handling is only updated when the view uses an extension or Pulse object.

Reference:

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)

Hi @Elis Vergan

 you can apply the same Tableau Server license key on three instances in parallel, as far as the other two environments are non-productive (following the Tableau User Agreements), for example production passive standby, or qa or dev... 

@Kundan Kumar Jha

Please read the Tableau forum rules on the ban of using AI generated answer for technology topics. Please contribute only personal with answers based on your own experience. That is the spirit of the Tableau community forums where Tableau users help each others.  

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

This error was caused by login failure on AD by the Tableau service account. 

Another problem that was caused was failure of Tableau to start up and then fail to either start or stop. 

Both were resolved by correcting the account and rebooting the server 

-Arvid

Hi @Harald Egner

I assume you have a database object corruption but you are not sharing much information or context. 

If you want to connect to the Tableau Postgres database and do whatever you want at your own risk as an admin superuser, the db username is "tblwgadmin" and the password can be retrieved through the following tsm command:

tsm configuration get -k pgsql.adminpassword

@Krzysztof Wascinski

Hi, unfortunatelly not possible with local auth, you will need to use an external Idp (SAML). 

I suggest you to create an idea for this: 

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 

Just an additional comment on the Identity Pool part as it is easy to mix up things. 

Identity Pool is a pair of 1) an identity store and 2) an identity provider. 

identity store can be local or AD/LDAD, and identity provider always and only OIDC. 

But the Identity Pool identity store is constrained by your original identity store defined during Tableau Server installation. 

If identity store local then Identity Pool identity store can only be local (same or new) 

If identity store AD/LDAP then Identity Pool identity store can only be  AD/LDAP (same!) 

It is pretty cool but tedious to configure as there is no tsm command or GUI to configure it. it is all through REST API calls only. 

Then your Tableau login page will have an additional button, for example External users. 

The internal users can continue to use Local authentication or SAML, it is totally independant.

It was a very good idea from Tableau, but Tableau didn't further develop this feature since 3 years. 

Unfortunately that has always been a limitation of Server/Cloud text tables. I prefer Desktop's behavior. You would need to add a unique hidden column like customer ID to the left of country to get it to appear on every row. But that prevents convenient selection by country.