community
cancel
Showing results for 
Search instead for 
Did you mean: 

Alteryx Designer Ideas

Share your Designer product ideas - we're listening!

1 Review

Our submission guidelines & status definitions before getting started

2 Search

The community for a solution or existing idea before posting

3 Vote

By clicking the like in the top left corner of an idea you support

4 Submit

A new idea to suggest a product enhancement or new feature


Suggest an idea

The following idea might not be as valuable as some of @SeanAdams posts, but it would save this user precious fractions of time.   When I leave the canvas with my mouse (point A) to go up to the pallet I select and drag the tool down to the canvas.  Sometimes I do right-click and go through the menus to add the next tool, but generally I go through that labor only when I'm inserting in-stream the tool.  So here is my idea:

 

Double-Click your NEXT tool and it "Alteryx-ly" appears on your canvas in proximity to the hi-lighted (last) tool.  Better yet, connect it!  Now I can move from the pallet to the configuration panel directly without having to move my mouse down to the canvas and then over to the configuration panel.

 

Hopefully, my friend @Hollingsworth will find this time-saving idea worthy of a star.  Speed demons like @NicoleJohnson and @BenMoss might not need this turbo boost, but at my age it is worth the ask.

 

Cheers,

 

Mark

My friend @jdunkerley79 posted a terse idea:  https://community.alteryx.com/t5/Alteryx-Designer-Ideas/FieldName-constant-in-Generate-Rows-Tools-an...  it is inactive, but I want to extend his thoughts.

 

Rephrasing his idea as mine:  The tool defaults the expressions to use [RowCount].  If you should either "Update Existing Field" or change the "Create New Field" the default expressions MUST be updated manually.  Please update the expressions to make use of the new field.

 

Well, that doesn't always work!  Often it will.  But if you change the TYPE to date, it certainly won't.  In fact, I see many questions about joining from within a DATE  RANGE and the technique to build date rows from the range requires the use of DateTimeAdd().  Wouldn't it be nice (like your sample workflows) to modify the default expression based on the change of data type?  I think so.

 

If we were thinking easy.  Suppose you could have a RANGE function (dates or numerics) where you simply selected the from, to fields and gave the user the option to select the units.  Now the tool auto-configures itself to create all of the "days" between the from and to dates or "1.0" and it creates all unit values between the two numeric amounts.

 

These would be "Alteryx" worthy enhancements in my opinion.

 

Cheers,

 

Mark

Hi Alteryx Designer Dev Team,

 

There are times where you want to create a variation of a particular pipeline and the data transformations in the beginning of the pipeline are similar but need slightly different configurations. To save time, can we have a right-click context option for each tool to be able to copy/paste or duplicate tool with existing configuration. This saves time by only having to change a few options in the duplicated tool. This is common for tools like, input, output, joins, groupings and reporting tools. An example where this functionality is handy in reporting: you may have a particular way that you always do your charts and instead of configuring the chart options from scratch each time, you copy paste the chart tool with current configuration and then you only have to make minor changes such as the data connections. 

 

Thank you

Hi to all,

 

I have seen one or two posts requesting ability to total up rows and/or columns of numbers, however this idea also requests the ability to subtotal data by a field and also produce an overall total.

 

This could be an extension to existing tools such as 'Summarise' and 'Cross Tab' or could be a stand alone tool.  Desired output of using a tool like this would produce something like this:

 

totals.JPG

 

This would be incredibly useful for building reports within Alteryx as well as analysing the data, and cut down the amount of tools currently required to produce this.  I have seen a third party tool which does some of this but this adds the ability to subtotal.

 

thanks - Roger

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

Hi Alteryx 🙂

 

When you set maximum records per file, the filename gets _# appended.  Great!  But in reality you get:

 

Filename.csv

Filename_1.csv

Filename_2.csv

 

The first filename doesn't get a number.  I think that it should.

 

Cheers,

 

Mark

Hi Alteryx 🙂

 

When I select fields within a BROWSE or Browse Anywhere, it would be nice to be able to highlight and deselect  a range of  fields instead of having to check/uncheck fields one at a time.  Yuck!  

 

Cheers,

 

Mark

The new Paste Before/After feature is awesome, as is the Cut & Connect Around.

 

https://community.alteryx.com/t5/Alteryx-Designer-Ideas/Paste-Before-After/idc-p/510292#M12071

 

What would be even better is to allow the combination of the two. E.G. It is not currently possible to copy or cut multiple tools and paste before/after, as this functionality only works for a single tool that's copied.

 

Thanks,

Joe

It seems like it is restricted to 255 characters using .hyper as an input (Alteryx designer discussion).  It would be great if we can read at least 2147483648 bytes which is the string limitation in Alteryx.

 

 

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

I see many posts where users want to view numeric or string data as monetary values. I think that it would be friendly to have a masking option (like excel) where you could choose a format or customize one for display.  The next step is to apply the formatting to the workflow so that folks who want to export the data can do so. 

cheers,

 

mark

My team uses a shared macro repository (say F:\AlteryxMacros), and we recently ran into an issue with the default save location for macros. While we save most macros to our repository, there are times when folks save their macros elsewhere (let's say C:\MyAwesomeWorkflow). The issue we've encountered is that if you go to file >> save as with a macro, it will ALWAYS default to the macro repository, even when my macro is currently saved elsewhere (C:\MyAwesomeWorkflow). Speaking for a friend, people have accidentally saved things to the macro repository by accident. Or, they waste time navigating from the macro repository to the their current folder.

 

If a macro is saved somewhere, please change the file >> save as to default to the current folder. Thanks! 

It would be useful to be able to select a single container (containing a data input) or multiple containers using Shift, and run those and only those.

 

When building a new element to a larger workflow, I often enter a new Input in a new container, the ability to run just that container without having to turn off all my other containers would be really useful in speeding up the start of joining things together.

 

Hope that makes sense.

 

Thanks,

 

Doug 

When writing a good amount of code, it is easy to get lost in a sea of parentheses.  Just when you think you're all done, you get an error that can force you to scour through your code to find the missing, extra, or misplaced parenthesis. 

 

A common feature today is to highlight a parenthesis when its partner is clicked on.  This instantly lets you know if you have the wrong number of them and where. 

 

I didn't think this was that important early on in Alteryx, at least for me.  Formulas were meant to be short and easily readable at a glance.  Now as I dig deeper, there's R, Python, SQL and other text-heavy inputs. 

 

I don't need a full-fledged text editor in Alteryx, but I would love some quality of life features like parentheses matching.

The Multi-Field formula tool has three really powerful features that it supports:

[_CurrentField_]

[_CurrentFieldName_]

[_CurrentFieldType_]

 

These are really powerful within Multi-Field formulas because they allow for a dynamic process to apply across multiple fields.

 

However, they would also be very helpful in regular formulas and Multi-Row formulas, for code transportability.

 

A basic example:  I have a Longitude field that is a string.  I need to set it to a value of 0 if there is a null value.

 

My formula today:

IF ISNULL([Longitude]) THEN 0 ELSE [Longitude] ENDIF

 

Now lets say I want to use the same formula somewhere else, but for Latitude instead.

 

 That formula looks like:

IF ISNULL([Latitude]) THEN 0 ELSE [Latitude] ENDIF

 

If I could use [_CurrentField_] instead, that would allow me to instead write both formulas as:

 

IF ISNULL([_CurrentField_]) THEN 0 ELSE [_CurrentField_] ENDIF

 

This code can easily be copied for any field that requires replacing Nulls with 0s, and doesn't require refactoring to use a Multi-Field formula instead.

 

This also means that if I later change my field name, the code will remain consistent.  This not only speeds up development time and flexibility, but more readily allows for validation that the existing code has not changed.

It would be extremely useful to quickly find which of my many workflows feed other workflows or reports.

 

A quick and easy way to do this would be to export the dependencies of a list of workflows in a spreadsheet format. That way users could create their own mapping by linking outputs of one workflow, to inputs of another.

 

Looking at the simple example below, the Customers workflow would feed the Market workflow.

 

WorkflowDependencyType
CustomersSQL Table 1Input
CustomersSQL Table 2Input
CustomersExcel File 1Input
CustomersExcel File 2Input
CustomersExcel File 3Output
MarketExcel File 3Input
MarketSQL Table 3Output

 

It would be CRAZY AWESOME if we could get a report like this for all scheduled workflows in the scheduler. 

With the 2019.3 release the summarize tool now includes prefixes for grouped fields. While a nice addition, in application it makes using this data downstream (like joining to other tables) more involved because of needing to remove this prefix. 

 

It would be nice to have this as an option (a checkbox to add/remove prefixes maybe) or just revert back to pre-2019.3 behavior...thanks!

My idea is to have the AlteryxEngineCMD.exe to run a workflow as part of the standard Alteryx license.

 

Use case - be able to run Alteryx from the command line without the need to buy the entire Scheduler package (at $6,500/seat).

 

I understand why certain features are add on, but the ability to run AlteryxEngineCMD.exe (I feel) should be part of  the standard license which is already $5K+. For those who only need to be able to run a command line execution of a workflow $6.5K is a lot of money!

  • Feature Request

The reporting tools do not currently support HTML structured or unstructured lists https://www.w3schools.com/tags/tag_ul.asp

All vertical combination creates tables which group the lines together.    Even if you manually create this - you get an error saying that ul (or ol or il) are not supported in composer

 

UL is not supported.png

 

This creates a challenge in 2 ways:

a) When creating lists in reporting outputs - you lose the functionality of structured lists (numbering with letters; numbers etc)

b) additionally - selecting the text in tables behaves differently than selecting data that is created in lists.

 

Please could you add the ability to create lists in addition to tables in the reporting tools by supporting the ol; ul; and il tags?

NOTE: this could initially be done just by supporting the tags; and then later this could be a summarize option on the summarize tool; and a bullet option in the text tool.

 

CombineOccursAsTBody.pngSummarize using tablesCombineAsList.pngdesired: summarise using listsList-RenderedVersion.pngList rendered with the list tags

 

 

 

 

 

The "Manage Data Connections" tool is fantastic to save credentials alongside the connection without having to worry when you save the workflow that you've embedded a password. 

 

Imagine if - there were a similar utility to handle credentials/environment variables. 

 

  • I could create an entry, give it a description, a username, and an encrypted password stored in my options, then refer to that for configurations/values throughout my workflows. 
    • Tableau credentials in the publish to tableau macro
    • Sharepoint Credentials in the sharepoint list connector
  • When my password changes I only have to change it in one place
  • If I handoff the workflow to another user I don't have to worry about scanning the xml to make sure I'm not passing them my password
  • When a user opens my workflow that doesn't have a corresponding entry in their credentials manager they would be prompted using my description to add it.
  • Entries could be exported and shared as well (with passwords scrubbed)

Example Entry Tableau:

Alias Tableau Prod
Description Tableau Production Server
UserID JPhillips
Password *********
+  

Then when configuring a tool you could put in something like [Tableau Prod].[Password] and it would read in the value.

 

Or maybe for Sharepoint:

 

Alias TeamSP
Description Team sharepoint location
UserID JPhillips
Password *********
URL  http://sharepoint.com/myteam
+  

 

Or perhaps for a team file location:

Alias TeamFiles
Description Root directory for team files
Path \\server.net\myteam\filesgohere
+  

 

Any of these values could be referenced in tool configurations, formulas, macro inputs by specifying the Alias and field.

1-3-2019 12-43-52 PM.png

Top Liked Authors