The Inspire Pin contest has begun! Win a free pass to Inspire by submitting your design to be made into a real-life pin! Submission details can be found here.
Alteryx Designer Desktop Ideas
Share your Designer Desktop product ideas - we're listening!Submitting an Idea?
Be sure to review our Idea Submission Guidelines for more information!
Submission GuidelinesFeatured Ideas
In the 20 years of my career I have built many automations using many tools. Alteryx is one of the best but lacks a key function that many others have. The File Browse Tool and the Folder Browse tool should be able to be configured with default values.
There should be an option under the File Specification that says "Default Location". When the user clicks browse button in the Analytical Interface it should default to opening that location ( eg.. \\ShareDrive\Reports\Finance\ ). If this location in inaccessible by the user or Account running the job then either an error should be thrown and the flow stopped or a default location open as in 2024.2
Users have requested this as when you have a large network browsing to the file you need can be slow and cumbersome. Ideally we should be able set the default location in the Designer to the folder where the file they want "most likely" is. Saving the user time and effort. This same concept applies to Folder Browse.
The funny part about this is when you ask Alteryx Co-Pilot (or ChatGPT, or Microsoft Co-Pilot) how to do this. Even it figures this was a option that exists.
When loading multiple sheets from and Excel with either the Input Data tool or the Dynamic Input Tool, I usually want a field to identify which Sheet the data came from. Currently I have to import the Full Path and then remove everything except the SheetName.
It would be great if there was an option to output she SheetName as a field.
Hello all,
As of today, you can populate the Drop Down tool in the interface category with a query launched from a in-memory connection. I would really appreciate the ability to use instead an in-db connection.
Why ?
It means managing two connections instead of one, and finding ways to manage it on server for both of them, etc etc.. Simplicity is key.
Best regards,
Simon
When I make the workflow, the font size on Result window is no problem.
But, when we show the contents of Results window on the presentation or online meeting, the font size is too small.
I want the function which is enlarge the font size. The important point is that the current font size is okay on making workflow and the large font size is only needed on showing to the another people on presentation or online meeting.
One more point to add, it would be helpful to be able to change the font size with Ctrl + mouse wheel.
Push the zoom button:
Hello,
The Data source window allow severla kind of connections like quick connect, ODBC, etc. But the order is not the same and this is confusing :
Best regards,
Simon
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:
- Refers to the actual interface of the Tool Container.
- 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.
- 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.
- 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.
- 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.
- 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
- z_cpkharris on: Enable horizontal mouse scroll on workflow canvas ...
-
TheOC
on:
Add pin a workflow to the Alteryx Designer file-->...
-
Carolyn
on:
Blob output to be turned off with 'Disable all too...
-
TheOC
on:
Add Tool Name Column to Control Container metadata...
-
fmvizcaino
on:
Show dialogue when workflow validation fails
-
TheOC
on:
Create a SharePoint Render tool
-
Kenda
on:
Non-Equi Relationships in the Join Tool
- AncientPandaman on: Continue support for .xls files
- EKasminsky on: Auto Cache Input Data on Run
-
TheOC
on:
Global Field Rename: Automatically Update Column N...
