#Tableau Cloud56 debatiendo

How to change the font of transaction type to match same as the number values .For example - Production Order Picking should be blue same as its value . Please have a look at the screenshots .It has to match the transaction type legend .Thankyou   

Our Tableau Cloud site is configured with Microsoft Entra ID (Azure AD) SSO, and all user authentication is federated. We do not allow local Tableau usernames/passwords. 

We are attempting to integrate Tableau Cloud with Zenoptics using Tableau REST APIs. Zenoptics requires authentication via a Personal Access Token (PAT). 

To generate a PAT, Tableau requires a user account to sign in. However: 

Our Azure / Entra ID administrators have confirmed that they cannot create a non-interactive “service account” with a traditional username and password. 

All Entra ID accounts are SSO-only and require interactive authentication. 

Therefore, there is no way to log in as a headless service account to generate or manage a PAT. 

Questions 

What is the recommended architecture for API-based integrations (such as Zenoptics) when Tableau Cloud uses Entra ID–only authentication? 

Is Tableau’s official guidance to: 

Use a licensed Entra ID user dedicated as a service principal (human account, non-MFA, non-expiring), or 

Use Connected Apps / OAuth instead of PATs, or 

Some other Tableau-supported approach? 

If PATs are still required, how does Tableau recommend customers securely create and rotate PATs when non-interactive service accounts are not possible in Entra ID? 

Please advise on the supported and secure best practice for this integration pattern in Tableau Cloud with Entra ID SSO enforced. 

Issue: 

I am unable to connect to Tableau Cloud from my Bridge Client on a Windows Server. 

I am also unable to connect to the web site using Edge. (Chrome not allowed on our servers.) 

Error: It looks like

closed the connection. 

What I have done: 

Reached out to my Network Defense team. They have verified that connections are being allowed to

and sub-domains. 

Verified the Root certificate, GlobalSign Root CA, exists and is valid.  

Attempted to restart the Bridge client. 

I get the following from the service / client: "There was a problem and the client could not reach Tableau Cloud." 

Rebooted the server. 

Cleared the stored Windows Credential for Tableau Bridge. 

Note: I have Tableau Prep installed on this server also and it is not having any issues connecting to Tableau Cloud. 

This issues started a few days ago.  

The Bridge has been working fine for 2 years with the only changes being server patching and Bridge updates. 

Bridge application is current.  20262.26.0603.1643  

Hello, 

 I'm wondering why the dashboard size and resolution change after I publish from Tableau Desktop to Tableau Cloud.

Currently, I have:

• Dashboard size: Automatic
• Worksheet size: Default

I create the dashboard on a desktop PC and want to display it on a larger external monitor, but the layout looks different after publishing.

Does anyone know why this happens or how to keep the size consistent? 

Thanks in advance for your help. 

(Japanese below)

---------------------------------------------------------------------------------------------------------------------------------------------- 

こんにちは。 

 Tableau Desktop で作成したダッシュボードを Tableau Cloud に公開すると、サイズや解像度が変わってしまう理由を知りたいです。

現在の設定は以下のとおりです：

• ダッシュボードサイズ：自動
• ワークシートサイズ：標準

デスクトップ PC でダッシュボードを作成し、大きめの外部モニターで表示したいのですが、公開後にレイアウトが変わってしまいます。

なぜこのような現象が起きるのか、またサイズを一定に保つ方法があれば教えていただきたいです。

よろしくお願いします。 

#Tableau Desktop & Web Authoring  #Tableau Cloud

Environment: Tableau Cloud, REST API 3.29, tableauserverclient (Python), Snowflake connection with authentication='oauth', oauth-config-id='default', server-oauth='server-custom'. 

ISSUE 

We publish workbooks via REST API/PAT in a CI/CD pipeline. We're trying to reproduce a connection state that Tableau Desktop can produce, but the REST API can't. 

Desktop-published state (Data Sources tab shows "Not embedded in connection"): 

auth_type='oauth' username='<user>' embed_password=False 

Our pipeline's state (REST API publish): 

auth_type='oauth' username='' embed_password=False 

The Desktop state results in viewers being prompted for their own credentials. Ours results in every viewer getting BadOAuthCredentials, since there's no username hint at all. 

WHAT WE TRIED 

Using Server.workbooks.update_connection() (PUT /workbooks/{id}/connections/{connectionId}), we tested every combination: 

1. embed_password=True + username -> credential embeds, all viewers connect silently as that one identity (no prompt). 

2. embed_password=False + blank username -> every viewer gets BadOAuthCredentials. 

3. embed_password=False + non-empty username (trying to match Desktop) -> the server silently discards the username; a follow-up GET always returns username=''. No error is returned, it just reverts. 

4. Re-embedding (embed_password=True) via update_connection without supplying a password fails outright with 404020: Resource Not Found ... This may be due to incorrect or missing credentials. There's no way to flip an OAuth connection back to embedded through this endpoint without a real credential, and OAuth connections have no password-style credential the API can supply. 

We confirmed #3 fails identically whether attempted via connections=[ConnectionCredentials(...)] at publish time, or via a separate post-publish update_connection call. Same result both ways. 

QUESTIONS 

1. Is there any documented REST API mechanism (any endpoint, any API version) to set an OAuth connection to embedPassword=false while preserving a non-empty userName hint, matching what Desktop produces? 

2. Is that "not embedded + username hint" state inherently tied to an interactive/vizportal-authenticated session (i.e. genuinely unreachable via PAT/REST), or is there an undocumented parameter/flow we're missing? 

3. Is per-viewer OAuth prompting for a Snowflake connection with oauth-config-id='default' expected to work at all when the workbook was published via REST API/PAT, or is this a Desktop-only capability? 

Happy to share full request/response payloads if that helps with diagnosis. 

#OAuth  #Tableau APIs & Embedding

#Tableau Cloud  #Tableau Server