2 of 2 people found this helpful
I'll leave this to the Desktop experts but to start off this conversation:
- What version of Desktop?
- Explain in detail what you mean by "...avoid crashing (avoid crashing in presentation)"
- How many worksheets are being used for each dashboard? Because every worksheet in a visible dashboard needs to be rendered for that dashboard. 25 dashboards is a lot...not very dashing, indeed...
I'd complete asking:
How many data sources has this .twbx (130 mb plus)?
Are they blended? It only work with extracts?
Depending on your situation i would recommend break it in others and build one to work as index and make a link between them.
1. It's 9.3
2. I've experienced once in presentation, the file crashes in the middle of the meeting.
It literally stops, and a pop-up message shows saying Tableau currently stops.
3. One dashboard has a minimum of 3 to 4 worksheet.
Well, this dashboard is for Monthly dashboard.
Size of the twbx has nothing to do with performance or stability - it only affects initial startup time. Twbx gets unpackaged into twb XML and all included files (text, excel, extracts, images etc).
Performance (and stability, sigh...) is affected by individual datasource and viz/dashboard composition.
If you have more specific question about performance - we can dig deeper.
Also, I would definitely want to know more about that!
I've manage to decrease the size of the file, and now the file is running much better.
I think, some of the issue comes from the calculation.
And some of the the dashboard comes from different workbook, I've just merge all the needed visualization for the monthly dashboard.
From 130 mb, it's 110 mb.
Think about breaking it in more dashboards.
Cannot do that, because we have this template to follow.
You can create a dashboard just to do links and open on the same window.
It would make users not realize to be in different dashboards. If you could do that probably would solve the problem.
You solved for now but it tends to happen again.
I get the idea, thanks