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
I'm surprised this is not part of Alteryx's core capability. Seems like it would be a no-brainer. Blaming the limitation on Tableau is a little weak, considering the partnership that already exists between the two companies. Alteryx should have pushed for this capability.
Hi there this would be game changing improvement. While it is true that there are work arounds (writing to two places (tde & yxdb) it would be so much cleaner and efficient to be able to read the tde itself as input. What can be done to get this one pushed forward and generally available? Regards and thanks.
Thanks for putting it up to vote on Tableau @michael_perillo . You have my vote for this one. I end up doing complicated pulls of cross tabs via .csv from Tableau to validate against the raw data. I would like to use it determine whether I can just append to the .tde (a capability with the publish to Tableau Server Macro) or if I need to replace it.
Currently Alteryx Designer is capable to create a .tde file as an output that can be opened into Tableau desktop, but it cannot read .tde (Tableau Extract file) as an input into Alteryx.
This would be a good functionality to add going forward.
There is not an ideal way to read Tableau Data Engine files, this is intentional by Tableau, they do not see their software as middleware, they are firmly endware. Data goes in, but does not come out.
While this idea is around read data from Tableau, I had an idea on writing spatial data into Tableau, which I hope to get more support from the community. As a tableau user who is dealing with a lot of spatial data, I had an idea around "Support WKT as Spatial object + output spatial object in TDE (now Hyper) file directly" on09-27-2017. (FME can do this, as it have better understanding of Tableau's spatial data type. I guess the reason Alteryx is not supporting the functionality is due to the lack of support to Well Know Test. So I combined the two ideas into one.)
Interesting idea, and I truly understand why this Idea was submitted.
But there is a reason to why this idea has status Partner Dependent, it is not because Alteryx can't or won't do it, but because Tableau basically does not allow anybody but Tableau to read .tde or .hyper files. What Tableau allows is for others to write to their data formats but not read from them.
So technically there is noting that prohibits Alteryx from reading .tde or .hyper files, but you would be violation the Tableau license.
These dataformats are propriety of Tableau, and all though there is a provided API for these formats, ir only allows you to create the files, not read them 😔
Since this thread began, Tableau introduced their PREP product that fills a lot of their gaps that Alteryx occupies and it inputs tde/hyper files making it better in that one way that Alteryx. Seems like time to re-negotiate with Tableau.
I suppose I could extract using Tableau Prep then work with Alteryx, but why should I have to do that??