Hello, team. @powerful-vase-22055@big-carpet-38439@dazzling-judge-80093 Can you tell about tableu object - datahub entity mapping? Watching code now and see this

Workbook - None ?

Dashboard - Dashboard

Sheet - Chart

Datasource - Dataset

Custom SQL - Dateset

Is it right? There are some problems with that: 1. All users work in tableau with workbooks and without it users will have navigation problems. 2. Sheet can exist in Workbook without Dashboard.

How this should be mapped ideally?

to my mind

Workbook - Dashboard

Dashboard - Chart

Sheet - Chart (or Dataset?)

Datasource - Dataset

Custom SQL - Dateset

But we have some datahub restrictions: 1. We need Dashboard - Sheet and Workbook - Sheet lineage (datahub do not support Chart - Chart, Dashboard - Dataset?). 2. And to my mind Sheet shoud have schema metadata for some reasons - calculated fields on sheet level; description, tags, terms for fields via UI and etc. (datahub do not support schema metadata for charts?)

Tableau supports projects within other projects, and we use that heavily to organize large categories of dashboards within a single site in Tableau Online. I guess the closest thing to a project is a dashboard, since it's a container of sorts

project is just path for other objects

What would you map a project to in Datahub?

I think if Datahub is compatible, this format would be good:

Workbook - Dashboard

Dashboard - Dashboard

Sheet - Chart

Datasource - Dataset

Custom SQL - Dateset

Datahub has a new container concept .. we could map workbooks to that

@big-carpet-38439 Do you have an example of how it would figure in the data lineage?

Which part, the Workbook?

Hey folks, want to make sure I’m understanding the feedback here. Is this the correct mapping?

Project - Container

Workbook - Container

Dashboard - Dashboard

Sheet - Chart

Datasource - Dataset

Custom SQL - Dataset

My first question would be how the workbooks will look when viewed within a project, both being containers. If this is an issue, would making a workbook a dashboard pose a problem?

This is a fantastic question… I’d love for @big-carpet-38439 to jump in to provide some thoughts about how we should be using Containers here!

Workbooks will just be in a list within the project.. For example here is an example of a Database (E.g. project) that contains 2 schemas (e.g. workbooks) inside

@little-megabyte-1074 So in case, a workbook is a container when detailing it, would the charts and dashboards that are part of that workbook appear in the entities? If so, I understand that would be very good.

Project - Container

Workbook - Container

Dashboard - Dashboard

Sheet - Chart

Datasource - Dataset

Custom SQL - Dataset

Why dont you want to use projects just like browse paths?

Hi! I'm sorry. I didn't pay attention to that part. I focused more on the workbook part. Projects should be browse paths.

Hi @colossal-easter-99672 @brainy-wall-41694 browse paths are only used for datasets and not for other entities like charts, dashboard or containers. How about we map Tableau Project to Container ? This can help view workbooks, datasets as well as subprojects that are in same project. It kind of aligns with Tableau Project concept.

https://demo.datahubproject.io/browse/dataset/prod/datahub/entities Charts and dashboars have browse paths too (don't know about container). I think use containers for projects and containers for workbooks is too much.

Yeah, workbook I agree. Projects I don't know.