Community Spring Cleaning week is here! Join your fellow Maveryx in digging through your old posts and marking comments on them as solved. Learn more here!
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

Hi, I have searched through the community, and I wasn't able to find a duplicate for this idea. If in fact there is, I apologize and please point me to that post. I think that it would be a good idea to have date options in the summarize tool that would allow for grouping at higher levels of the date. I often have a date field that is specific to the day (i.e. 2018-01-01), and I just want to group by the year or month. Currently in order to do this, I have to create a formula before the summarize tool that formats the date according to how I want to group it, and then I am able to group off that field in the summarize tool. It would be nice if in the summarize tool, I could select the date field, and then have the option to group it at year, month, week, etc. 

When bringing data together it is often needed to assign a source to the data.  Generally this happens when you union data and need to know things later about the data for context.  It would save time to generate a source field that is assigned based upon the input connections of the union tool.  Perhaps when unioning data you can assign a name to each input stream?

 

 

 

Please extend the Workflow Dependencies functionality to include dependencies of used macros in the worflow too. Currenctly macros are simply marked as dependencies by themselves, but the underlying dependencies (e.g. data sources) of these macros are not included.

 

We have a large ETL process developed with Alteryx that applies several layers of custom and complex macros and several data sources referenced using aliases. Currently the process is deployed locally (non-server) and executed ad-hoc, but will be moved to the server platform at some point. 

 

Recently I had to prep an employee for running the process. This requires creating aliases and associated connections and making sure that access to needed network locations is in place (storing macros, temp files, etc.). Hence I needed to identify all aliases and components/macros used. As everything is wrapped nicely by a single workflow, I hoped that the workflow dependencies functionality would cover dependencies in the macro nodes within, but unfortunately it didn't and I had to look through the dependencies of 10-15 macros.

In other data programs like access or Toad you can put conditions on a join. You can choose if something is greater than, less than, left join, right join, etc.
But with Alteryx you are only allowed to join a perfect match. It would be really great if you could add that functionality into 9.0
Hi,

Instead of having multiple filters to create mutliples new branches for downstream analysis, Alteryx should have one filter with multiples ouputs ports. Each filter would is own statement. 

This would reduce the numbers of filters in a canvas.

Currently if I enter a long text using the Text Input Tool (for example when posting data using XML) it's impossible to see what's in the entire field since the horizontal scrolling immediately jumps to the next field instead of smoothly scrolling the (long) first field. I have to edit the data in Notepad and then paste back into Alteryx to fix.

Alteryx Designer x64 - RFM_pushSF.yxmd.jpg

This idea is concerned with suggesting values based on text box entry in an analytic app. This would be an autocomplete within the text box interface based on matches to a list of connected values. For example, if someone was posting "805 Wells Road" it would expand the text box window and supply potential matches to click on.

 

Quick and dirty photoshop image below:

 

autocompleteaddress.png

It would be great if you could select multiple Data Fields in a single Crosstab

For example. I would like to SUM (Methodology) Pet Food Sales (Data Field 1) & Baby Food Sales (Data Field 2) By Store (Grouping Field) By Day of Week (Header field).
 

I have reviewed a number of batch macros that work well for mirroring the "NetworkingDays" excel calculation but it would be great to add an interval type for "weekdays" to the DateTimeDiff formula ie

 

 DateTimeDiff ( [Date01],[Date02], "WorkDays")  where any Saturday or Sunday between the dates would be discounted.

In the ‘Report – Table’ tool I would like to be able to force headings to multiple lines. For example If I have a heading such as “Catchment (%)” or “Spend (£)”, I would like there to be an easy way to make the (%) / (£) move to the second line when I have fixed width columns.
 

 

As the subject header says, I would like the Data Cleansing tool to incorporate a way for the user to explicitly specify characters that should be removed.

A very common task that should exist in this tool, removing the need for writing formulas and cluttering the workflow with additional tools.

 

 

I think that it would be useful to add two new Rename Modes to the Dynamic Rename tool -- here are the existing ones:


I would add:
Take Field Metadata from Right Input Metadata
Take Field Metadata from Right Input Rows

These would allow mass changes in data type, size and scale based on either an existing data table's metadata or an external metadata table.

I have an app that contains 4 check boxes.  Each check box is independent, and when checked, two other prompts open up to the user (in this case, text boxes which are also independent of the other check boxes).

I would like to be able to "Check All", so that with one click, ALL four check boxes are checked, and their prompts all open up.

I would like to be able to pause a module A, run module B then restart A at a later time.   

You can select all fields at once, but it'd be nice to select a chunk of fields using CTL+Shift+Click

For an email event, there are several defaults that are shown in the body (e.g., %User%, %ComputerName%, %WorkingDir%).

It would be nice to add a date in there, maybe %Date% or %DateTime% or something like that which would display the computer system time.
Hello,

It would be great if there was an option to compute 'median' on numerical data column in 'cross-tab' tool. We trust 'median' a lot more than 'average' in many different computations.
I would stretch my suggestion far enough to propose adding quantile computations as well...

Thanks!

It would be good to be able to constrain the size of an image in the vertical direction as well as the horizontal.  I am currently working on a report that has an image in the middle of a page of text.  If the user inputs an image that is not the same size as my test image, it can push text onto the next page which ruins the report.  Having the image next to the text and constraining horizontally is not an option with this project.

It would be nice if we could change the tool numbers and effect which one gets done first. If I'm working on a module and I later add some more analysis upstream it won't get done or pulled first since it has a greater number. a simply ability to change the numbers would really make things a lot easier and it will allow the flow of work to flow smoothly visually
Whenever Alteryx recognizes a field as a Date, it should default to Date, not Date/Time. I don't think I'm in the minority, but I rarely need to see the date AND the time. 99.9% of all of my date fields do not have a time associate with them; such as: Open Date, Close Date, Remodel Date, Lease Expiration Date, Lease Start Date, Date Record Updated, Relocation Date, etc., etc., etc. So I always get results like 4/1/2013 12:00:00, which makes it difficult to query against without changing to just Date. I would venture to guess that most people don't use the time either, but I may be wrong. So, defaulting to just Date would save a lot of us that extra step for each date column.
Top Liked Authors