Alteryx Designer Ideas

Hello Team,

Currently, in the select tool, we have to scroll up or down to check or see the list of the fields. In case, if the user wanted to change the data type, they can scroll into the list. Like, I am working on the mid-size data, and sometimes data contain 300+ fields, if I need to change anything in the data type I have to search by scrolling up or down. 

The idea here is, If you provide a search bar under Field, it will be a great help to all, in case if anyone needs to go for some specific field, the user just types the name in the search bar and make changes quickly. The select tool is important and we used much time while working on the flow. 

Thank you,

Mayank

Our company often builds applications where we need the ability for it to dynamically update dropdowns based on a user's previous selections. 

For example: 

• A user needs to select their Server, database, and table for analysis (3 dropdowns).
• When the user selects their server, a query is run to get a list of all databases on that server. Then the database dropdown will automatically populate with this list of databases. 
• The user then makes a database selection, and a query is then run to get all tables within that database. The table dropdown will automatically populate with this list of tables. 
• The user makes their table selection, and then runs their analysis using the server, database, and table variables with values that they have selected from each dropdown.

We can do this in other programs, but unfortunately the lack of dynamic selections/dependent dropdowns is a big limitation for us when building Alteryx applications. Our current workarounds are chaining applications together, or using PyQt within the workflow. Chaining is clunky and often causes unforeseen issues when uploading to Server with errors that are non-descriptive, and using PyQt comes with Python versioning issues. 

If this interactivity can somehow be added to Alteryx applications it would be a huge upgrade to our current Alteryx processes. Any suggestions for further workarounds would also be helpful!

Thank you, 

Amanda 

The interactive results pane is great, but wouldn't it be cool if you could interact directly with the result pane to do things like filtering.

There are a few too many steps with the method at the moment, where you need to either copy the value or type it into the filter pop up. A simple right click and filter on selected value would be a big ux improvement.

Hi team,

Currently, we can FILTER results in the result window using some string operations like "String equals", "String Contains", etc.

Firstly, it's a great feature. Kudos for the same.

However, it would be really helpful if we can add the IN operator functionality to this Result window FILTER.

Most of the time, we always want to check for multiple values while filtering the data.

I am attaching a screenshot of the FILTER location that I am referring to!

For eg, In the above screenshot of the result window, I want to filter for Name IN ('Bullock County','Baldwin County','Butler County')

Kindly look into this.

Thanks in advance.

Regards,

Shreyansh Rathod

Hi,

It would be great if users have the option to display the number of records that go in and out of the different tools in your canvas. This allows users to very quickly see how many records are in their datasets, and especially quickly analyze the results of specific actions such as joins, filters etc. without the need to open each individual tool. Especially when performing joins this can be very useful to quickly see how many of your rows have been successfully joined. I think this will give users a feeling that they have more control over their data and a better understanding of what is happening in Alteryx. Also if you quickly want to review a complex workflow (especially when it is not your own) this could be a huge timesaver. Simply run the workflow and follow the numbers to see what is happening and identify tools that might cause issues.

Love to hear what you think!

It would be great to have an option in the Output Data tool to write the workflow name to the Info properties of Excel outputs.

Maybe something like this:

So that whenever you open an Excel file you always have a way of finding the name of the workflow that created the file.

This would make it so much easier as I often have to share Excel files with colleagues and customers and then need a way of tracking them back to workflows weeks or months later.

Hi 

The wording of the tool tip displayed in results window cells with long strings is misleading.  The current wording is "This cell has truncated characters".   

New users tend to infer that this means that the data value has been truncated somewhere upstream.  See here, here and here.   Changing this message to something like "Only a portion of long strings is displayed" will help reduce the confusion immensely.

Dan  

It would be useful to allow for temporary local variables in formula tools. This could make code shorter, better readable, easier to maintain and help to avoid auxiliary columns which have to be deleted afterwards.

Arbitrary example for illustration:

if Length([Col1] + [Col2] + [Col5]) > 50 then
    Left([Col1] + [Col2] + [Col5], 48) + "..."
else
    [Col1] + [Col2] + [Col5]
endif

versus

tmpstr = [Col1] + [Col2] + [Col5]
if Length(tmpstr) > 50 then
    Left(tmpstr, 48) + "..."
else
    tmpstr
endif

The idea is that the temporary variable has limited validity inside the formula for a specific cell.

When a field's data type has changed or it has been renamed, there is a visual cue in the form of highlighting to indicate that there has been a change. When fields has been reordered, there is no cue. I am looking at a wf with many select tools and they appear to do nothing. I have to spend some time and effort to see if they reorder fields or not. Please add a visual cue to help me understand which fields have been reordered or at least that one or more fields have been reordered. Thank you.

When building API calls within Alteryx there are a few common steps required

1) Build out the URI for the API call (base URL plus any query parameters)

2) Deal with authentication, such as basic authentication requires taking a key and secret, base 64 encoding and passing this into the tool

3) parsing the results out and processing these downstream

For this idea I am specifically focusing on step 3 (but it would be great to have common authentication methods in-built within the download tool (step 2)!).

There are common steps required to parse out the results, such as using Filter (to check for a 200 response), JSON parse, text to columns and then cross tab to get the results into a readable format. These will all be common steps anyone who has worked with APIs will be familiar with:

This is all fine for a regular user to quickly add in and configure these tools. However there is no validation here for the JSON result being as expected, which when embedding an API into a batch macro or analytic app means it can easily fail.

One example of a failure which I've recently come across is where the output JSON doesn't have all fields (name:value pairs) depending the json response. For example using the UK Companies House API, when looking at the ceased to act field at this endpoint - https://developer-specs.company-information.service.gov.uk/companies-house-public-data-api/resources... the ceased to act field only appears in the results if a person has actually ceased to act. This is important if you have downstream tools such as a formula to create a field [Active] where you have:

IF ISNull([ceased_to_act]) THEN "Active" ELSE "Ceased to Act" ENDIF

However without modification the macro / app will error if any results are returned where there is not this field.

A workaround is to add in the Crew Ensure Fields or union on a list of fields, to ensure that the Cease to Act field is present in the output for all API calls. But looking at some other tools it would be good if an expected Schema could be built in to the download tool to do this automatically.

For example in Power Automate this is achieved as follows:

I am a big advocate of not making things unnecessarily complicated. Therefore I would categorise this as an ease of use feature to improve the experience of working with APIs within Alteryx and make APIs (as load of integrations are API based) accessible to as many users as possible.

Hi all,

When debugging an error, we need to verify tool by tool in a sequence to better understand what is really going on.

Sometimes the tools are miles away from each other. Imagine a gigantic workflow with a lot of connections going back and forth and wireless connections everywhere to help the workflow organization. Here is an example with more than 1300 tools: 

My idea is to have a shortcut showing all the previous/next tools and by selecting the previous/next one you go directly to them.

Something like this: 

What do you guys think about that?

Best,

Fernando Vizcaino

When Alteryx Designer detects an existing 32-bit Oracle driver on a user's machine, it displays an error message saying  that it requires a 64-bit driver.  If there is no driver at all installed, it will go ahead and install one. 

Can we get Alteryx to simply prompt the user to install the 64-bit driver instead of the 32-bit driver present error message? 

(I know they can co-exist since removing the 32-bit driver will cause Alteryx to install its own 64-bit driver after which one can re-install the 32-bit driver.)

Thanks!

D

There are a fixed number of data types and I hate having to scroll through them when I set the data type in a Formula tool. Can the drop down expand into a window that shows them all at once? It doesn't take up that much real estate. They can even be grouped by type. I mocked it up in Excel.

The Output tool currently creates a zero-row file if you filter all the rows out (an empty file)

However - there's a very common need to say "don't generate a file at all if there are zero rows" - for example if you are generating a "Daily Details" file and there are no daily details today, you want to suppress this file.   This frequently trips up newer users since the only way to suppress a zero-row output file today is to it with macros.

Could you add a flag to the output tool to "Suppress empty files" so that if there are no rows to be written, Alteryx does NOT create an empty file?   This way the user can be in control of what to do with empty record sets?

 This might be something that people see as a feature, but if you've got an input tool on your canvas that isn't connected to anything, I'd like the engine (either) to ignore reading the data.  

I often put tools onto the canvas and build around the input and in reality (or when working with large files), the execution is slower than it needs to be with reading files that are not used.

Cheers,

Mark

Here is the issue I have, when you are using a Join tool and you have multiple columns that you are joining on (to the point that they don't all show in the 
Configuration window), i have a tendency to use the mouse scroll wheel to move down to see additional columns i am joining on.  The mouse scroll controls different things depending on where your cursor is.  If your cursor is over the Left or Right columns then the scroll button will change the Fields you are using to join on.  I have messed up more workflows then i care to mention due to this.  I do not think it is appropriate for the scroll wheel to effect and change the fields in the configuration window and it should only be used to scroll up and down in the configuration window.  

it would be great if the formula tool could expand the intellisense to the select column box. For example, I could start typing in the select column box and it would widdle down the list of fields down.let's suppose I wanted to update field 79A, I could type in 7 and it might show something like 

7

17

27

37

70

71

79A

79B.

So if I typed in 79 then, it would further reduce it to 

79A

79B

And i could select 79A.

I find it annoying that the count records and heat map macros have file inputs which point to a W drive. This will show up in workflow dependencies and can cause false alarm warnings. Since these are packaged with Designer, simply change the macros to text inputs instead of file input. 

Thanks!

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