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

We need color coding in the SQL Editor Window for input tools.  We are always having to pull our code out of there and copy it into a Teradata window so it is easier to ready/trouble shoot.  This would save us some time and some hassle and would improve the Alteryx user experience. ( I think you've used a couple of my ideas already. This one is a good one too. )

2018-10-18_7-49-16.jpg2018-10-18_7-50-52.jpg

 

@AdamR did a talk this year at Inspire EU about testing Alteryx Canvasses - and it seems that there is a lot we can do here to improve the product:

https://www.youtube.com/watch?v=7eN7_XQByPQ&t=1706s

 

One of the biggest and most impactful changes would be support for detailed unit testing for a canvas - this could work much like it does in Visual Studio:

 

Proposal:

In order to fully test a workflow - you need 3 things:

  • Ability to replace the inputs with test data
  • Ability to inspect any exceptions or errors thrown by the canvas
  • Ability to compare the results to expectation

To do this:

  • Create a second tab behind a canvas which is a Testing view of the canvas which allows you to define tests.   Each test contains values for one or more of the inputs; expected exceptions / errors; and expected outputs
  • Alteryx then needs to run each of these tests one by 1 - and for each test:
    • Replace the data inputs with the defined test input.   
    • Check for, and trap errors generated by Alteryx
    • Compare the output
    • Generate a test score (pass or fail against each test case)

This would allow:

  • Each workflow / canvas to carry its own test cases
  • Automated regression testing overnight for every tool and canvas

 

 

Example:

 

Testing.jpg

 

For this canvas - there are 2 inputs; and one output.

Each test case would define:

  • Test rows to push into input 1
  • Test rows to push into input 2
  • any errors we're expecting
  • The expected output of the browse tool

 

 

This would make Alteryx SUPER robust and allow people to really test every canvas in an incredibly tight way!

It may be user-friendly to display the DSN description. It's usually stored in the windows registry under "description" :

 

descirption_dsn.png

 

This should display in the log and when you configure a connexion.

It may be user-friendly to display the DSN description. It's usually stored in the windows registry under "description" :

 

descirption_dsn.png

 

This should display in the log and when you configure a connexion.

There is a great question in the Designer space right now asking about saving logs to a database: https://community.alteryx.com/t5/Alteryx-Designer-Discussions/Save-workflow-messages-log-in-database...

 

This got me to think a little more about localized logging options in Alteryx.

 

At a high level, there are ways to accomplish this in Designer at a User or System level by enabling a Logging directory and then parsing those logs with a separate Alteryx job.  However, this would involve logging ALL Designer executions, which seems like it may be overkill for this need.  A user can also manually save a log after each execution, although this requires manual intervention.

 

I think adding an option in the Runtime settings for Workflow Configuration to Enable Logging and (optionally) specify a Logging directory would be a great feature add for Designer.  In my opinion this should not apply once a workflow runs on Server (Server logging should be handled in a fully standardized way), but should apply to designer "UI" execution.  Having the ability to add a logging naming convention (perhaps including a workflow name and run date in the log name) would be icing on the cake.

 

This would allow for a piecemeal logging solution to log specific flows or processes that might be high visiblity or high importance, while avoiding saving hundreds or thousands of logs daily of less important processes, and of dev test.  It would also reduce or eliminate a manual process to save these logs individually.

Not sure if this has been submitted... or if this option is already in a newer version.

There should be an option, after correcting an issue/error within a workflow for users to start again at the error point instead of running the entire workflow again.

This option will help users to streamline the process of building workflows and avoid wasted time spent waiting for large complex workflows to complete or error out.    

Hi, i am from ETL back ground and coming from my knowledge i would like to suggest or ask a feature which will helpful in alteryx solution.

 

"Error Line" : many ETL tools provide an "On Error" line which performs certain actions like "altering user by sending an email", "ignoring and going to next step" etc. It will be great if Alteryx can provide the same feature where we can have an error line (red line) for each tool.

 

Hope this is not a repeated idea. thank you for all the support and providing a wonderful tool.

 

Thanks,

Harika K

Not sure if this has been submitted... or if this option is already in a newer version.

There should be an option, after correcting an issue/error within a workflow for users to start again at the error point instead of running the entire workflow again.

This option will help users to streamline the process of building workflows and avoid wasted time spent waiting for large complex workflows to complete or error out.    

Alteryx Designer should automatically save my modules on a regular basis so that if I have a failure of some sort, my hard work will not be lost.
  • Troubleshooting
Alteryx Designer should automatically save my modules on a regular basis so that if I have a failure of some sort, my hard work will not be lost.
  • Troubleshooting
It would be nice to have the annotations that a user gives a tool with a different background color on the canvas than those tools where the annotation is being automatically populated.  Example would be the user gives a tool a specific name that shows up in blue but the formula tools that display the formula preview under the tool show up in yellow.
  • Troubleshooting
I have several modules that need to run in sequence.   Can a ksh or some other program be used to string the modules together?  

So that if I have Step1.yxmd, Step2.yxmd and Step3.yxmd.  2 is dependent on 1, 3 is dependent on 2.  I want to tell it the jobs to run and then to wait until that module completes, then run the next.  


run Step1.yxmd
Wait

run Step2.yxmd
Wait

run Step3.yxmd
Wait


Or, if I have a group of modules that can run concurrently but subsequent jobs are dependent on all of them to finish, i can let all those jobs run and have the next step wait for those to complete to begin.  

run Step1A.yxmd
run Step1B.yxmd
run Step1C.yxmd
run Step1D.yxmd
Wait

run Step2.yxmd
Wait

run Step3.yxmd
Wait


I know this is very simplistic, but hoping it shows the need.  Also, we do have the scheduler set up to use, so if there is a way to set dependencies between modules within Scheduler, that might be helpful.  Just haven't found anything.  

Thanks!

  • Troubleshooting
It would be nice to have the annotations that a user gives a tool with a different background color on the canvas than those tools where the annotation is being automatically populated.  Example would be the user gives a tool a specific name that shows up in blue but the formula tools that display the formula preview under the tool show up in yellow.
  • Troubleshooting
When a process is running in foreground, the GUI does an excellent job of giving feedback to the user as to which "step" the job is running and how much data is processing through the active tools.  When that same job is scheduled, the amount of information is limited to when the job began execution.

If a tool was able to give checkpoint status out to the user, we could better monitor the progress of scheduled jobs.  The visibility to the job is most important for long running jobs.  We've unfortunately had instances where we have had to cancel jobs and to restart them not knowing how close or how far from finishing they were.

Thanks for your consideration,

Mark
  • Troubleshooting
I have several modules that need to run in sequence.   Can a ksh or some other program be used to string the modules together?  

So that if I have Step1.yxmd, Step2.yxmd and Step3.yxmd.  2 is dependent on 1, 3 is dependent on 2.  I want to tell it the jobs to run and then to wait until that module completes, then run the next.  


run Step1.yxmd
Wait

run Step2.yxmd
Wait

run Step3.yxmd
Wait


Or, if I have a group of modules that can run concurrently but subsequent jobs are dependent on all of them to finish, i can let all those jobs run and have the next step wait for those to complete to begin.  

run Step1A.yxmd
run Step1B.yxmd
run Step1C.yxmd
run Step1D.yxmd
Wait

run Step2.yxmd
Wait

run Step3.yxmd
Wait


I know this is very simplistic, but hoping it shows the need.  Also, we do have the scheduler set up to use, so if there is a way to set dependencies between modules within Scheduler, that might be helpful.  Just haven't found anything.  

Thanks!

  • Troubleshooting
Add an option to cancel an occurrence currently queued to run without it removing, or completing, the original schedule. Not sure if this is by design or a bug but when you cancel a workflow that's in queue, it sets the scheduled workflow to "Completed" even though you just wanted to stop that occurrence and still keep the workflow schedule “Active”.

Also, adding an option to PAUSE a scheduled module. This is useful when you need to temporarily suspend a workflow from running, but save the hassle of re-configuring the schedule when you want to turn it back on.
  • Troubleshooting
Add an option to cancel an occurrence currently queued to run without it removing, or completing, the original schedule. Not sure if this is by design or a bug but when you cancel a workflow that's in queue, it sets the scheduled workflow to "Completed" even though you just wanted to stop that occurrence and still keep the workflow schedule “Active”.

Also, adding an option to PAUSE a scheduled module. This is useful when you need to temporarily suspend a workflow from running, but save the hassle of re-configuring the schedule when you want to turn it back on.
  • Troubleshooting
I would like the ablity to view the processing order of tools within module prior to processing and if needed reprioratize which tool processes first/last.  It would also be great to have the ablity to disable a subset of tools within a module prior to processing.
  • Troubleshooting
I would like the ablity to view the processing order of tools within module prior to processing and if needed reprioratize which tool processes first/last.  It would also be great to have the ablity to disable a subset of tools within a module prior to processing.
  • Troubleshooting
Create a new module that outputs statistics after processing. For instance creating a table of all used modules by reference number with fields for records input, records output, processing time, processor load, memory used.  As well as starttime, endtime, username, hostname, etc.  This would make debugging quite a bit easier, expecially if the results could be output to Excel.
  • Troubleshooting
Top Starred Authors