This has probably been mentioned before, but in case it hasn't....
Right now, if the dynamic input tool skips a file (which it often does!) it just appears as a warning and continues processing. Whilst this is still useful to continue processing, could it be built as an option in the tool to select a 'error if files are skipped'?
Right now it is either easy to miss this is happening, or in production / on server you may want this process to be stopped.
Hi Alteryx community,
It would be really nice to have v_string/v_wstring and max character size as a standard for text columns.
it is countless how many times I found that the error was related to a string truncation due to string size limit from the text input.
Thumbs-up those who lost their minds after discovering that the error was that! 😄
Currently, Input tool, Flat File format, only support String and V_String field data type.
Note: UTF-8 is a supported character set.
I would like to request W_String and VW_String be supported, given UTF-8 is a supported character set.
There is a workaround to do this, meaning Alteryx already does this, albeit through CSV input format, using a non-existent field separate, e.g., | is what I used, or in this link, the NUL or \0 character.
When using the output data tool, it would save me and my cluttered organizational skills a lot of effort if the writing workflow was saved as part of the yxdb metadata.
I've often had to search to find a workflow which created the yxdb. I tend to use naming conventions to help me, but it would be easier if the file and or path was easily found.
The current version of the Publish to Tableau macro retrieves an API key at the start of the workflow run. Often times the workflow may take several hours to run before it's ready to write to Tableau by which time the API may have expired. (I think the default tableau server setting times out in 2 hrs) It's one of those soul crushing "I should've forked the output!"
Sample Log Error -
The idea would be to change when the macro obtains the API from when the workflow is initiated to just before the workflow is ready to write to the Tableau avoiding these timeouts.
(If you're having this issue in the meantime you can have your Tableau server admin up the timeout)
Please add official support for newer versions of Microsoft SQL Server and the related drivers.
According to the data sources article for Microsoft SQL Server (https://help.alteryx.com/current/DataSources/SQLServer.htm), and validation via a support ticket, only the following products have been tested and validated with Alteryx Designer/Server:
Microsoft SQL Server
Validated On: 2008, 2012, 2014, and 2016.
This is one of the most popular data sources, and the lack of support for newer versions (especially a 2+ year old product like Sql Server 2017) is hard to fathom.
ODBC Driver for SQL Server/SQL Server Native Client
Validated on ODBC Driver: 11, 13, 13.1
Validated on SQL Server Native Client: 10,11
Please could we add Qubole to supported data sources,
It is possible to connect to Qubole via ODBC Connection
However, this error message is often returned on a query: InboundNamedPipe GetOverlappedResult: The pipe has been ended
I've been advised by Alteryx Support that this is likely due to the ODBC driver.
If it's possible to add Qubole to supported data sources it would save a lot of time committed to troubleshooting this error.
All the best
Referencing the previous idea: Inputs/Output should have the option to read/write a compressed file (ZIP or GZIP)
This idea has been implemented for inputting .zip files. However, we still need to use the run command workaround for outputs. It's very common for many users to want to output their .csv, .xlsx, .pdf to a .zip. The functionality would also need to extend to Gallery.
See the following links for people that are looking for this type of functionality:
Feel free to merge this idea with the previous one for continuity.
Alteryx 2019.4 added support in the Input tool for Tableau .hyper extract files. The tables stored in the .hyper files have a schema and a table name. Tableau's old .tde files and Hyper files created by Alteryx & Tableau Desktop use "Extract.Extract" as the schema.tablename. However when using Tableau's Hyper API the default schema is "public" and the table name is arbitrarily specified by the user or application.
This has two impacts:
1) Without this support Alteryx can't open many .hyper files created by other applications. By way of example I've attached a sample .hyper file (in a .zip because the community software doesn't allow .hyper files) that has the schema.tablename "public.table1".
2) Also support for names beyond Extract.Extract is required in order to support multiple table extracts (submitted as a separate Idea).
Please update the Input tool so the user can select the particular schema and table name from the .hyper file.
Tableau's Hyper file structure can store multiple tables and the published Hyper API exposes a SQL interface. Therefore instead of supporting the standard file-based interface (like text, Excel, etc.) for connecting to Hyper files how about supporting the database server interface used for MS SQL Server, PostgreSQL, etc. so we can select the schema, tables, fields, or even write SQL?
Two related ideas:
Supporting alternative schema & table names: https://community.alteryx.com/t5/Alteryx-Designer-Ideas/Input-tool-Support-more-than-Extract-Extract...
Supporting multiple table extracts: https://community.alteryx.com/t5/Alteryx-Designer-Ideas/Input-tool-support-multiple-table-extracts-f... to support multiple table extracts for the Input
Hi Alteryx 🙂
When you set maximum records per file, the filename gets _# appended. Great! But in reality you get:
The first filename doesn't get a number. I think that it should.
Hi GUI Gang
At the moment, I have a lovely formatted XLS with corporate branding, logos, filled cells, borders etc. The data from the Alteryx output needs to start in cell B6. I have tried the output tools to this named range, but Alteryx destroys all the Excel formatted cells in the data block.
As a workaround on the forums, many Alteryx users pump out to a hidden "Output" tab, and then code =OutputA1 in the formatted sheet. This looks messy to the users who then go hunting for the hidden tab. Personally I end up pumping the workflow out to a temporary CSV file. Then opening that in Excel, selecting all, and then pasting values in the pretty Excel file.
This is fine for one file, but I need to split the output report block by a country field and do this 100s of time for each month end.
Please can we have a output tool that does the same as my workaround. Outputs directly from a workflow to a range in Excel that doesnt destroy the workbook's formatting.
When you are navigating within the text input tool, it would really help if we can navigate to next/previous cell upon pressing right/left arrow keys. If the cursor is at the end of a cell value then pressing the right arrow should go to next cell. Similarly, if the cursor is at the beginning of value of a cell, it should go to previous cell.
I think it would be really good if we have the option to cache data for few days, as currently cached data gets deleted when you close the workflow.
It’s useful to catch data when developing reports with input data from data warehouses or big data platforms , as sometimes it can takes a while to extract the data.
If we have the option to cache data for few days or delete when it’s not required anymore, it can save a lot of time, the next time when you open the workflow to complete the development or make changes to your workflow.
Alteryx 2019.4 introduced support for Tableau's .hyper extract format, however it only supports single table extracts. .hyper files have supported multiple tables since mid-2018, so I'd like Alteryx to support that as well.
Here are a couple of current use cases (as of February 2020) and one future one.
- We have malaria incidence data that is joined to multiple sets of spatial data. Doing all of the joins in the extract creation process to build a single table extract is not possible due to processing time & memory constraints, so we use a multiple-table extract.
- There are multiple ways to do row level security in Tableau. A common way is to have separate tables for the data & the entitlements and then use calculations at run-time to filter the data, and for that having a multiple table extract is ideal.
- In 2020 Tableau will be introducing new data modeling capabilities (this was first demoed at the 2018 Tableau Conference, there were sessions on it at the 2019 Tableau Conference) where one goal is vastly improved performance for large fact table to fact table joins where previously we'd have to do much more data preparation. This is another case where multiple table extracts would be useful.
I've attached a sample Hyper file with two tables in the extract (it's zipped because the Community site doesn't accept .hyper files).
Supporting alternative schema and table names in Hyper extracts https://community.alteryx.com/t5/Alteryx-Designer-Ideas/Input-tool-Support-more-than-Extract-Extract... is a prerequisite for this because by definition multiple table extracts have multiple table names.
A related idea is supporting multiple table extracts for the Output tool: https://community.alteryx.com/t5/Alteryx-Designer-Ideas/Support-multiple-table-extracts-in-the-Table...
the SQL Editing screen has recently been changed (thank you @JPoz and team!) - and now has syntax indenting and keyword coloring.
Could I ask for a minor change:
- The tool seems to be doing a word-wrap even if the container doesn't need it - for example in the screenshot below, the entire on clause can fit on one line because I've expanded the window so that it doesn't need to wrap.
- Could you also default to putting the ON clause for a join 4 spaces indented underneath the join clause? worked example below.
Could we use a default structure for queries where the on part is indented underneath the Join?
inner join table2
On Table1.key = table2.key
and table1.keyb = table2.keyb
inner join table3
on table3.key = table1.key
and table3.date = table1.date
The Tableau Hyper API supports regular SQL queries, see https://help.tableau.com/current/api/hyper_api/en-us/reference/sql/index.html and https://help.tableau.com/current/api/hyper_api/en-us/docs/hyper_api_reference.html for more information. Being able to use the In-database tools for querying Hyper would let us take advantage of Hyper's internal optimizations just like other databases.
Hi Alteryx -
It would be nice if we could include some of the sampling functions in the Input tool. For example, I am creating a random 10% sample from a large data set but in order to do this I need to first input the entire data set then create the sample. This takes processing time and effort. Ideally, in the Input configuration I would like to see the option to create samples without having to load in the entire data set. Similar to Record Limit but with added functionality.
MemSQL is a very popular high-velocity; high scalability database which is often used for analytics: https://portal.memsql.com/
However, when attempting to make a connection to MemSQL, Alteryx throws the error "Get Table List Error: Error opening "SHOW VARIABLES LIKE 'aurora_version'": No Columns Returned."
From discussions with the support team at Alteryx - it appears that this is due to Alteryx presuming that the database is a MySQL database (because MemSQL also uses the MariaDB ODBC driver) and then sending a followup query to identify system version before making a connection - however MemSQL does not support this value so the connection fails.
- Please can we add the ability to connect to MemSQL without this error (i.e. trap this error and identify the DB version)
- Please can we give an advanced view to Alteryx users so that they can see this additional traffic and change this where needed?
NOTE: By providing an advanced view - users can understand and diagnose / fix behaviours that Alteryx assumes by default, but which are not always relevant or useful. An example of this is that on MS SQL Alteryx tries to open a cursor on columnstore tables by default and you have to use a workaround - please can you give us the ability to see and change these under-the-covers behaviours that are presumed by default.
- It may be useful to the Alteryx corporation to reach out to MemSQL and add Alteryx to the list of applications that can be used with MemSQL:
- Fire up a MemSQL cluster (easiest is to get a trial cluster using the link above, or use an internal DB)
- Connect to this DB using the MariaDB ODBC connector (as recommended by MemSQL)
- Test this connection works with an ODBC compliant app like Tableau; Excel; etc
- Then attempt to connect using Alteryx - see screenshot below.
Hi Alteryx 🙂
When I select fields within a BROWSE or Browse Anywhere, it would be nice to be able to highlight and deselect a range of fields instead of having to check/uncheck fields one at a time. Yuck!