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 star 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

I love Workflow Meta info, especially the ability to put the Author, the search tags,the version, the description, etc...

workflow meta info.png

But why can't we use it as Engine Constant? It doesn't seem very hard to implement and it would change life for development.

 

engine_constant.png

When we industrialize our workflows, we often use a parameter file with a command like :

 

 

AlteryxEngineCmd.exe MyAnalyticApp.yxwz AppValues.xml

 

 

I would like to have the parameter file path with its extension as an engine constant, like we have the workflow name.

A lot of popular machine learning systems use a computer's GPU to speed up some of the math to a huge degree. The header on this article on Medium shows a 15x difference from a high-end CPU vs a high-end GPU. It could also create an improvement in the spatial tools. Perhaps Alteryx should add this functionality in order to speed up these tools, which I can imagine are currently some of the slowest.

Idea:

I know cache-related ideas have already been posted (cache macros; cache tools), but I would like it if cache were simply built into every tool, similar to the way it is on the Input Tool.

 

Reasoning:

During workflow development, I'll run the workflow repeatedly, and especially if there is sizeable data or an R tool involved, it can get really time consuming.

 

Implementation ideas:

I can see where managing cache could be tricky: in a large workflow processing a lot of data, nobody would want to maintain dozens of copies of that data.  But there may be ways of just monitoring changes to the workflow in order to know if something needs to be rebuilt or not: e.g. suppose I cache a Predictive Tool, and then make no changes to any tool preceeding it in the workflow... the next time I run, the engine should be able to look at "cache flags" and/or "modified tool flags" to determine where it should start: basically start at the "furthest along cache" that has no "modified tools" preceeding it.

 

 

Anyway, just a thought.

 

Hi!

 

It would be cool if the Overlap tool also worked with report layouts, instead of just the map image. For example, once I've pieced my different report tables into one layout, it would be cool if I could just add my company logo using image tool, add a Overlay tool, and add the logo to the top corner of my finalized report. I realized there are other ways of doing it, this would seem the most straight forward though. Just an idea.

 

If progress bar or overall process completion percentage can be displayed somewhere, adds great value for the users running complex processes (with multiple databases/ files as input and complex queries especially spatial queries).

 

 

Please evaluate the option to add 2 new containers:

1. parallel - execute tasks inside in parallel
2. serial - execute tasks in strict  order, imposed at design time. In the future the oder of operations could be enforced by parameters or other input conditions at runtime.

 

Please Give us the capacity to mix and match these 2 containers.

Thank you

 

Regards,
Cristian.

I just noticed in a workflow I'm looking at, that I derived a column but after a bit of developing, forgot about it, so there it sat, unused.  It doesn't hurt anything, but it would be useful if that sort of thing would automatically generate a soft warning on the tool in question: e.g. any item not referenced downstream automatically generates an "Unused variable" warning.

 

The excel driver (.xlsx) converts these values to 0.  If you use the legacy excel driver (.xlsx) it brings in the #N/A values.  This issue was reported in the community and I am forwarding it to the New Idea as a problem that needs to be addressed on behalf of @JohnDoe.

In case of system crash/ upgrade, transfer of Alteryx license from one system to another system or from one user to another. User should be able to surrender/ borrow/ transfer license from one machine to another. This helps for more flexible use of product.

 

  • Engine
0 Stars

Please test/certify Teradata 16.2 for designer, server, scheduler, and Gallery applications.  

0 Stars

As per this discussion, I'd like to create constants that stay with me as I create new workflows rather than creating a user constant across multiple workflows.

 

This could perhaps be done by editing an xml file in the bin.

0 Stars

It'd be nice to have Engine Constants that follow us across all workflows. Having an XML file in the bin that we can update could be a way of doing this. 

0 Stars

Hi,

 

Noticed an issue in the Browse tools, specifically if you’ve run a module once, where browse tools are displaying information, and then you add new browse tools into the process (without clicking run yet). What I’m seeing is if I’m looking at the “existing” Browse that is showing data, and then click directly onto a Browse tool that was added after the run (not remembering I just added it), the “new” Browse tool is showing the previous Browse tools info, I literally have to click on the canvas, and then back to the new Browse tool for Alteryx to recognized there isn’t any data to display in it yet. My point being it can be misleading to the user if they don’t recognize the wrong info is being displayed (because as you click back & forth between the two, the data stays the same, making the user think the issue is in the process rather than just the display, can waste a lot of time backtracking for no reason). I’ve seen this behavior over at least the past 3 engine updates, just FYI.

0 Stars

For most of our "Production" mode, we launch our apps with an xml file containing the parameter send to the app.

We would like to have the path of this file in the Engine Constant.

0 Stars

Idea:

I know cache-related ideas have already been posted (cache macros; cache tools), but I would like it if cache were simply built into every tool, similar to the way it is on the Input Tool.

 

Reasoning:

During workflow development development, I'll run a workflow repeatedly, and especially if there is sizeable data or an R tool involved, in can get really time consuming.

 

Implementation ideas:

I can see where managing cache could be tricky: in a large workflow processing a lot of data, nobody would want to maintain dozens of copies of that data.  But there may be ways of just monitoring changes to the workflow in order to know if something needs to be rebuilt or not: e.g. suppose I cache a Predictive Tool, and then make no changes to any tool preceeding it in the workflow... the next time I run, the engine should be able to look at "cache flags" and/or "modified flags" to determine where it should start: basically start at the "furthest along cache" that has no changes preceeding it.

 

Anyway, just a thought.

 

 

Top Starred Authors