#Tableau APIs & Embedding16 discussing

@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 

@Benjamin Peters

Hi, according to my experience the answer is no. 

The embed docs does not include anything about this: 

Also, the iframe attributes also do not state a parameter for that: 

The only option would be to remove the toolbar completely. 

Would you explain how are you filtering the records? Maybe you can use Tableau Claims definition to pass attributes from the user, to the JWT generated by Salesforce, and then use it in Tableau Classic with the USERATTRIBUTEINCLUDES('state', [State/Province]) 

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

Hi there,

here is the Tableau Embedded Playbook.

Full documentation on how you can ebbed your dashboards in a website.

Here are few samples on how the variables for embedding can be changed (based on your shared code).

Here are the parameters for embed code.

For your example you need to embed this code:

<param name='toolbar' value='yes'/>

Values might be: yes; no; top

Not sure you can display them based on user access. But, if the website js can recognize the user you can programmatically change the value to 'yes' from 'no'.

Let me know if this was helpful and mark the answer.

thanks

Adrian

Hi @Thomas Kennedy​ 

Yep possible, and opens up some pretty cool use cases.

Here are some resources:

https://www.tableau.com/blog/enable-predictive-capabilities-tableau-using-analytics-extensions

https://www.tableau.com/developer/tools/python-integration-tabpy

https://www.tableau.com/developer/tools/r-integration

Let me know if this helps!

Ta, Steve

Hi @Raghul Kumar

I asked Claude and asked it again to verify the answer. So, please, review it with caution as AI answers might sound confident but can be wrong.   

This is what

came up with:  

TACO 3.0 EPS Connector: Dynamic OAuth Instance URLs per Region – Known Limitation 

I’ve researched this thoroughly and want to share findings that may help others facing the same constraint. 

You’ve correctly identified a hard architectural limitation in TACO 3.0 EPS connectors: EPS-based OAuth connectors have a dependency on Tableau OAuth support and cannot run with the EPS standalone server

, unlike built-in connectors like OneDrive. 

The root cause is the schema constraint between TCD (Tableau Connector Dialog) and EPS:

• TCD-based plugins can use <show-instance-url-prompt> to collect dynamic OAuth endpoints from users at connection time. This is how OneDrive and SharePoint Online connectors prompt users with an “OAuth Instance URL” dialog to enter tenant-specific or custom connection endpoints Tableau.
• EPS connectors (TACO 3.0) use connector.json without dialog support—only stateless field submission. The EPS server only tests EPS connector logic and doesn’t consume TACO infrastructure files like manifest.xml Tableau.

Setting {instanceUrl} or {region} in oauth-config.xml doesn’t work because those placeholders are resolved only within TCD’s connection-dialog context, which EPS cannot access. 

This exact scenario was raised as a feature request: Databricks requested SDK support for multiple OAuth endpoints per connector, proposing dynamic loading of oauth-config.xml based on detected cloud provider

Status:

with no EPS-specific solution. 

1.

Create separate oauth-config.xml files per region (e.g., oauth-config-us.xml, oauth-config-eu.xml, oauth-config-in.xml) in your connector. Add logic in your app UI to present a region dropdown, then conditionally load the matching config. This requires connector regeneration per region but keeps EPS architecture intact. 

2.

If your use case allows, migrate to the standard Tableau Connector Plugin SDK (ODBC/JDBC-based) instead of TACO/EPS. This gives you full connection-dialog support and the ability to prompt for dynamic OAuth endpoints. See:

3.

If your SaaS supports this requirement, file a feature request directly with Tableau/Salesforce to extend EPS OAuth to support dynamic instance URLs. Reference Issue #705. 

TACO Toolkit Documentation (EPS constraints):

OneDrive Dynamic OAuth Endpoints:

Connector SDK OAuth Reference:

• Known Feature Request (Multi-Region OAuth): https://github.com/tableau/connector-plugin-sdk/issues/705

@Nilim Borua

Hi, have you folowed the steps stated in Platform API? 

https://help.tableau.com/current/api/cloud-manager/en-us/docs/platform_data.html

You mau use the bridge_client_status

 event type: 

GET https://cloudmanager.tableau.com/api/v1/tenants/{tenantId}/sites/{siteId}/activitylog?startTime=2026-03-20-T00:00:00&endTime=2026-03-23-T00:00:00&eventType=bridge_client_status

Regards,  

Diego

@Sami Ahmad

Hi, you may use:

import jwt
import tableauserverclient as TSC
import datetime
import uuid
Client_id = "f27a043b-c771-4b18-a1a1-007e120293a3" 
SecretValue = "nijAJ5p"
SecretID = "aaa0e3"
siteId = ''
token = jwt.encode(
        {
            "iss": Client_id,
            "exp": datetime.datetime.utcnow() + datetime.timedelta(minutes=10),
            "jti": str(uuid.uuid4()),
            "aud": "AHMADSA",
            "sub": "dmartinez@modux.co",
            "scp": ["tableau:content:read","tableau:workbooks:*","tableau:projects:*","tableau:datasources:*"]
        },
        SecretValue,
        algorithm="HS256",
        headers={
            'kid': SecretID,
            'iss': Client_id
        }
    )
print(token)
server = TSC.Server('https://tableau-qa.park-edw.com')
tab_auth = TSC.JWTAuth(token,site_id=siteId)
with server.auth.sign_in(tab_auth):
        print("signed in")
        workbooks, paginator = server.workbooks.get()
        for wb in workbooks:
            print(wb.name)

Basically you need the tableau:content:read in the scopes: 

https://help.tableau.com/current/api/rest_api/en-us/REST/rest_api_ref_workbooks_and_views.htm#query_workbooks_for_site

And in the auth object site_id=siteId

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 

@Bhavesh Dave

Hi, the method is not supported in Tableau Server:

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