Alteryx Designer Ideas

Hi 

Wanted to control the order of execution of objects in Alteryx WF but right now we have ONLY block until done which is not right choice for so many cases 

Can we have a container (say Sequence Container) and put piece of logic in each container and have control by connecting each container?
Hope this way we can control the execution order
It may be something looks like below 

This is a pretty quick suggestion:

I think that there are a lot of formulas that would be easier to write and maintain if a SQL-style BETWEEN operator was available.

Essentially, you could turn this:

ToNumber([Postal Code]) > 1000 AND ToNumber([Postal Code]) < 2500

Into this:

ToNumber([Postal Code]) BETWEEN 1000 AND 2500

That way, if you later had to modify the ToNumber([Postal Code]), you only have to maintain it once.  Its both aesthetically pleasing and more maintainable!

Right now we can create Tableau extract files (.tde), but cannot read them into Alteryx -- this limits the partnership of these two companies.
Please add the functionality to import .tde files,
Best,
Jeremy

I've seen this question before and have run into it myself.  I'd like to see a new tool that would allow a developer (of a workflow) to choose a path of logic based upon criteria known only during the execution of a module.

If LEFT INPUT Count of records < 10,000 THEN Path1 (e.g. use a calgary join)

ELSE Path 2 (e.g. use a standard join)

endif

Thanks,

Mark

I'd like to see Alteryx allow a second install of your license on a second, personal machine.  Tableau allows this and IMO is why there is such a robust online / blog community around that product.

For those of us that work at mid-size to large organizations, there are often strict rules governing internal data and use of cloud-based data sources.  If I discover some new trick I'd like the share with my fellow Alteryx analysts outside of my company, I have no clear way to do that the same way I can with Tableau where I can do it at home not using my company's data.

Being able to learn new features and test things out on commonly available public data (ever notice that Superstore data set everyone who gets Tableau has?) would accelerate what we're able to do with the community site here and the larger analytics blogging community.

in our organization people are moving away from network drives to BOX for file repository and they needs to use to connect to BOX using Alteryx as an Input and Output platform where they should be able to access files to read and write. 

Currently few of the users are able to use the BOX as a repository using BOX Sync tool (Map BOX as a network drive) but that is not at all useful when they try to save into a gallery and run or schedule on the gallery. A connector for BOX will be of great help. 

Ever tried to copy a field rename from one select tool to another, or from one summarize tool from another.

Have you noticed that it doesn't work?

I think it should. 🙂

i.e., if you click on the rename box ("Total") and enter ctrl-c, when you enter ctrl-v in the other tool, it pastes this:

Field2 Sum Total

not just the name "Total"

Instead of just the renamed field "Category", the select tool pastes this:

True Field1 String 1 Category

I think I'm liking the new UI, but I think it's necessary to bring back save, undo and re-do buttons....

1. Frequent saving of workflows is crucial and not everyone uses keyboard shortcuts

2. The ability to undo (lots) of changes is a key part of iterating and rapidly building workflows in Alteryx and again not everyone uses keyboard shortcuts to do this.

Looks like there's potentially space to add this to the right of 'help' (I suspect this might be technically quiet difficult) or to the left of 'run', 'schedule' and 'active documents' as seen in the image below.

Out of interest, where has the 'documents' terminology come from?

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.

It would be nice if we can arrange some tools on the canvas neatly by one click and having them distributed evenly (horizontally/vertically).

See this picture which worth thousand words.

Can you put a check box on the container title bar to make it easier to enable/disable containers in the process window? And can you make the minimize/maximize option for a conatiner a separate option from enable/disable?

At the moment containers either expand and overlap other tools, or you have to leave space for them (defeating the original purpose of using them). Is there a way we can have the containers expansion shift the workflow so the others tools shift down / right to account for this expanision?

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:

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:

Or perhaps for a team file location:

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

The SQL Editor window could have a better presentation of the SQL code; two issues observed

• First, that it's simply plain text without even a fixed-width font, much less syntax highlighting
• Second, if you type in some manually formatted SQL code (e.g. with line feeds and indentation), then click on the "Visual Query Builder" button, then click back to the "SQL Editor" button, all the formatting is lost as it is converted to one run-on line of code, which is very difficult to read.

I understand that going between the Visual Query Builder and the SQL Editor is bound to have some issues; nonetheless the "idea" is to allow a user friendly display in the SQL Editor window:

• Use a fixed width font, (should be trivial to implement)
• SQL formatter, implementation ideas can be found here: https://github.com/TaoK/PoorMansTSqlFormatter
• SQL syntax highlighting, implementation ideas can be found here: https://github.com/jdorn/sql-formatter

My "implementation ideas" are based on a couple minutes with google, so hopefully this is a very feasible request; my user base is very likely to spend more time in the SQL editor than not, so this would be a valuable UX addition.  Thanks!

I'm not sure if this will ever be possible, but I know that it would greatly benefit me and I'm sure thousands of other users. In my work place I am constantly working in a conference room and at my desk. At my desk I am wired into an Ethernet connection while in the conference room I am wireless. When I start my workflows after working with my team in the conference room, I can't go back to my desk until the workflow is finished running because I am changing internet connections and I lose connection to the databases. With the pause button it would become possible to run a workflow and then change my internet without losing connection to the databases.

Another use for this would be while testing a workflow with a new tool. There are times I run a workflow that can take a few hours, but then I realize there is a mistake somewhere in my workflow, where the data hasn't reached yet. I think it would be very helpful to be able to pause the workflow and add the new tool in, while seeing results from tools it has already passed through.

But yet again this is just an idea that relates to me, I wonder what the rest of the community thinks.

Idea: Prompt the user to find a missing macro instead of the current UX of a question mark icon.

Issue: When a macro referenced in a workflow is missing, then there is no way to a) know what the name of the macro was (assuming you were lazy like me and didn't document with a comment) and b) find the macro so you can get back to business.

When this happens to me know, I have to go to the XML view and search for macros and then cycle through them until I find the one that's missing. Then I have to either copy the macro back into that location or manually edit the workflow XML. Not cool man.

Solution: When a macro is missing, the image below at the right should be shown. In the properties window, a file browse tool should allow the user to find the macro.

Tools within a workflow needs to be able to run in parallel whereever applicable.

For example: Extracting 10 million rows from one source, 12 million rows from a different source to perform blending.

currently the order of execution is the order in which tools are dragged into the canvas. Hence Source1 first, Source2 second and then the JOIN.

Here Source1 & Source2 are completely independent, hence can be run in parallel. Thus saving the workflow execution time.

Execution time is quite crucial when you have tight data loading window.

Hopefully alteryx considers this in the next release!

Many files I use are in .xlsb format.