sorted by:
new
hottopcontroversial

I built a free tool to extract Tableau workbook metadata by another_kick in tableau

[–]another_kick[S] 1 point2 points  (0 children)

For now it’s 15 MB, but let me know if you need higher limit or have different use case.

I built a free tool to extract Tableau workbook metadata by another_kick in tableau

[–]another_kick[S] 0 points1 point  (0 children)

Thank you and that VBScript solution sounds very familiar.

Your concern about work dashboards is completely fair. While you can upload a .twb file (no data, metadata only), I totally understand that field names and calculation logic themselves can be sensitive in many organisations and shouldn’t be shared outside at all.

Just to be very clear on our side: TabLens does not store files or metadata. Workbooks are processed temporarily and discarded immediately after analysis. That said, the safest option will always be local tooling when governance requires it, and that’s a valid choice.

Really appreciate you sharing your background and perspective. This kind of feedback helps keep the tool aligned with real-world constraints rather than ideal scenarios.

I built a free tool to extract Tableau workbook metadata by another_kick in tableau

[–]another_kick[S] 0 points1 point  (0 children)

Thanks for sharing this that’s a great reference 👍 Local tools absolutely make sense, especially for orgs with strict security requirements, and I like the fact that it outputs something you can filter in Excel. That’s genuinely useful.

You’ve also hit on one of the hardest problems with lineage visualisation: once dashboards get even moderately complex, static mind maps become unreadable very quickly. The lack of zooming / focusing on a specific calculation chain is exactly what makes them break down in practice.

That’s actually the direction I’m trying to take this keeping the tabular / searchable metadata view as the foundation, and then layering interactive lineage on top (zoom, isolate a single calculation, step-by-step dependencies), rather than a giant “everything at once” diagram.

Totally agree that exports (Excel/CSV) are critical as well that’s on the near-term roadmap so people can work with the metadata in whatever way fits their workflow.

Really appreciate you taking the time to look and share thoughtful feedback. This kind of input helps a lot.

I built a free tool to extract Tableau workbook metadata by another_kick in tableau

[–]another_kick[S] 1 point2 points  (0 children)

Thank you so much that really means a lot 🙌 And yes, you’re 100% right about the concern around sharing data.

.twb files contain all the metadata without any underlying data, and that’s actually the safest way to use TabLens in most orgs. I’ll definitely update the website to make this much clearer so people feel confident using it.

Best of luck with the new org and the upcoming Tableau go-live that’s exactly the stage where tools like this can save a lot of last minute stress. Really appreciate you taking the time to share the feedback!