Tableau Ingestion imports data successfully, but f...
# troubleshoot
m
Tableau Ingestion imports data successfully, but folder hierarchy is messed up. Some folders are in place, some folders are missing completely with its contents. Some folders are in wrong place or contain that they should not contain, or merged based on same name despite being two different folders in different places originally What can be a reason and solution to this? I saw someone mention that if objects in Tableau has same names, it can mess up the structure. Is this the reason? If it is, are there any plans to address this issue? Because trying to have unique names across thousands of workbooks, charts, datasources, folders and so on seems almost impossible considering collaborative nature of our Tableau server P.S. We’re running on older version of Datahub, so that might be not the case in newer version. That’s what I want to know, because our devops team would like to know if it’s worth to update to fix this issue, or it will stay the same no matter the version
Sometimes even dashboards that has unique name are missing…I don’t understand why and how to fix it Maybe the current structure mess has different reasons affecting it
h
Hey Nikolay ! The behavior is still the same . There is an open feature request for this - https://feature-requests.datahubproject.io/p/tableau-nested-projects-support Like you mentioned, this issue primarily impacts the browsing experience by project hierarchy. Basically all the workbooks in project hierarchy(assuming alphabets are projects ) A/B/C or X/Y/Z/C or P/C or C end up in same browse path, i.e. C. (immediate parent).
m
Thank you! Is there any way to know when (and if) this feature will be developed?
a
Hi Nikolay, we’ll be releasing our roadmap for this quarter soon! In the meantime, we are always open to collaborate on contributions!
m
@hundreds-photographer-13496 Hello, I have an additional question regarding this feature I noticed that same names can conflict not just across folders, but across different entities too For example, in the parent folder “Market assessment” we had a dashboard named exactly “Market assessment”. Data source and a chart of this dashboard was imported in Datahub successfully, because they had different names, but the dashboard entity itself hasn’t been imported. There’s only a folder with this name Or another case, in the parent folder named “General” there’s a dashboard named “recommended_tournament”, and this dashboard also has a chart with same name “recommended_tournament”. But both dashboard and it’s chart hasn’t been imported in Datahub. There’s no other entity or folder with same name in Tableau or Datahub Is the source of the issue the same, a lack of support for nested projects? Or should I add this examples in comments to the feature request, to highlight that not only folders are affected by this? Or maybe create a different feature request?
h
Hey @magnificent-lock-58916 this does not sound like a nested project issue however needs some investigation to be able to root cause this behavior. Can you create a github issue ? Do mention the the complete project hierarchy for concerned charts/dashboards/workbooks along with the
projects
section from tableau recipe .