#Tableau Cloud63 discutindo

The message “2026.3 Deployment to Production will start in two weeks” is simply the official heads‑up that this automatic upgrade is approaching. Tableau Cloud rolls out major releases first to Release Preview environments, then automatically to production sites about two weeks later

. 

You can check out 2026.3 beta version via signup here 

Hi, 

Thank you for providing the workbook. 

 In the Data Source tab, please switch the connection from Live to Extract, and then save the workbook as a Packaged Workbook (.twbx). 

 We would appreciate your cooperation. The current file cannot be accessed correctly due to issues with the data reference. 

@Nate Laning

Hi, I have been also getting some results as you, and lineage not available as described in this issue and other issues related to lineage: 

Unfortunatelly, there is not a workaround for this. 

I suggest you to report by clicking on the first link, and if you want, you may create also a case: 

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 

@Donald Kean

Hi, check if the other required urls are also whitelisted: 

Also, if you still having problems, I would advice you to try with other Tableau Bridge releases (older or newer).  Sometimes an older release has worked for me. 

Finally, the same article states you need ports 80 and 443.  Don't hesitate to take a complete read of the document. 

If you cannot connect to Tableau Cloud using Edge, it means that maybe a proxy is interfering with your connection. 

what do you get when you run in a cmd:

curl -v https://online.tableau.com

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 

@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