Alteryx Designer Ideas

Currently it's possible to use the Output tool to output to either a sheet, a place in a sheet or a named range in Excel, but it is not possible to output to a preformatted excel table - it would be really good if the output tool had an option to output to [Table1] in an Excel workbook for example. This enhancement would be incredibly helpful for reporting purposes.

When using an OUTPUT tool, you can currently only output to one (1) format.  My idea is to allow for a checkbox to create a YXDB file format when you output to another format.  In many instances a copy of the CSV data in YXDB file format is needed.  Creating another output requires another tool with nearly identical information.  This is my backup copy to what I sent the customer is an example.

Cheers,

Mark

Would love to see an option to disable a specific Output tool (rather than the global "Disable All Tools that Write Output" option). I'm envisioning the inverse of the Email tool, where there is a checkbox to enable Email... rather, the Output tool could have a check box that would disable that output (and ONLY that output), similar/consistent with the "Disable All Tools" function. A "Disable This Output" check box. The benefits would be a quick way to make sure not to overwrite something in one output (but still getting all the good content in all the other outputs) rather than having to go through the multiple clicks of adding to a container and then disabling the container. Could have benefits for connecting with Action tools/interface toggles as well. It would likely need to contain the same/similar formatting in Designer to indicate it has been disabled, though maybe a slightly different color so you could tell it was disabled differently? 

(On a similar vein, would love to take this opportunity to bring up my favorite idea-that-has-not-been-implemented-yet-that-would-love-your-vote-and-attention, implementing a Warning that outputs are disabled when posting to Gallery...)

Cheers!

NJ

Here's a reason to get excited about amp!   Create a runtime setting that gets Alteryx working even faster. 

when you configure a file input you see 100 records.  Imagine the delight that after you run your workflows all input tools are automatically cached.  You run so much faster. 

now think of the absolute delight that even before you run the workflows that a configured input tool causes a background read off the input data.  Whether it is a new workflow or an opened existing flow that reading can start ahead of the time button. 

what do you think 🤔?

In normal output tool, when file type is csv, it is possible to custom select the delimiter.  It would be great to be able to have the same option in the Azure Data Lake output tool, so for example you can write a pipe delimited file to your ADLS storage account.

As per a recent discussion (https://community.alteryx.com/t5/Alteryx-Designer-Discussions/Geopackages-Can-Alteryx-Open-GeoPackag...), please add the GeoPackage datatype to the Input tool.

For reference, the open-source project ogr2ogr has this functionality. (https://gdal.org/programs/ogr2ogr.html)

Thanks!

Hello - The Input Data tool allows you to import a list of sheet names, but it doesn't let you import a list of named ranges. I'm proposing the Input Data tool allows you to import a list of named ranges for as many Excel file formats as possible. Right now when I go to import say an xlsx or xlsm the Input Data tool allows me to select from a drop down of named ranges, so it seems the functionality is already there. I am not aware of a reasonable approach to getting a list of named ranges other than opening up the Excel file as XML, specifically xl/workbook.xml - however, I've ran into issues with this approach providing sheet names instead of named ranges (unsure why but I posted about this here https://community.alteryx.com/t5/Alteryx-Designer-Discussions/How-do-I-get-a-list-of-all-named-range...)

If we were able to import a list named ranges I think the benefits are obvious. The one that really stands out to me is that if you have a standard when creating named ranges (for example "prefix_name1, prefix_name2" etc... you could search for specific prefixes to find the named ranges available. In a large portfolio of models deploying such a standard the total universe of named ranges might not be known ahead of time except the prefix to search. I'm curious if this resonates with others.

Thank you

Hi,

It would be helpful to improve the tools regarding connections, for example:

In a snowflake data connection tool, it would be good to have the form to fill with the necessary parameteres of warehouse/role/etc as shown in the driver configuration, instead of setting all this details in the driver or manually in the connection string (and for snowbl (bulk) the connection string is not applying the adicional parameters at all). Also for bulk output we would like to have the DSN-less option available.

Regards.

It would be great to have an option in the Output Data tool to write the workflow name to the Info properties of Excel outputs.

Maybe something like this:

So that whenever you open an Excel file you always have a way of finding the name of the workflow that created the file.

This would make it so much easier as I often have to share Excel files with colleagues and customers and then need a way of tracking them back to workflows weeks or months later.

This is a QoL-request, and I love me some QoL-updates!

While I'm developing I often need the output of a workflow as input for the next phase of my development. For example: an API run returns job location, status, and authentication ids. I want to use these in a new workflow to start experimenting what'll work best. Because of the experimenting part, I always do this in a new workflow and not cache and continue in my main flow.

Writing a temporary output file always feels like unnescesary steps, and tbh I don't want to write a file for a step that'll be gone before it reaches production. Esp if there is sensitive information in it.

Thanks.

The Output tool currently creates a zero-row file if you filter all the rows out (an empty file)

However - there's a very common need to say "don't generate a file at all if there are zero rows" - for example if you are generating a "Daily Details" file and there are no daily details today, you want to suppress this file.   This frequently trips up newer users since the only way to suppress a zero-row output file today is to it with macros.

Could you add a flag to the output tool to "Suppress empty files" so that if there are no rows to be written, Alteryx does NOT create an empty file?   This way the user can be in control of what to do with empty record sets?

It would be really helpful to have the ability to read in a Header from an Excel file as part of the Excel file.  I am not referring to column names but the actual Header on the file as this can contain important info to be appended to the data.  This could be an additional checkbox in the Input tool for excel files to read in the header and append to the data as a field.

Currently, a workaround process to do this is to make a copy of the xlsx file and rename as file.zip.  Then unzip the xlsx file and open the sheets as xml files where the headerFooter child element is read in.  Then the header info is appended to the Excel data file which is read in separately in another input tool. 

Would be much more efficient if this was simply a checkbox in the Input Data interface and the Header read in with the data.

DearAlteryx team and community,

all the best for 2021!

Thank you very much for enhancing the output option from Alteryx Designer to Excel keeping the format.

For a lot of my use cases this is very helpful!

Still, there are some use cases left. In case I want to overwrite a calculated/linked number (e.g. calculated prediction) with the Actual number, it would be very helpful to feed into those cells as well. At the moment Alteryx is doing the job but I receive a lot of Excel Errors (xml errors) and a corupt Excel file when overwriting calculated fields/linked fields.

Is there a chance to extend the current setup for all of those cases?

Thanks and best regards

Chhristoph

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:

https://community.alteryx.com/t5/Alteryx-Server-Discussions/Download-Multiple-Outputs-from-the-Galle...

https://community.alteryx.com/t5/Alteryx-Designer-Discussions/Output-files-to-ZIP/td-p/163502

https://community.alteryx.com/t5/Alteryx-Designer-Discussions/Zip-files/td-p/151456

Feel free to merge this idea with the previous one for continuity.

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! 😄

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.

Thanks,

Andy 

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.

• No R versions are mentioned (2008 R2, for instance)
• SQL Server 2017, which was released in October of 2017, is notably missing from the list.
• SQL Server 2019, while fairly new (~6 months old), is also missing

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

• ODBC Driver 17+ is not mentioned, even though it was released in February of 2018. https://docs.microsoft.com/en-us/sql/connect/odbc/windows/release-notes-odbc-sql-server-windows?view...
• SQL Server Native Client is deprecated. It is being replaced by Microsoft OLE DB Driver for SQL Server. However, there is not a mention of Microsoft OLE DB Driver for SQL Server. The latest version of this is 18.3.0. https://docs.microsoft.com/en-us/sql/connect/oledb/release-notes-for-oledb-driver-for-sql-server?vie...

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. 

cheers,

 mark

This idea is to fix one of the Power BI Output tool options for existing datasets.

Currently, if the 'Replace existing dataset' option is selected, the dataset is dropped and replaced with one having the same name.  Problem with this is that any reports or dashboards using that dataset become invalid (likely due to a changed internal identifier).

Idea is to change the 'Replace existing dataset' functionality to delete & replace the data within a dataset rather than deleting & replacing the dataset itself.

This behavior is described in the following thread & flagged as 'solved' although the workaround isn't practical as a true solution to the issue.  We'd like to see this supported more seamlessly via Alteryx.

https://community.alteryx.com/t5/Alteryx-Designer-Discussions/Publish-to-Power-BI-breaks-linked-Powe...