Alteryx Designer Desktop Ideas

The option to "Disable all Tools that Write Output" doesn't currently affect the Publish to Tableau Server output tool.

I would like to propose an idea for the evolution of INPUT TOOLS and OUTPUT TOOLS in relation to their compatibility with DATA CONNECTIONS configured in Settings ALTERYX.

Indeed, it is now possible to create a Data Connection of SQL Bulk Loader (SSVB) type and to use this DATA CONNECTION in an Input Tool. The configuration is possible (Choose the table, the query ...), when you run the Workflows it works and you get the data well.

On the other hand, when we try to click again on the INPUT Tools, there is an error message and we cannot retrieve the contained request because the File Format is unknown.

After analysis with the support, there is a compatibility problem between SSVB and INPUT Tools in ALTERYX because there is no support for SSVB in INPUT in ALTERYX but it is supported in OUTPUT Tool.

My proposal would therefore be that there be a validation made during the configuration of the INPUT Tool and the Output Tool between the DATA Connection chosen and the type of tool used.

Thnaks for your return.

Regards,

Psyrio

I would like to propose a more interactive results window.  The reason is that if you click on any of the tool hyperlinks next to the messages while the output is compiling, you get trapped inside that tool's output for the entire time that the workflow runs.  You do not get to see any additional workflow result/detail as it compiles until after the entire workflow is run. It would be great if a user could escape back to the main workflow's results.

For instance if I am running a fairly long or complex workflow that does not all fit on one screen...I may want to zoom in on a tool if it has a warning or error before the workflow finishes.  By clicking on the hyperlink "Union(5)" the palette will zoom to Union (5) so I can see which tool is a problem.

I can see any messages attached to Union(5), however I am stuck with this view the rest of the time the workflow runs.  Clicking on the canvas (or really any other action I try to take) does not take me back to the overall workflow result window.

Granted if I have an error I may want to stop the workflow altogether, but sometimes warnings may prompt further investigation once the workflow is run and I may want to get an immediate read on where in the workflow the problem is while it is still running...which inputs might I have to check etc.

When I select multiple containers using control. I can see the configuration pane still on the left. If I adjust anything there it will only adjust the last selected container. I would like it to adjust all selected containers.

I guess it's better if the current column filter feature would cover the entire data set not just the partial results. This would be useful especially if after you run the complicated workflow and you just want to test the data particular nodes in the canvass. 

DearAlteryx team and community,

all the best for 2021!

Thank you very much for enhancing the output option from Alteryx Designer to Excel keeping the format.

For a lot of my use cases this is very helpful!

Still, there are some use cases left. In case I want to overwrite a calculated/linked number (e.g. calculated prediction) with the Actual number, it would be very helpful to feed into those cells as well. At the moment Alteryx is doing the job but I receive a lot of Excel Errors (xml errors) and a corupt Excel file when overwriting calculated fields/linked fields.

Is there a chance to extend the current setup for all of those cases?

Thanks and best regards

Chhristoph

All,

I'd like to be able to disable the notification to update Alteryx toward the top of the screen.  The longest choice is only one year...I'd like to turn it off forever, since we control versions used internally and it is driven by the server version.

Folks are updating their software when they shouldn't and causing issues for each other.

Thanks for any advice.

Today the Autofield tool transforms the fields into byte by default when it considers that the content is suitable while we expect text in it and that it can simply be a field not filled in in the context current but which may be later.

The idea would be to be able to choose which type by default to implement on text or empty fields and not the default byte because a byte field is not recognized on a formula using an IN for example which can produce errors in the following workflows.

Hello,

My idea is that the current Download tool does not handle errors and continues its path even if it does not find for example a file in the transmitted URL or if it does not find the hostname it crashes.

In the case of a user with several URLs in a row, this is penalizing.

In the case of downloading files with recording, it still writes a file (thus overwriting the existing file) but which is not openable and is not in the correct format. (BLOCKED file!) Which then causes problems in workflows reading these files.

The idea would be to put a second output to this tool for all the URLs where there was a problem (non-existent hostname, file not found, HTTP KO) and one where it received the expected elements so as not to prejudice the processing. and allow better management of error cases.

Regards,

Bruno

Yes.  I'll admit it.  I have set up email events and forgot to enter my address into the 'to' field.  The upshot is that an error was occurring in my workflow, the tool went to email me, and then double borked because I hadn't filled in a recipient. 

Lots of tools error out without appropriate configuration applied, it shouldn't be too difficult to get this working on the events panel also. 

Thank you for attending my TED talk on improvements to the Events pane.

Hello,

In cases where more than one field is being used in a join, the "Join (Tool ID) String fields can only be joined to other string fields" error message could be improved by indicating which field has a mismatch.

For example, if I'm joining Fields A, B, C, D... to fields Z, Y, X, W... in Join tool 24, and for some reason Field Z gets changed from String to Double, it'd be nice to see a message like:

"Join (24) (Field 1) String Fields can only be joined to other String fields"

or

"Join (24) String Fields can only be joined to other String fields (A)"

So that I know I need to go to a select tool and change the type of either A or Z.

Otherwise I look at the Join tool output and try to figure out which pair no longer has matching types, which can take a minute when dealing with a multiple-point join.

Thank you!

Simple request to revert back to the functionality that generated an error at the onset of running the workflow.  

File has a different Schema than the first file in the set- This is error received in Dynamic Input Tool, when there is change in data type any column in the file.  My File has a column Which comes in " V String" Data type but suddenly it comes in " Double" then this error will come.

Tool should ignore this error and consider incoming data in a data type defined while in configuration, so request to provide feature to configure data type in Dynamic Input Tool.

When creating annotations in the new image template tool as part of intelligence suite, a feature improvement would be the ability to modify the annotation, to change the dimensions of it.

Currently the only option is to cancel and redraw but being able to edit and drag the existing annotation would be a great addition. This is because the sizing and position of the annotation is important in the OCR process, and when there are many annotations on a page a user is likely to only need to make minor adjustments instead of deleting and redrawing. A mock up is below.

In the new Intelligence Suite tools the PDF Image Template tool allows a user to select portions of the document to be OCRed downstream by the Image to Text tool, however there is no way to currently zoom in and out of the document to draw the annotations, the only way I have found is to stretch the configuration window and the PDF width will autoscale, but doing so will lose the annotations.

So the request is to have zoom in/out and pan options within the configuration pane to improve the UX.

We have discussed on several occasions and in different forums, about the importance of having or providing Alteryx with order of execution control, conditional executions, design patterns and even orchestration.

I presented this idea some time ago, but someone asked me if it was posted, and since it was not, I’m putting it here so you can give some feedback on it.

The basic concept behind this idea is to allow us (users) to have:

• Design Patterns
  • Repetitive patterns to be reusable.
  • Select after and Input tool
  • Drop Nulls
  • Get not matching records from join
• Conditional execution
  • Tell Alteryx to execute some logic if something happens.
  • Record count
  • Errors
  • Any other condition
• Order of execution
  • Need to tell Alteryx what to run first, what to run next, and so on…
  • Run this first
  • Execute this portion after previous finished
  • Wait until “X” finishes to execute “Y”
• Orchestration
  • Putting all together

This approach involves some functionalities that are already within the product (like exploiting Filtering logic, loading & saving, caching, blocking among others), exposed within a Tool Container with enhanced attributes, like this example:

The approach is to extend Tool Container’s attributes.

This proposition uses actual functionalities we already have in Designer.

So, basically, the Tool Container gets ‘superpowers’, with the addition of some capabilities like: Accepting input data, saving the contents within the container (to create a design pattern, or very commonly used sequence of tools chained together), output data, run the contents of the tools included in the container, etc.), plus a configuration screen like:

1. Refers to the actual interface of the Tool Container.
2. Provides the ability to disable a Container (and all tools within) once it runs.
   • Idea based on actual behavior: When we enable or disable a Tool Container from an interface Tool.
3. Input and output data to the container’s logic, will allow to pickup and/or save files from a particular container, to be used in later containers or persist data as a partial result from the entire workflow’s logic (for example updating a dimensions table)
   • Based on actual behavior: Input & Output Data, Cache, Run Command Tools, and some macros like Prepare Attachment.
4. Order of Execution: Can be Absolute or Relative. In case of Absolute run, we take the containers in order, executing their contents. If Relative, we have the options to configure which container should run before and after, block until previous container finishes or wait until this container finishes prior to execute next container in list.
   • Based on actual behavior: Block until done, Cache, Find Replace, some interface Designer capabilities (for chained apps for example), macros’ basic behaviors.
5. Conditional Execution: In order to be able to conditionally execute other containers, conditions must be evaluated. In this case, the idea is to evaluate conditions within the data, interface tools or Error/Warnings occurrence.
   • Based on actual behavior: Filter tool, some Interface Tools, test Tool, Cache, Select.
6. Notes: Documentation text that will appear automatically inside the container, with options to place it on top or below the tools, or hide it.

This should end a brief introduction to the idea, but taking it a little further, it will allow even to have something like an Orchestration layout, where the users can drag and drop containers or patterns and orchestrate them in a solution, like we can do with the Visual Layout Tool or the Interactive Chart tool:

I'm looking forward to hear what you think.

Best

If you open a workflow in Designer from the Gallery, make some changes, and then attempt to save it back to Gallery (i.e., Ctrl-S), you receive the Save Workflow dialog (as per attached).  However, if you then realize that you want to make an additional change before saving the workflow and click 'Cancel', the workflow closes without saving.  The expected behavior would be for the Save Workflow dialog to close, but not the entire workbook.  This is terrible functionality and should be fixed because it results in lost work.  Thank you

Using a wide-screen monitor and canvas, I typically initiate a workflow by clicking the RUN button.  But, in my canvas, I am usually working in the left or middle portion of the screen.  The Run button is to the far right and find myself moving to the right to click the button and then back to my workflow location. 

I'd like to be able to have this relocated or optionally functionality to move this button (maybe even creating a customized personnel quick access toolbar or button panel) to the left portion of the canvas window.  Sure, there is a key board shortcut, but if the button is provided, than it implies that it is a valid UI feature.  I've also seen and liked the ability to have this as a right-click menu enhancement. 

When using Dynamic Input with databases, the Database may be returning errors or other information that the tool cannot parse into a dataset.

It would be great if we could see the 'raw' response from the database somehow, as this might provide insight into why we are not getting the expected results. 

If the tool could output an optional error column that has the unparsed response from the database server, it might allow us to debug the problem ourselves. 

If the returned data is actually a string response from the database, but one that is flawed in some way, we might still be able to parse data out of it to 'ride over' the error.