#Tableau APIs & Embedding17 diskutieren mit

Hi @Umesh Chorge

dealing with WebEditing and credentials can be a bit unstable. I've seen a lot of instances over the years were credentials for some mysterious reasons were not committed or using old ones or using credentials from another tenants while the Analysts were working daily on multiples tenants.  

This is one example: 

As you seem to work with embedded data source directly in the workbook, as Diego said in his earlier post, use published data sources. To keep your datasource stable and modify your workbook content irrelevant of Athena connections even in WebEdit. 

And ideally you modify your published data sources using Tableau Desktop if you can.

Hi @David Foster​ ,

To create a data source from a Snowflake view using an API-based script, you can utilize Snowflake's native SQL API to execute SQL statements over HTTP. This approach allows you to interact directly with your Snowflake data warehouse, enabling operations such as creating views and managing data sources. By sending HTTP requests containing your SQL queries to Snowflake's API endpoint, you can automate the creation of data sources based on your views. For detailed guidance on using Snowflake's native SQL API, refer to the official Snowflake documentation. https://blog.dreamfactory.com/generate-a-snowflake-rest-api-in-less-than-5-minutes

Best regards,

Nikolay Gerasimov

Tableau Forums Ambassador

Hi, in addition to Diego's comment about connected apps implementation (which is the way to go) I wanted to point that the REST API endpoints for Collections are finally being released for Tableau Server with version 2026.2 (so somewhere Q3 this year).

@DAEYEON KOO

I am not completely 100% sure, but you may give a try using Unified Access Tokens: 

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,Eleanor Hunt

It seems that embedding Tableau dashboards into Google Slides isn’t very stable at the moment. I’ve seen similar reports where the extension loads slowly or the refresh action fails quite often. I’m not aware of any official statement calling this a known issue, but the behavior does feel inconsistent in practice. 

Regarding the axis changing after embedding, this might happen because Google Slides adjusts the frame size, and Tableau then reflows the axis labels based on the available space. When the embedded view becomes smaller than the original dashboard, long date labels can wrap or shift unexpectedly. 

• Use a fixed-size dashboard in Tableau
• Increase the frame size in Google Slides if possible
• Shorten the date format (e.g., “Apr 26” instead of a long format)
• If stability is important, consider embedding the view in a regular web page instead of Google Slides — that tends to behave more reliably

The concept of embedding into Slides is great, but in its current state it may still be a bit sensitive depending on the dashboard and environment.

@Tara Morton

  Great review of details.  

I am currently testing the Tableau MCP connector with Claude and wanted to document the issue we are experiencing and confirm the best supported path forward. 

We have successfully added the official Tableau MCP connector/extension in Claude, and it works as expected in standard Claude Chat. However, when attempting to use Tableau through Claude Cowork, the Tableau tools are not available.  

In Claude Cowork, we ran ToolSearch for the following terms:

• Tableau
• tableau-mcp
• Tableau MCP
• workbooks
• datasources
• published data sources

The result was that no Tableau tools were found. Claude Cowork also explicitly stated:

“I do not have Tableau MCP tools in my allowed tools list for this Cowork session.”

Based on feedback from Anthropic support, the likely reason is that the Tableau .mcpb Desktop Extension is designed for local Claude Desktop environments and cannot run in web-based Claude Cowork.  

 Please let us know the best supported implementation path, whether this is currently available, and any documentation or examples you can share.  

Thank you in advanced.

@Benjamin Peters

Hi, in this case, I would remove the toolbar, and I would add some buttons using the Download Object to allow the download of the image, pdf: 

Something similar as this Tableau Public workbook: 

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 

@Eric Guerin

Hi, It seems you are trying to render the tableau-viz component without a src, and then you are trying to change the src. 

What if you try to give first a src, that will render the iframe child object, and all the related code, and then you change the src. 

If you are able to share your full code, we may have a better way to assist you.  

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 Caleb, try this:

query workbookFields {
  workbooks(filter: {name: "testjuly19"}) {
    name
    sheets {
      name
      sheetFieldInstances {
        name
        ... on CalculatedField {
          formula
        }
      }
    }
  }
}

Use "datasourceFields" if you also want to include fields that were used in calculations but not actually on the worksheets.

-Keshia