#Tableau Cloud토론 중인 항목 67개

Hi Jahnavi,

I agree with Hideaki's approach.

One advantage of this method is that the text colors will automatically stay in sync with the Transaction Type color legend. This can be easier to maintain than manually formatting labels when new categories are added.

Another option would be to use a separate worksheet for the labels and align it within a dashboard. This provides more formatting flexibility, although Hideaki's dual-axis approach is probably the simpler and more maintainable solution.

Hope this helps!

@Kasumi Kikugawa

  さん、こんにちは。  

ダッシュボードは固定サイズが推奨されています。 

自動にするとサイズでレイアウトが意図しないものになってしまいます。  

大きめの外部モニタ用の固定サイズのものを用意したほうがよいかもしれません。 

（多くの人が大きな外部モニタで使うのではなく、特殊なケースであればなおさら）

こちらの記事も参考にしてみてください。 

https://help.tableau.com/current/pro/desktop/ja-jp/dashboards_organize_floatingandtiled.htm

Hi, @Winston Kaki

It's been a while since this was posted, so you may have already found a solution. However, I wanted to share a thought in case it's helpful.

If Zenoptics only supports PAT-based authentication, then using a dedicated licensed user account may be the most practical option.

That said, this approach seems to introduce additional operational overhead around PAT management and rotation. Looking at Tableau's Connected Apps documentation, features such as SSO integration, JWT-based authentication, and secret rotation are supported. Because of that, it seems worth considering alternatives to PATs from both a security and governance perspective.

However, from what I have been able to find, I have not seen any Tableau documentation that explicitly states which approach is considered the best practice for Entra ID SSO-only environments. So while Connected Apps or OAuth appear to be promising options, I'm not sure which architecture Tableau officially recommends for this type of integration.

I'd also be interested to hear from anyone running a similar setup, or from someone familiar with Tableau's official guidance on this topic.

Hi, @Draghici Ionut

It's been a while since this was posted, so you may have already found a solution. However, I wanted to share one possible approach.

If I understand correctly, the issue is that in a product-level table, products that do not exist in every year (for example, new or discontinued products) end up with different year positions. As a result, INDEX() points to different years depending on the product.

If that's the case, I think a model-side solution is probably the most practical approach.

• Expose the Year attribute from the cube so it can be referenced directly.
• If that's not possible, pad the data on the cube side so that every product has records for every year, even when the measure values are null.
• If neither option is feasible because of data volume or other constraints, continue using the INDEX() approach.

To me, INDEX() is essentially a workaround based on position rather than the actual year value, so it can be difficult to make it fully reliable when products have different year histories.

Hi @Wascar Perez

thanks for sharing the details with the community. 

What I would try if I were in your shoes: set embed_password=True with your REST API pipeline as usual, then try to unset the embedded password with the VizPortal API. It is undocumented and unofficial, but you just need to trace your browser traffic with dev tools when using the Server UI then google the VizPortal API info a bit to see how to authenticate against it and you will figure it easily if you are a developer. 

I checked on my sandbox. It is this endpoint:

@Henry Tannler

You know, a lot of AI answers in the forums recently. 

It seems you may have some problems.  One related to Tableau Cloud sign in. So let's start here. 

a. Resetting your MFA verifiers from Tableau Cloud (

) 

will only work if you are using Tableau Cloud local authentication (not using Salesforce, or Google, or SAML or OpenId authentication). 

b. Once you reset your MFA verifiers (and if you are using Tableau + MFA auth), after signing in again you will be asked to choose an MFA (Salesforce Auth, Code Generator, etc). 

Thus: 

a. Please verify first other admins have access (so if you are locked out, they can help you) 

b. Change your auth type to Tableau + MFA 

c. Reset your MFA verifiers 

d. Sign in again, and set your MFA verifier 

e. Sign out again 

f. Sign in again and you will be asked to create emergency codes. 

After that, try to sign in using Tableau Desktop: 

a. Try to sign into your site and do your stuff. 

b. If you can't sign in or do your stuff, maybe you will need to clean sign ins:

c. If clearing the saved sign ins does not work, you may need to go with a "hard delete": 

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 

Hi , 

I think the SSO authentication is failing. 

Resolution Steps 

1. Sign out completely from Tableau Cloud 

2. Close the browser 

3. Open the browser in Incognito/Private mode 

4. Log in again using the Tableau Cloud site URL 

5. Log in to your company's SSO portal (e.g., Azure AD, Okta) first, then access Tableau Cloud 

Update / likely root cause found 

For anyone following this thread, here's where things stand. 

Symptom recap: 

- Scheduled extract refresh failed with: "TableauRuntimeException: Missing password. Incorrect username or password" (offline mode, status code 10000). 

- Test Connection succeeded every time. 

- Manually triggering a refresh from the Data Sources tab in Tableau Cloud succeeded every time. 

- Deleting and recreating the refresh schedule/task didn't help. 

- Re-entering and re-embedding the password via the web UI showed as "Embedded in connection," but the scheduled/background job still failed with the same error. 

What we found: 

We opened the workbook in Tableau Desktop and went through Server > Publish Workbook > Data Sources > Edit, checking each embedded connection's Authentication setting individually. One connection (a custom SQL connection) was configured differently from the others — it did not have "Allow refresh access" (or "Embed password") selected under Authentication, unlike the rest of the data sources in the workbook, which all had one of those two options properly set. 

What we did: 

1. Set the Authentication option to "Allow refresh access" for that connection in the publish dialog. 

2. Verified the settings for all other embedded connections as a sanity check. 

3. Republished the workbook from Tableau Desktop, overwriting the existing published workbook. 

4. Ran a full manual extract refresh from Tableau Cloud afterward — it succeeded. 

Caveat: manual/interactive refresh succeeding was already true before this fix too, so it's not fully conclusive on its own. The real test is whether the next scheduled (unattended) refresh — run by the Backgrounder/scheduler with no interactive session — succeeds. If it does, that would confirm the missing "Allow refresh access"/"Embed password" authentication setting on that one connection was the actual root cause (the other connections had it set correctly, which is presumably why they always refreshed fine). If the scheduled refresh still fails with the same "missing password" error, we'll need to dig further into differences between the manual and Backgrounder/scheduler execution context specifically. 

Will report back once the next scheduled run has completed. Posting this in case it helps anyone hitting the same "test/manual refresh OK, scheduled job fails on missing password" pattern — worth double-checking the Authentication setting per-connection in the Desktop publish dialog, not just the post-publish credential edit in the web UI.

To access Tableau Cloud Manager (TCM) without knowing who holds the admin credentials, follow these diagnostic steps to identify your site admin.

Step 1:Log in to Tableau Cloud ([https://online.tableau.com](https://online.tableau.com)).

Step 2:Go to the Users tab from the left sidebar navigation.

Step 3:Look at the Site Role column.

Step 4:Filter or search for users marked as Site Administrator Creator or Site Administrator Explorer.

Contact those individuals—in many organizations, the Site Administrator is also the Cloud Administrator (TCM Admin) or knows who made the original procurement purchase.