Alteryx Designer Desktop Ideas

I would like to suggest to contemplate the option to add a new SDK based on lua language.

Why Lua?

o is open source / MIT license

o is portable

o is fast

o is powerful and simple

o Lua has been used to extend programs written in C, C++, Java, C#, Smalltalk, Fortran, Ada, Erlang

We are experiencing performance issues with fetching schema/table/columns info on Alteryx Designer when using Vertica DB.

From the troubleshoot with Alteryx support, the query hitting "odbc_columns" is contributing to the performance issue. Vertica DBA suggests to use "columns" instead of "odbc_columns". Submitting this request to change the query.

Refer to case 00551930 for more info.

Hi - 

We are using the new(ish) Anaplan connector tools; in particular, the "Anaplan Output" tool (send data TO Anaplan).

The issue that I'm having is that the Anaplan Output Tool only accepts a CSV file.  This means that I must run one workflow to create the CSV file, then another workflow to read the CSV file and feed the Anaplan Output Tool.

If it were possible to have an output anchor on the Output tool that would simply pass the CSV records through to the Anaplan Output tool, the workflows would be drastically simplified.

Thanks,

Mark Chappell

Alteryx really needs to show a results window for the InDB processes.  It is like we are creating blindly without it.  Work arounds are too much of a hassle.

Current:

Currently in Result window we have datacleanse, fileter and sort functionality which makes life easier.

We dont have column Rename and Data type change functionality. In order to do that we need to drag a tool for the same for Rename of column.

Expectaion:

Result Tool should be capable enough to Rename column and Data type.

It will save a lot of time ,

The "Field Summary" tool and several others have a configuration requirement that provides a list of fields to select or deselect.  The selection action is singular meaning you can only effect the action on one item in the list of many.  As the number of fields we work with grows significantly this becomes a time consuming and tedious task.

This should be enhanced to allow highlighting of multiple fields to select or deselect as we can do in tools like the "Select" tool.

The field summary tool is an excellent resource to get an overview of the data and spot targets for analysis or data cleansing. 

Unfortunately it has limitations either in the number of fields included or some combination of the number of fields and one or more of its attributes.   There is nothing in the documentation I found to make a user aware of this. When you exceed N  fields selected the system just hangs, indicating it is running but there is no connection progress shown and nothing seems to happen, even if you limit input to 1 record.

Through trial and error I found an approximate limit in number of fields I can include and still have it work.

I request that Alteryx update the tool help info and devise enhancements to dynamically load balance the tool so it can scale to the number of fields requested or at least warn when the limit is reached or approached.  The latter warning could be similar to the red font warnings in the formula tool when you have a malformed expression.  However a load balancing version is most desired.

The issue as it stands results in users wasting a lot of time trying to make the tool work as expected, then report it to support as an apparent bug in the tool which can be argued both ways.

I realize in the real world there are limits but in this real world we are seeing the number of fields to analyze increase significantly, especially when you have a data license and integrate 3rd party data to you own native data adding a hundred or hundreds more fields.

By default output always print Headers as shown in item 1 below, I am looking to print item 2 as Header.  Item 3 is my output.

I tried item 4 below, doesn’t work.

Please consider this in your future releases.  It saves lot of time as the Outputs can contain hundreds of fields and output files are shared with User community who understands the Field description much more than Field name.  For example SAP Field-KUNNR does not mean nothing to a User than its description 'Customer'.

A check box on the Output Tool should able to toggle the selection between Field or its Description.

You might argue that the Rename column can be used, agree it would be difficult to manually type in hundreds of fields.  As an alternative you can provide automatic Rename population with Description.

Hi 

Sometimes when your using a filter you want to let everything pass through. Which means you have to remove the filter or go around it.

In stead of beeing able to out comment your filter. And the filter tool see's that as no filter.

How about adding the ability to split intersecting trade areas at the points of intersection to create two new spatial objects.  The two objects could then be used to process customer records and divide them into "territories" based on  the line of intersection.

https://community.alteryx.com/t5/Alteryx-Designer-Discussions/BigQuery-Input-Error/td-p/440641

The BigQuery Input Tool utilizes the TableData.List JSON API method to pull data from Google Big Query. Per Google here:

• You cannot use the TableDataList JSON API method to retrieve data from a view. For more information, see Tabledata: list.

This is not a current supported functionality of the tool. You can post this on our product ideas page to see if it can be implemented in future product. For now, I would recommend pulling the data from the original table itself in BigQuery. 

I need to be able query tables and views.  Not sure I know how to use tableDataList JSON API.

The look of the canvas is important. Being able to toggle between viewing classic icons (as seen throughout this video: https://www.youtube.com/watch?v=DJwgYYP_xlA), to the extent available, and current icons would provide users with more variety. As a secondary benefit (when toggled to show the classic icons), users would be able to differentiate between the tools that are not classic (i.e., the newer tools that don't have an older design) and the classic tools.

Thank you very much.

Hi Alteryx,

I tried importing a file into my text input tool and I ran across this error.

Why is there a limit? Can we get rid of it since we're not living in DOS anymore.

Hi,

The imputation tool allows exchange of numbers. It would be great if we are given the option to impute string values and NULL value too

I am trying to use the Dynamic Replace to selectively update records in a set of variables from survey data. That is, I do not have all potential values in the “R” input of Dynamic Replace. Instead, I have a list of values that I would like altered from their current values by respondent (RespondentID) and question # (Q#).  Currently, when I run the workflow, any Q#/ResponseID combos that are not in my “R” input are replaced with blanks. However, I would like an option that maintains the original data if there is nothing to replace the data with. Without this option, there are few (I'm still working on some ways) workarounds to ensure the integrity of the data.

Matt

Recently, I posted one problem regarding on merging a column with same value using  the table tool. I do have a hard time to make a solution until @HenrietteH helped on how to do it. What she showed was helped me a lot to do what I want in my module, however it would be more easier if we are going to add this feature on the table tool itself. 

Thank you

A user may need to perform regression test on their workflows when there is a version upgrade of Alteryx. To save users time and effort, users can be encouraged to submit a few workflows in a secure area of the Alteryx Gallery. Prior to a version release, the Alteryx product testing team can perform a regression test of these workflows using automation. Thus when users receive an upgraded version of Aleryx it is more robust and with the added assurance that the workflows they had submitted will continue to work without errors.  

The Input Data and Text Input Tools are visually distinct, so it's easy to see when a workflow is inputting live (File) or static (Text) data.

The Macro Input tool has the same appearance whether it's inputting a File or Text data, so you have to open the tool configuration to see whether it's inputting live (File) or static (Text) data. It would be great if there was a way to visually distinguish these two cases, perhaps even separating the macro tool into two tools, one for Files and one for Text.

The current Export Workflow user experience is extremely frustrating and it sometimes takes me several attempts to export the workflow with all of the correct assets. Some ideas for improving the UX:

• Allow the width of the window to be expanded or maximized. I often have many assets that start with the same folder structure name and I have to scroll to the right for each one to decide whether to check or uncheck it. 

•  Have a display option for "Group asset by Type" (e.g., Input, Output, Macro). I typically only package up my workflows with the embedded macros, not the Inputs or Outputs. (This is especially important during development and testing, when interim yxdb's are saved to facilitate QC and trouble-shooting.) I would like an easy way to "Check all Macros" without having to go through the list one-by-one. I may have over 100 assets; with the current UX, it's really hard to get all the right assets checked.

• Add an option to filter the display to see only the assets that have been checked. 
• Add a way to copy the asset list (checked and/or unchecked) to the clipboard. This would allow us to confirm that all of the assets needed are included BEFORE EXPORTING. 
• Add an option Select All or Deselect All