Right now we can create Tableau extract files (.tde), but cannot read them into Alteryx -- this limits the partnership of these two companies. Please add the functionality to import .tde files, Best, Jeremy
We're thrilled to announce that, through the integration of Tableau's new Hyper API with the Input Data tool, you can now read Tableau Hyper Data Extract (.hyper) files as an input data source from within Alteryx Designer! We've been tracking this request for a long time and were quick to act once Tableau enabled this functionality.
The ability to read Hyper files is currently in beta and can be accessed from Alteryx Beta Program > Alteryx Analytics Beta 2019.4 > Designer | Tableau Hyper API Integration.
Thank you to @jeremy_dalletezze and everyone who has commented or liked this idea! We appreciate your participation and enthusiasm for Alteryx.
- Can we expect the ability to read from hyper extracts stored on Tableau server as well as those stored locally?
- Is there a provision to support Update and Delete records from a hyper extract? I understand that Tableau has opened hyper to full CRUD from systems other than Tableau, so technically it should be possible.
Can we expect the ability to read from hyper extracts stored on Tableau server as well as those stored locally?
Extracts would need to be manually downloaded from Tableau Server and stored locally. This is a great idea though and we'll keep it in mind as we evolve this capability.
Is there a provision to support Update and Delete records from a hyper extract? I understand that Tableau has opened hyper to full CRUD from systems other than Tableau, so technically it should be possible.
The Hyper output support includes: Create New Extract File, Overwrite Existing Extract File (Create if does not Exist), and Append to an Extract File.
Can this be extended to .hyper tableau extract files not just the legacy .tde. please ignore this comment. Just realised I missed the request and implemented note on .hyper
Hello @KylieF , I'm trying out the read Hyper files feature in 2019.4 and it's got two serious holes:
1) It only reads single table extracts. We can create multiple-table extracts through the Tableau Desktop interface as well as the Hyper API, if we do then we get a "no fields found" error on that extract file.
2) As far as I can tell the only schema.table name supported by Alteryx is "Extract.Extract" (which is what the older Extract API 2.0 generated). The Hyper API defaults to "public" as the default schema and table names are user entered so if I've used the Hyper API to add a table called "Facilities" then by default I'll get "public.Facilities" as my schema.table name. When I open that in Alteryx I get a "no fields found" error.
My first wish is that the Input step support multiple schema/multiple table hyper files, so when the user connects to the Hyper file the Input step would at least allow the user to select the schema and then the table. That would at least enable me to be able to work with multiple table extracts as well as Hyper files generated by the Hyper API.
Should I submit a new Idea for this?
(My second wish would be that the Input step for Hyper files actually uses the schema/table/query interface used for databases, since the Hyper engine supports queries), and my third wish would be for In-DB tools to work on Hyper files.)