SuperTables
Discover interactive Excel-like tables and allow users to decide how to organize their data!
With the SuperTables extension for Tableau, you can offer your dashboard users the power of interactive and dynamic Excel-like tables that allow users to decide how to organize and analyze their data in a flexible grid using the features just like in Excel without leaving Tableau! Enrich your dashboards with the SuperTables extension for Tableau and allow your visitors to do their own analysis with the summarized data of your visualizations.
Some of our valued customers
“I have over a thousand users on Tableau, and we are still growing at a rapid pace. SuperTables, has made Tableau so much more accessible to people that are used to Excel and have raised their game for how they think about data and analytics in our company. Because it’s so easy to use, even savvy business users are able to incorporate it in a matter of minutes.”
Countless features

There is more!
- Filter, Parameter and Highlight Actions
- Conditional cell formatting
- Header grouping
- Prefix and suffix
- Tooltips for headers
Using a table in your dashboard comes in handy if you want to provide your dashboard users with extra context on their visualization. Drag the SupertTables solution to your dashboard, configure the data(sheet) to feed the table and provide your dashboard users with some amazing details. You’ve never seen a more powerful table!
NEW: Enhanced Accessibility Mode
With enhanced accessibility mode all rows and columns will be rendered even if they are not visible in the screen. This makes using SuperTables with screen readers seamless. Animations will be disabled when using enhanced mode as it is complex to use screen readers with dynamic contents. For specific questions related to ARIA, please check the FAQ below.
Saving hundreds of hours a week by using SuperTables

SuperTables brings a lot of value by reducing the number of dashboards that have to be created and maintained. For Mario, the data process became faster and hundreds of hours per week were saved by not constantly being asked to make a report or having to hire an expensive contractor.
Are you ready to turn the Tables?
Support
Our team is committed to your success with Infotopics | Apps for TableauContact us by mail:
Latest news
- Free with limited features
- –
- Tableau Desktop – Tableau Server – Tableau Cloud
- Always up to date
- Requires internet access
- Instant Download
- Cloud based / 99% uptime
- Support by ticketing system
Share Cloud
- Billed Annually
- 14 Day FREE Trial
- Tableau Desktop – Tableau Server – Tableau Cloud
- Always up to date
- Requires internet access
- Instant Download
- Cloud based / 99% uptime
- Support by ticketing system
- Bronze: 0-50 Tableau users
- Silver: 50-150 Tableau users
- Gold: 150-300 Tableau users
- Contact us for a custom quote!
Enterprise
- Billed Annually
- On premise trial
- Tableau Desktop – Tableau Server – Tableau Cloud
- Always up to date
- No internet access required
- Additional enterprise features
- On premise installation
- Personal enterprise support
- Personal enterprise portal
Enterprise-Ready Security
When company policy or IT security requires an on-premise installation / integration of the extension, we can help you organize it. This is particularly useful when your Tableau Server is not granted internet access, or you need to be in full control of the usage and management of your extension.
On-premise installations allow you to be in control of infrastructure, privacy, governance, and to comply with company policies. It also allows the installation/hosting of several individual extensions. Please contact us for more information regarding on-premise installation of our extensions.
FAQ
Known limitations
Navigation to pinned rows/columns
Screen readers assume that the visual and DOM element order are identical. Specifically, when you pin a row/column, it causes elements to be rendered in different containers. This is why you cannot use screen readers to navigate into a pinned row/column cells, as in fact, this means they’re rendered in a different element from the rest of the columns/rows which are scrollable.
Limitations announcing the correct column name in grouped columns
Even though all aria tags have been applied to the necessary elements, some screen readers have trouble navigating the tags when the structure of the grid gets more complex (eg. grouped columns). This is the reason why there are some limitations announcing the correct column names.
No announcements of state change of a grid cell or grid header
Some screen readers will not recognize changes that happen to an element that is currently focused (including children of this element). So in order to detect changes (eg. sorted state, updated labels, etc…) you will need to move focus to another element and back.
Check the Product Guide for more information.
Aria Rule: Bypass repeated blocks by setting role to “Main”
Since web sites often display secondary, repeated content on multiple pages (such as navigation links, heading graphics, and advertising frames), keyboard-only users benefit from faster, more direct access to the primary content on a page. This reduces keystrokes and minimizes associated physical pain. Since SuperTables is just one page and there are navigation shortcuts to move around. This does not affect the accessibility of SuperTables. Check the Product Guide for more information.
ARIA Rule: configuration option to enable/disable Accessibility optimization for the grid
You can use the “Enhanced accessibility option”, if you wish to optimize SuperTables for accessibility. It in general disables the column and row virtualization. Which in results generates all cells in the DOM thereby you will see considerable reduction in performance. There may be 2 scenarios when you may wish to disable column virtualization (if you prefer).
1) Auto-sizing of all columns. This will ensure that all columns, and not just the columns which are rendered on the screen, will be resized.
2) Support for a11y. This is to prevent any potential issues for keyboard navigation and screen readers (https://www.a11yproject.com/).
Check the Product Guide for more information.
ARIA Rule : A Main landmark should be available in the SuperTables structure
Screen reader users can use keyboard shortcuts to navigate directly to the first h1, which, in principle, should allow them to jump directly to the main content of the web page. If there is no h1 or if the h1 appears somewhere other than at the start of the main content, screen reader users must listen to more of the web page to understand its structure, wasting valuable time. To tackle this this issue we have added an invisible heading which will help the screen reader to easily recognize the SuperTables container. Check the Product Guide for more information.
Aria Rule: landmarks to element
Navigating a web page is far simpler for screen reader users if the content splits between multiple high-level sections. Content outside of sections is difficult to find and the content’s purpose may be unclear. However, in this case, SuperTables stand as one single element instead of website where contents are spread of multiple sections. Check the Product Guide for more information.
ARIA Rule : For every column header ARIA parent role must be added.
By default, SuperTables has column header’s role described as role=”columnheader” - element containing a column header. For all the members cells there is an ARIA-Describe By tag which explains where it belongs. However, even though all aria tags have been applied to the necessary elements, some screen readers have trouble navigating the tags when the structure of the grid gets more complex (eg. grouped columns). This is the reason why there are some limitations announcing the correct column names. Check the Product Guide for more information.
ARIA Rule : Page must contain a level-one heading
Generally, it is a best practice to ensure that the beginning of a pages main content starts with a h1 element, and to ensure that the page contains only one h1 element. However, ARIA Standards also mentions that in case if iframes, the heading can be an <h2> or <h3> so we have added an invisible heading, which tells the screen readers that it is the SuperTables container. Check the Product Guide for more information.
- Use an (Hyper) extract
- Remove columns from your datasheet that are of no use in your extension
- Do not format your datasheet but use this method to build a better performing datasheet: https://www.youtube.com/watch?v=JJ-S96rGcFo&list=PLk7W-GiyTaBDQX7z868t8R1nrNS3vM1dE&index=5
- Filter your datasheet (to reduce the number of rows) to a specific period, department, product category etc.
- Change the level of detail in your datasheet (to reduce the number of rows). Use Monthly aggregations instead of showing all records on a daily basis for instance.
- Apply user filters (or Row Level Security) tu reduce the number of rows on the datasheet
- Avoid using complex calculations in your datasheet (table calcs, LOD calcs, data calcs etc.)
Yes!
We will definetely investigate possibilities and would love to cooperate about this!
- Make sure the extension domain is whitelisted on Tableau Online/Server.
- Webserver services content with proper
X-Frame-Options
andContent-Security-Policy
headers. - Extensions feature is turned on, on Tableau Online/Server.
- The Extension server/domain has a valid SSL Certificate.
- Tableau Online/Server has access to the Extension Server to load the extension.
You can find any issues by doing the following: While running on Tableau Online/Server in the browser open the “console” tab in Chrome Developer’s tools. To open the developers tools can be done via: Hamburger menu top right > More Tools > Developer tools. Refresh the page while the developers tools is open. Now you can see if there any issue while embedding.
Note: Tableau will show warnings with something like: ‘cannot load source map’ by default, these are not caused by our extensions. They can be identified based on the domain of the url that it warns with.
Make sure to follow our installation guide to setup the right configuration!
Common issues
CSP Header error or X-Frame-Options error.
Make sure the following headers are properly set:
X-Frame-Options: SAMEORIGIN
Content-Security-Policy: frame-ancestors 'self' *.online.tableau.com;
For Tableau Server
*.online.tableau.com
should be your domain.
Check all security headers with the following website: https://securityheaders.com/
Tableau Server/Online does not support the embedding of web elements (and extensions are also web elements). Tableau Desktop does and I know Tableau Software is working to enable this feature on the Server platform as well. Unfortunately currently we have to do without the embedding of extensions in the PDF and image exports.
Last weeks, you can find the changelog with release dates here: https://appsfortableau.infotopics.com/support/changelogs/
It loads data on popup, but on Tableau Server/Online you can keep the popup open and mark selections will only update the data. So in case of performance, nothing changes when the popup is opened.
Governed and Secure Products
All our products are secure as we comply with ISO 27001 and NEN7510. Your data and user access is secured under Tableau’s governance. Our products are 100% secure on premise or private cloud deployed and facilitate your workflow in Tableau, eliminating the need to move to external programs.



