Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add flows input and output information #79

Closed
omargherardi opened this issue Jun 27, 2023 · 1 comment
Closed

Add flows input and output information #79

omargherardi opened this issue Jun 27, 2023 · 1 comment
Labels
duplicate This issue or pull request already exists

Comments

@omargherardi
Copy link

Hi,

I was directed here because I needed to map all tableau server, its content and connections between objects, flows, datasources and sql server's tables. It is easy to connect views with workbook - and easier thanks to your work. It is also easy to map relations between published datasources and sql server's tables. But the thing I struggle doing is to map all relations (input/output) with flows. raw data seems to be incomplete (no table name, for example), but we know tableau has all information, because in the server, if we enter in a view, we can see all flows related to that view, and back to all tables, dbs and servers.

Maybe could be useful to add flow connection in a separate workbook.

Anyway, I also accept hints on how to do this (infamous) job

Thanks,

Omar

@mcoles mcoles added the duplicate This issue or pull request already exists label Jun 27, 2023
@mcoles
Copy link
Contributor

mcoles commented Jun 27, 2023

The short answer here is that I tried to model flow inputs/outputs in TS Data Connections, but could not find a satisfactory way to do it.

But at a higher level, the dependency relationships you are after are really not designed to be consumed from the Tableau Server postgreSQL repository database. The data you want is stored in the Metadata API, which uses a GraphQL model to store information in. It has what you need and more, capturing even column-level mapping details. So my recommendation would be to use that as your resource instead.

@mcoles mcoles closed this as completed Jun 27, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
duplicate This issue or pull request already exists
Projects
None yet
Development

No branches or pull requests

2 participants