Support multiple table extracts in the Tableau .hyper output

[jdrummey]

Tableau v2018.3 introduced multiple table extracts. These are particularly useful for fact table to fact table joins and fact table to entitlement table joins for row-level security where the number of rows created by the join and/or size of join results would be prohibitively large. Also they are useful for fact table to spatial joins where we might have multiple spatial objects (for example custom province/district/health facility catchment) for each row of fact table data.

So in Alteryx I'd like to be able to specify 2+ tables & their join keys and then write out a .hyper multiple tables extract.

Jonathan

[JReid]

This functionality in the publish to tableau server tool would be useful as well.

[jdrummey]

One note re: the original idea - having worked with the Hyper API myself it turns out that we don't specify the join keys in a multiple table extract, we just work with tables.

With Alteryx 2019.4 adding support for Hyper for input it turns out that it also only supports single-table extracts. Here are related ideas around more complete support for Hyper files in Alteryx:

Supporting alternative schema & table names for Hyper files in the Input tool:
https://community.alteryx.com/t5/Alteryx-Designer-Ideas/Input-tool-Support-more-than-Extract-Extract...

Supporting Hyper multiple table extracts in the Input tool:
https://community.alteryx.com/t5/Alteryx-Designer-Ideas/Input-tool-support-multiple-table-extracts-f...

Using the database server interface for Hyper files in the Input tool:
https://community.alteryx.com/t5/Alteryx-Designer-Ideas/Support-database-server-interface-for-Input-...

Support in database tools for Hyper files
https://community.alteryx.com/t5/Alteryx-Designer-Ideas/Support-In-Database-tools-for-Tableau-Hyper-...

[VojtechT]

Hi everyone,

we have released a new tool Tableau Output which does support multiple tables in the hyper extract. However, due to Tableau's limitation user has to provide the tds file for them. Currently, the tool doesn't support Tableau Server On-Premise, but we're going to implement that support soon as well. 

The new tool can be downloaded from Gallery.

Vojta

[jdrummey]

Hi @VojtechT

I'm not sure what you mean by "due to Tableau's limitation"? The .tds is only required for publishing entire Tableau data sources, it's not required for local output (and the new Tableau Output macro doesn't require a .tds). I think this could be more clear in the docs.

What's the best route to get support for this macro? I tried a really simple use case with one spatial field and I'm getting a "KeyError: 'spatialobj'" with a Python traceback in the log. Here's a zip file w/both the flow and the log: https://path.box.com/s/h7iauy2ef3fir0owwwmwhrjoadntm0nl

Jonathan

[VojtechT]

In Gallery you can find Tableau Output tool, which provides support for creating hyper extract with multiple tables in it. 

The tool supports both Tableau Server in Cloud and On-Prem.

[VojtechT]

Hi @jdrummey ,

I mean what you're saying - that the tds is required when uploading to Server. But you can also create the hyper file locally, in which case you do not have to provide the tds file, as you mentioned. 

The spatial objects are unfortunately not supported by our Python SDK at this moment. The tool should support WKT for spatial objects, though.