Type 2 Add service to ConnectionItem properties For Oracle #1807

Activity

1. binnera

   added

   enhancement

   needs investigationIssue needs to be looked at by TableauIssue needs to be looked at by Tableau

   on Jun 29, 2026
2. jacalata commented on Jul 31, 2026

   

   jacalata

   on Jul 31, 2026

   Contributor

   More actions

   Thanks for the report. Looked into this and the underlying issue turns out not to be Oracle-specific.

   The REST API's <connection> response element has a fixed attribute set — currently id, type, authenticationType, dbClass, filename, googleSheetId, scope, useOAuthManagedKeychain, instanceUrl, oauthConfigId, embedPassword, password, serverAddress, serverPort, userName, queryTaggingEnabled, workgroupAuthMode, authFederationServiceAccount. There is no service, serviceName, dbName, or databaseName in what the server sends back on either GET /datasources/{id}/connections or GET /workbooks/{id}/connections, for any connection type. Verified by inspecting the API schema (v3.27–v3.30) and by round-tripping ~500 real connections across 10 connector types on Tableau Cloud — none of them carry those attributes. I will look into what should be added to this by the server. Tagging this as server-side work for now.
3. jacalata

   added

   Server-Side Enhancement

   on Jul 31, 2026
4. jacalata commented on Jul 31, 2026

   

   jacalata

   on Jul 31, 2026

   Contributor

   More actions

   Follow-up to the last comment — the easiest way to read connector-specific attributes (Oracle service, Snowflake schema, Teradata query-band, initial SQL, etc.) today is the tableau/document-api-python library. Combined with TSC's datasources.download() or workbooks.download(), you can:

   import tableauserverclient as TSC
   from tableaudocumentapi import Datasource
   
   server.datasources.download(ds_id, filepath="ds.tdsx", include_extract=False)
   ds = Datasource.from_file("ds.tdsx")
   for c in ds.connections:
       print(c.dbclass, c.server, c.dbname, c.service, c.schema, c.query_band, c.initial_sql)

   That covers the connector-specific fields today. The REST API <connection> schema is a stripped subset of what's in the file itself.
5. jacalata commented on Jul 31, 2026

   

   jacalata

   on Jul 31, 2026

   Contributor

   More actions

   Update — for the audit / discovery use case (finding which connections point at which Oracle services, dbnames, etc.), the Tableau Metadata API is a better fit than either the REST API or downloading files. The GraphQL DatabaseServer type exposes hostName, port, connectionType, and service — the last one being exactly the Oracle service name field this issue asks about.
6. jacalata

   removed

   enhancement

   needs investigationIssue needs to be looked at by TableauIssue needs to be looked at by Tableau

   on Jul 31, 2026
7. jacalata

   added

   ui-existsFunctionality is available in the Tableau UI but not yet in the REST APIFunctionality is available in the Tableau UI but not yet in the REST API

   on Aug 25, 2026
8. bcantoni

   added a commit that references this issue on Oct 14, 2026

   feat(samples): sample for reading connector-specific connection attrs (…

   ...

   6f171fa