Get Inspire insights from former attendees in our AMA discussion thread on Inspire Buzz. ACEs and other community members are on call all week to answer!
The Product Idea boards have gotten an update to better integrate them within our Product team's idea cycle! However this update does have a few unique behaviors, if you have any questions about them check out our FAQ.

Alteryx Designer Desktop Ideas

Share your Designer Desktop product ideas - we're listening!
Submitting an Idea?

Be sure to review our Idea Submission Guidelines for more information!

Submission Guidelines

Featured Ideas

Currently only DateTime based functions are available, Time based functions should be introduced. like TimeAdd(), TimeDiff() etc.

This will help users a lot to calculate different aspects of time based calculations...

 

Ashok Bhatt

Using Render tool to create an excel document. 

(This is for a specific use case)

 

If you are using the RENDER tool to create one or more EXCEL documents.  Ensure that you are NOT explicitly stating the Sheet name in the file name.  (Output file or 'Replacing entire Path with Group).

 

If you explicitly name the sheet, it will throw an inboundPipe error.  

Remove the sheet name, and it should work fine. 

 

 

It would be nice to have an option for annotations to be hidden and then show when the tool is selected or hovered over. Long annotations are distracting in normal use but may be necessary to inform new users. Currently, our only option is to always hide or always show them. Having an option to allow annotations to be hidden and then appear when a tool is hovered over, or selected, would allow for a more sleek canvas and not deter users from writing long annotations. This is similar to how comments in excel work. Having a canvas wide setting and then an override option on a tool by tool basis would be ideal. 

Hello,

 

as shown in the Alteryx Inspire Demo, Assisted modeling is going to work with a wizard and generate several tools as result.

The data evaluation functions and feature engineering assist however would be extremely useful tools in their own, is there any chance we can use them as separate tools in the upcoming version?

 

Thanks in advance!

This minor but also easy.  It would be nice to have four way control to adjust the size of four open windows.  Instead of adjusting two and then adjusting the other two.  When hovering over the four corners of where the window come together - when they are lined up - then the cursor would change to a four way arrow and allow adjustment of all four windows in four directions.

 

 

 

 

You have a slide within a slide and if your window is not big enough you don't even see both slides.  Makes absolutely no sense and is super annoying.

 

join double slide.JPG

Can you please add a setting to the Dynamic Input tool where the developer can choose to treat different schemas as either Errors, Conv Errors or a Warning?

 

Depending on which of these issues are flagged during a workflow run my management of it differs. I tend to ignore warnings, yet pay attention to Errors and Conv Errors.

It would be very helpful if there was a master variable list for the entire workflow, with one column of that list being the first tool number where the variable appeared.  For example, when using JOIN with many fields, it is pretty easy to get duplicate fields.  It is also common to have fields that are only slightly different, for example, "Variable_1" and "Variable 1."  If there was a master list of variables with hotlinks to the first tool where a variable appeared, it would be easy to fix duplicate or near-duplicate variables.  Other useful fields for a variable summary would include the variable type (integer, double, etc.), whether the field has any nulls, and whether the field has any text.  

I use macros all the time, and I would love if the metadata could persist between runs no matter what tools exist in the macro. I've attached a simple example which should demonstrate the issue. After running the module once, the select tool (4) is populated with the expected data; however, as soon as anything changes (like a tool is dropped onto the canvas), the select tool (4) is no longer receiving the metadata to properly be populated. I've added the crosstab tool from the macro onto my workflow to demonstrate that it's only a problem when the tool is inside a macro. It makes it difficult at times to work with workflows that utilize macros due to the metadata constantly disappearing anytime a change is made. The solution would be for the metadata from the last run to persist until the next run. This is how the crosstab tool is working on my workflow, but putting it inside the macro changes its behavior.

Add a new feature to develop your own customized decision tree with Insight. So instead of using a tree generated with the Decision Tree tool a user can generate a tree with custom splits and save  the splitting rules as a model to score later a new dataset. This will provide user the ability to enhace a tree with business knowledge.

The add to / remove from container behavior needs to be modified.  I have frequently had the application completely rearrange my workflow because of it. I was just deleting a handful of closed containers when the application removed all my tools from their individual containers and wrapped everything in one big container completely screwing up my entire workflow.  This happens a lot.  Now I have to reorganize the workflow.  This is one of my biggest frustrations with the application.containers.png

I appreciate being able to write to an ESRI File GeoDatabase. It would be even better if in the process of writing to an ESRI File GeoDatabase I could identify fields to index and have them indexed when writing to the File GeoDatabse. Currently I have to add the index in ArcGIS after the fact. Writing to an ESRI File GeoDatabase currently adds a spatial index automatically, but I'm talking about an attribute index here.

Hello gurus - 

 

Pretty much every coding framework supports this.  If we really want Alteryx to embrace no-code, we've got to have some ability to control commit / rollbacks across transactions.  As it stands currently, it is pretty easy to write out parent records, fail to be able to write out children, and wind up with a database state that makes the end users very sad.  

 

Thanks!

 

brian

At the moment, we are not able to use input data field names and its values in Output tool, mainly in the Pre-SQL and Post-SQL statement. I see some discussions on this in the community and in many scenarios we require that. It will be great if we have this option.

We are attempting to connect to a Sybase DB. The version we're trying to connect to is 15.7.0. It seems Alteryx only officially supports 15.0.2 connection. 

 

Will there be an update coming in a future release so that we can connect directly and not have to use DB extracts? 

 

 

 

Please add measures of statistical central tendency to the Summarize tool, such as:

Mid-range

Midhinge

Quartile

Thank you.

The Record ID tool can take a custom starting value other than the default of 1. I sometimes have a case in which I want the starting value to begin with 1 + the max of another field. I can either do this with a macro or with Append and Formula tools. This is just one example. If I have the ability to use an expression as the Starting Value, then I can do the 1 + max or something else cool and useful.

It would be nice if we could cancel out of the interactive chart tool without saving the changes we made. It would make it easier than trying to recall how we had it before it was opened, especially when you're making small tweaks to formats & dimensions of things to make them look a little different.

 

The macros included in the CReW macro pack are excellent. However, having to install them each time and hope that your users have the macros installed can be a pain. 

Suggest adding them as default tools in the next version of alteryx.

I have not found this function or a workaround, only as "recent connections" which normally, are not saved on Virtual Machines.

This would save the time it takes to find the path/folder where Calgary DBs are saved.

 

if this has been proposed or fixed already, please delete this idea! 

Top Liked Authors