Good Morning Ariel,
In general your strategy seems sound.
In my role I work with many new Tableau Online customers, such as yourself.
The first place I would investigate is the data source. Are you using a Tableau Data Extract published to your Tableau Online Account?
If not, using one is the best possible single thing you could do for performance.
Beyond that, it's more of a diagnostic and trouble shooting art. The best resource, bar none, is the document in the following link:
Performance and Related Best Practices
Best Practices for Designing Efficient Workbooks (Best document on designing for optimal performance):
If this response is helpful, or answers your question, please mark it as such so that others can find it quickly.
Tableau Online Deployment Advisor
Good morning Steve and thanks for the quick answer.
I'm using a live connection.
So I asume that I should change it for a daily extract right?
Here is what I advise customers: Only use live connectors with Tableau Online if the primary business requirement is to have as near real-time data as your source can provide. And in that case, use the document I provided you for guidelines to tune and address performance considerations on the datasource side.
That said, if your audience will accept daily data updates/refreshes, yes absolutely use the Tableau Data Extracts and schedule for a daily refresh. That will make a significant improvement in your load and response time.
But still, look at the Best Practices For Designing Efficient Workbook document to see if you can make gains in other areas as well.
Another way to improve performance is to take a look at this blog here:
Can you describe a bit more how your workbooks are set-up and what your data source is?
besides the performance issues what do you think on the idea to mount via iframe the dashboards on a web page to easy sharing?
Honestly, I don't much see the point when the Tableau Online interface already provides easy access to the views.
Maybe, if the viz is surrounded by a substantial amount of other content, such as an article or supplementary materials, that would make a lot of sense. But in terms of distribution, it seems that the iFrame simply adds another layer of complexity.
This is pure opinion, so feel free to take it with a grain of salt.
The questions I have: why did you choose to use an iFrame instead of Tableau Online? What are the benefits? What need does it satisfy?
I have 6 dashboards and plan to have a few more.
using the tableau online intereface requires more time to navigate.
my solution has a menu on the left so to change from one to another it's only one click
Thanks for the additional info.
You have a few alternative options:
- Create a single workbook and enable the show tabs option when publishing
- Creating a Table of Contents to Navigate to Other Dashboards | Tableau Software - Create a table of contents dashboard
- Integrate a table of contents option into your existing dashboards: https://www.interworks.com/blog/rrouse/2016/01/04/creating-collapsing-menu-container-tableau
The iFrame makes a bit more sense now in the grand scheme of your design. I personally feel that navigation is less of an issue than better performance overall. People wil spend the time to navigate more than they will spend the time to wait for a dashboard to load. Another question, what are your end-users asking for? Is it navigation, performance, time to iteration?