Alteryx Designer Desktop Ideas

Similar to the setting that you have in many individual tools  (join, append, select, et al) where you can go to options and choose to "forget missing fields" it would be nice where you could go to options for the entire flow and "forget missing fields".

This would remove the headache that you have with large flows where you make a change(s) then have to go back through each and every tool to "forget" within that tool. Yes you could still do it individually, but if you chose, you could also do it universally for the entire flow all at once to all the 'missing fields'. 

Add the remove or add Prefix or Suffix Feature on the Summary Tool because this is where the prefix is added automatically by the Summary tool, so instead of adding a new select tool after the Summary tool to remove the prefix. why not to embed it with the summary tool it self. 

I am working with complex workflows which use multiple files as input, located on network drives. Input tools are Input Data, Directory, Wildcard Input, Wildcard XLSX Input (from CReW macros).

Regularly, I experience very slow Designer when working on the workflows, and slow progress when running the tools mentioned above, especially when working from home. Switching off Auto Configure did not really help because I the column list sometimes does not converge even after pressing F5 multiple times, and when actively working on workflows, I have to press F5 all the time...

In order to speed up both working on workflows and running the workflows, I would like to propose a function "Cache all File Inputs" which loads and caches all file inputs at once. To achieve this state, I now have Cache and Run workflow once per every file input.

Hello all,

As of today, you can populate the Drop Down tool in the interface category with a query launched from a in-memory connection. I would really appreciate the ability to use instead an in-db connection.

Why ?
It means managing two connections instead of one, and finding ways to manage it on server for both of them, etc etc.. Simplicity is key.

Best regards,

Simon

The idea is to have a Run option, where the workflow runs everything up to the selected tool (Like the Cache functionality does).

You select the tool, hit Run Up and the workflows executes everything "before" the selected tool.

That'll make developing much easier, specially when dealing with big workflows and constant changing data.

When loading multiple sheets from and Excel with either the Input Data tool or the Dynamic Input Tool, I usually want a field to identify which Sheet the data came from. Currently I have to import the Full Path and then remove everything except the SheetName.

It would be great if there was an option to output she SheetName as a field.

Hello all,

As of today, Alteryx proposes the Intelligence Suite with amazing tools never seen in a data tool, even OCR, image analysis etc.. https://www.alteryx.com/fr/products/intelligence-suite

But... these wonderful tools are part of a paid add-on. And this is what is problematic :

-Alteryx is already an expensive tool. With a huge value but honestly expensive.

-The tools in Intelligence Suite are not common in data tools because you won't use often. And paying for tools you use once or twice in a month is not easy to justify.

So, I suggest to incorpore Intelligence Suite in the core product. The Alteryx users benefit is evident so let's see the Alteryx benefits : 
-more user satisfaction
-a simpler catalog
-adding a lot of value to Designer, with the ability to communicate widely on the topic.

-almost no cost : most costumers won't buy the Intelligence Suite anyway.

Best regards,

Simon

The JOIN tool could use some love.  Let's consider merging the JOIN and UNION functions into a single tool.  Instead of strictly L, J, and R outputs, we could have an option to allow for all standard SQL joins:

• Cross Join (Warning!!!)
• Inner Join (boring)
• Left Outer Join (saves time configuring Union)
• Right Outer Join (saves time ...)
• Full Outer Join (saves time ...)

Being able to JOIN on case-insensitive values is a big bonus (resisted urge to BOLD and change font size).

Being able to JOIN on date-range is often requested.

Being able to JOIN on numeric-range is often requested.

If we are combining tools, getting UNIQUE on L or R (or both) inputs would also save time.  Most JOIN errors are because the incoming (R) data contains duplicates by KEY.

cheers,

Mark

Hi @NicoleJ 

Currently it's not possible to "switch off" interface tools in the same was as we can with the other tools. This limits the functionality especially within chained apps. If we could switch these tools off it would be much easier for us to tailor the experience by allowing selections to be activated by logic, rather than simply the data therein.

Please Alteryx Gods. I beseech thee!

*lights candles*

Adding a up and down arrow on each column would make it easier and quicker to sort columns then the drop down menu or sort tool

To allow users to pull data from Power BI, eg. datasets and usage data, to allow it to be manipulated in Alteryx. 

Hello!

I am just making a quick suggestion, specifically for the Formula tool within Alteryx.

Often when I am working on a larger workflow - I will end up optimising the workflow towards the end. I typically end up removing unnecessary tools, fields, and rethinking my logic.

Much of this optimisation, is also merging formula tools where possible. For instance, if I have 3 formulas - its much cleaner (and I would suspect faster) to have these all within one tool. For instance, a scaled down example:

to this:

This requires a lot of copy and paste - especially if the formulas/column names are long - this can be two copy and pastes, and waiting for tools to load between them, per formula (i do appreciate, this sounds an incredibly small problem to have, but on what I would consider a large workflow, a tool loading can actually take a couple of seconds - and this could burn some time. Additionally, there's always potential problems when it comes to copy/pasting or retyping with errors).

My proposed solution to this, is the ability to drag a formula onto another - very similar to dragging a tool onto a connection. This integration would look like:

Drag to the first formula:

Release:

Formula has been appended to the formula tool:

I think this will help people visually optimise their workflows!

Cheers,
TheOC

Please improve the Excel XLSX output options in the Output tool, or create a new Excel Output tool, 
or enhance the Render tool to include an Excel output option, with no focus on margins, paper size, or paper orientation

The problem with the current Basic Table and Render tools are they are geared towards reporting, with a focus on page size and margins.
Many of us use Excel as simply a general output method, with no consideration for fitting the output on a printed page.

The new tool or Render enhancement would handle different formats/different schemas without the need for a batch macro, and would include the options below.

The only current option to export different schemas to different Sheets in one Excel file, without regard to paper formatting, is to use a batch macro and include the CReW macro Wait a Second, to allow Excel to properly shut down before a new Sheet is created, to avoid file-write-contention issues.

Including the Wait a Second macro increased the completion time for one of my workflows by 50%, as shown in the screehshots below.

I have a Powershell script that includes many of the formatting options below, but it would be a great help if a native Output or Reporting tool included these options:

Allow options below for specific selected Sheet names, or for All Sheets

AllColumns_MaxWidth: Maximum width for ALL columns in the spreadsheet. Default value = 50. This value can be changed for specific columns by using option Column_SetWidth.

Column_SetWidth: Set selected columns to an exact width. For the selected columns, this value will override the value in AllColumns_MaxWidth.

Column_Centered: Set selected columns to have text centered horizontally.

Column_WrapText: Set selected columns to Wrap text.

AllCells_WrapText: Checkbox: wrap text in every cell in the entire worksheet. Default value = False.

AllRows_AutoFit: Checkbox: to set the height for every row to autofit. Default value False.

Header_Format: checkbox for Bold, specify header cells background color, Border size: 1pt, 2pt, 3pt, and border color, Enable_Data_Filter: checkbox

Header_freeze_top_row: checkbox, or specify A2:B2 to freeze panes

Sheet_overflow: checkbox: if the number of Sheet rows exceeds Excel limit, automatically create the next sheet with "(2)" appended

Column_format_Currency: Set selected columns to Currency: currency format, with comma separators, and negative numbers colored red.

Column_format_TwoDecimals: Set selected columns to Two decimals: two decimals, with comma separators, and negative numbers colored red.
Note: If the same field name is used in Column_Currency and Column_TwoDecimals, the field will be formatted with two decimals, and not formatted as currency.

Column_format_ShortDate: Set selected columns to Short Date: the Excel default for Short Date is "MM/DD/YYYY".

File_suggest_read_only: checkbox: Set flag to display this message when a user opens the Excel file: "The author would like you to open 'Analytic List.xlsx' as read-only unless you need to make changes. Open as read-only?
vb code: xlWB.ReadOnlyRecommended = True

File_name_include_date_time: checkboxes to add file name Prefix or Suffix with creation Date and/or Time

========

Examples:

My only current option: use a batch macro, plus a Wait a Second macro, to write different formats/schemas to multiple Sheets in one Excel file:

Using the Wait a Second macro, to allow Excel to shut down before writing a new Sheet, to avoid write-contention issues, results in a workflow that runs 50% longer:

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.

I surprisingly couldn't find this anywhere else as I know it's been discussed in person on many occasions.

Basically the Formula tool needs to be smarter in many ways, but this particular post focuses on the Data Type component.

The formula tool, should not always default to V_String as the data type when entering data or a formula into the formula tool, it should look at the data type and estimate the most likely option.

I know there are times where the logical type might not be consistent in all fields, but the Data Preview and the Function of the formula should be used to determine the most likely option.

E.G. If I type a number or a date directly into the formula tool, then Alteryx should be smart enough to change the data type from the standard V_String to Int, Double or date.

This is an extension to the ideas posted here:

https://community.alteryx.com/t5/Alteryx-Designer-Ideas/Tab-from-Select-Column-to-Enter-Expression-H...

https://community.alteryx.com/t5/Alteryx-Designer-Ideas/Formula-tool-data-type-should-be-prominent/i...

https://community.alteryx.com/t5/Alteryx-Designer-Ideas/Alteryx-11-formula-tool-default-data-type/id...

I love this tool,  but think it would be improved by including an option to create a column per delimiting character.  This could be added in the number of columns selector box.  In the case where 1 row has more delimiters than another, null columns can be created.  Without this option you have to Regex count the delimiters, select the max and then embed the Text to columns tools in a macro and then pass the max columns as a param.  Would be nice to resolve all this in the main tool.

Thanks, nick

Hello,

We use the pre-sql statement of the input to set some parameters of connections. Sadly, we cannot do that in a in-db workflow. This would be a total game-changing feature for us.

Best Regards,

Simon

I constantly find my using pre and post SQL Commands in the Output tool to run SQL when I don't actually have any data to output.

One example is when I load data into S3 and want to load it into Redshift. I have SQL code to run but no data to Output - I end up running a dummy row into a temp table.

So can we have an SQL tool that simply acts the same as a Pre-SQL command without the associated data output. Once the command is run we should be able to continue the workflow, so the tool should have an option input and output, like the Run Command tool.

From Wikipedia :

In a database, a view is the result set of a stored query on the data, which the database users can query just as they would in a persistent database collection object. This pre-established query command is kept in the database dictionary. Unlike ordinary base tables in a relational database, a view does not form part of the physical schema: as a result set, it is a virtual table computed or collated dynamically from data in the database when access to that view is requested. Changes applied to the data in a relevant underlying table are reflected in the data shown in subsequent invocations of the view. In some NoSQL databases, views are the only way to query data.

Views can provide advantages over tables:

    Views can represent a subset of the data contained in a table. Consequently, a view can limit the degree of exposure of the underlying tables to the outer world: a given user may have permission to query the view, while denied access to the rest of the base table.
    Views can join and simplify multiple tables into a single virtual table.
    Views can act as aggregated tables, where the database engine aggregates data (sum, average, etc.) and presents the calculated results as part of the data.
    Views can hide the complexity of data. For example, a view could appear as Sales2000 or Sales2001, transparently partitioning the actual underlying table.
    Views take very little space to store; the database contains only the definition of a view, not a copy of all the data that it presents.
    Depending on the SQL engine used, views can provide extra security.

I would like to create a view instead of a table.