cancel
Showing results 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

## Repair Macro Path

We all love seeing this.  And, it's fairly easy to fix, just go find the macro and insert a new copy.  But, then you have to remember the configuration and hope that it was simple.

With the tool that's there, the XML still contains the configuration, all that's missing is the tool path.    It would be great to be able to right click and repair the path from the context of the missing macro.

## Server Macro Bank - Reference Macros on the Server

Current State:  When a macro contains nested macros the only method that reliably works to share them is via yxi (which I fondly refer to as my wixies).

Future State:  Allow macros published to the gallery be their own tool palette so that when I or any user connects to the server the macros are there and just work, no import, no visible install just a single set of tools that work on that server.

Side task - also get export to yxi

• Category Macros

## Monetary Unit Sampling

Using R tool, I created Monetary unit sampling macro. Auditors often use MUS methodology to select samples from population for testing.

Check it out and let me know if you have any suggestions or comments.

• Category Macros

## Debug batch macros: Test Values

When building and debugging batch macros - it is important to be able to add test values and use these for debugging. However, the input values in the interface tools section do not allow input, and the ability to save or load test values also does not work.

While there is a workaround - setting the values in the workflow variables - this does not work fully (it doesn't reflect in the interface view; and is incorrect in the debug report) and is inconsistent with all other macro types.

Please could you make this consistent with other ways of testing & debugging macros?

All screenshots and examples attached

Screenshot 1: not possible to capture test values

Screenshot 3: Workaround by using workflow variables

Scree

Screenshot 4: Values entered do not reflect properly

Screenshot 5: Debug works partially

## Find Missing Macro

Idea: Prompt the user to find a missing macro instead of the current UX of a question mark icon.

Issue: When a macro referenced in a workflow is missing, then there is no way to a) know what the name of the macro was (assuming you were lazy like me and didn't document with a comment) and b) find the macro so you can get back to business.

When this happens to me know, I have to go to the XML view and search for macros and then cycle through them until I find the one that's missing. Then I have to either copy the macro back into that location or manually edit the workflow XML. Not cool man.

Solution: When a macro is missing, the image below at the right should be shown. In the properties window, a file browse tool should allow the user to find the macro.

## Which version of macro is in use?

When you right click on a Macro tool (e.g. Google Analytics) within a workflow, you can choose the version of the tool to use. However, it does not indicate which version of the tool is already in use.

Why is this an issue for me?

I have a workflow with 15 instances of the Google Analytics tool.  (I needed to use the API for each month fo GA data and then use a join. I built it this way due to the restriction on the number of records.)

So when I update the Google Analytics tool I have to do it 15 times. I'd like to be sure the update is needed before I start.

Alteryx Support confirm that there is no way to tell which version of the macro is in use.

## Pass Parameters into Pre/Post SQL Statements

Right now in order to pass a parameter to pre/Post SQL we need to make a macro as a work around.

It would be really great if this was a native capability for the output tool so we don't have to replicate all the output too fields as macro inputs

## Add List-Based Mode to Dynamic Select

A seemingly minor task that has popped up several times on my team is the ability to select a subset of columns using an input list.  Different people have achieved this in different ways (transpose/join/cross-tab, dynamic rename/select), but it seems like a common enough task to warrant a single-tool solution.

R has a simple way to do this:

# create a vector of the columns we would like to select
columns <- c("column_b", "column_d")

# subset based on the column names we defined in our "columns" vector
df_subset <- df[columns]

We have built a macro to achieve this (attached), but I would love if there was a second input anchor on the Dynamic Select tool, with list-based select mode as an option in the dropdown.

The macro currently has a minor annoyance, where the user gets a "RecordInfo::CreateRecord" error presented on their palette when they choose the "Keep Columns in List" entry.  This error goes away with a run or an F5 refresh, but if anyone has a suggestion for getting rid of this, it would also be appreciated.

• Category Macros

## Server Macro Bank - Reference Macros on the Server

Current State:  When a macro contains nested macros the only method that reliably works to share them is via yxi (which I fondly refer to as my wixies).

Future State:  Allow macros published to the gallery be their own tool palette so that when I or any user connects to the server the macros are there and just work, no import, no visible install just a single set of tools that work on that server.

Side task - also get export to yxi

• Category Macros

## Run macros in debug mode

Despite being an Alteryx user for 2 and a 1/2 years this is something I have only recently came across but it does not appear that you are able to use debug mode appropriately with macros.

What I mean is, I have a macro input which drives a series of drop down boxes. In debug mode my drop down boxes will not populate. Now I understand why, Alteryx doesn't know what the input is so it doesn't generate the meta data for the debug mode drop downs.

What I suggest Alteryx do is automatically convert your macro inputs for file browses for the purpose of debug mode (I had to do this myself manually and it was a tedious task, not only to set up but then maintain two separate versions, one essentially an application and one a macro).

Or, by default debug mode uses the macro input data to run through debug mode as.

Ben

## Allow Last Run metadata to persist

This is similar to a prior idea now marked complete "Allow macro metadata to persist until next run".  I tried the check box solution and still have the same issue, running V11.

What we NEED is for tools that derive columns like CrossTab to retain metadata from the most recent run and thus pass that metadata downstream for further tools and development.

Use case:

I have several cross tabs and before V11 I could run the flow once to push metadata downstream, then add or modify tools downstream and the derived fields from the cross tab stayed available in those tools to be recognized and referenced as I add more tools and logic. Now in V11 I am finding if I click on a tool or add a tool downstream the metadata for the derived columns disappears.

I attached pics to illustrate where I have 6 CrossTabs and decided I needed to add a summary downstream.  I had to run the flow to get metadata populated which is normal and I added the first summary, then inserted another summary and immediately the derived column metadata was lost in all paths after the crosstabs.  so ended up having to re-run the flow 5 more times for each summary tool added. then I had to re-run it 5 more times to adjust column names in selects after downstream joins.

I end up wasting a lot of time having to re-run a sufficient test file to feed all the variety of data necessary to generate all columns between most edits or new tool adds.  What used to take ~5 minutes to do now takes ~35

I recall seeing and discussing this issue previously and hoped the check box would resolve but It does not fix the issue.

We see similar issue for tools downstream from other tools where the columns are derived or uncertain until that tool runs, such as, transpose, Joins and Unions.  I recall some discussion at user groups and in the community but the only reference I found this morning of seeming relevance is the one I mentioned above.

## Which version of macro is in use?

When you right click on a Macro tool (e.g. Google Analytics) within a workflow, you can choose the version of the tool to use. However, it does not indicate which version of the tool is already in use.

Why is this an issue for me?

I have a workflow with 15 instances of the Google Analytics tool.  (I needed to use the API for each month fo GA data and then use a join. I built it this way due to the restriction on the number of records.)

So when I update the Google Analytics tool I have to do it 15 times. I'd like to be sure the update is needed before I start.

Alteryx Support confirm that there is no way to tell which version of the macro is in use.

## Pass Parameters into Pre/Post SQL Statements

Right now in order to pass a parameter to pre/Post SQL we need to make a macro as a work around.

It would be really great if this was a native capability for the output tool so we don't have to replicate all the output too fields as macro inputs

## Allow Last Run metadata to persist

This is similar to a prior idea now marked complete "Allow macro metadata to persist until next run".  I tried the check box solution and still have the same issue, running V11.

What we NEED is for tools that derive columns like CrossTab to retain metadata from the most recent run and thus pass that metadata downstream for further tools and development.

Use case:

I have several cross tabs and before V11 I could run the flow once to push metadata downstream, then add or modify tools downstream and the derived fields from the cross tab stayed available in those tools to be recognized and referenced as I add more tools and logic. Now in V11 I am finding if I click on a tool or add a tool downstream the metadata for the derived columns disappears.

I attached pics to illustrate where I have 6 CrossTabs and decided I needed to add a summary downstream.  I had to run the flow to get metadata populated which is normal and I added the first summary, then inserted another summary and immediately the derived column metadata was lost in all paths after the crosstabs.  so ended up having to re-run the flow 5 more times for each summary tool added. then I had to re-run it 5 more times to adjust column names in selects after downstream joins.

I end up wasting a lot of time having to re-run a sufficient test file to feed all the variety of data necessary to generate all columns between most edits or new tool adds.  What used to take ~5 minutes to do now takes ~35

I recall seeing and discussing this issue previously and hoped the check box would resolve but It does not fix the issue.

We see similar issue for tools downstream from other tools where the columns are derived or uncertain until that tool runs, such as, transpose, Joins and Unions.  I recall some discussion at user groups and in the community but the only reference I found this morning of seeming relevance is the one I mentioned above.

## Case insensitive join

Hey all,

The join tool currently does not allow case-insensitive joins, but the find/replace tool does.    Additionally- even if both sides are identical, the join tool will not join "Sean's house" to "Sean's house" because of the non-letter character in the middle.    Finally - if one side is a string(2), and the other is a vString(200) - even if you have a single identical character on both sides you get uncertain outcomes unless you force the type

Please could you consider amending the join tool to include 3 new options or capabilities:

- Case insensitive join

- Allow full Unicode character set in join

- Full match across text types (irrespective of string size) - this would allow a string(2) value to match to a string(100) value as long as the string(100) value only has the same 2 characters in it as the string(2) value

That would remove a load of work from every text-join that's being done on every canvas we do.

Thank you

Sean

## Case insensitive join

Hey all,

The join tool currently does not allow case-insensitive joins, but the find/replace tool does.    Additionally- even if both sides are identical, the join tool will not join "Sean's house" to "Sean's house" because of the non-letter character in the middle.    Finally - if one side is a string(2), and the other is a vString(200) - even if you have a single identical character on both sides you get uncertain outcomes unless you force the type

Please could you consider amending the join tool to include 3 new options or capabilities:

- Case insensitive join

- Allow full Unicode character set in join

- Full match across text types (irrespective of string size) - this would allow a string(2) value to match to a string(100) value as long as the string(100) value only has the same 2 characters in it as the string(2) value

That would remove a load of work from every text-join that's being done on every canvas we do.

Thank you

Sean

As seen in This Discussion Post,  the idea here is to be able to add a link to example workflows in macro descriptions - like the ones seen in native tools.

Filter Tool

Many thanks to @jdunkerley79 for demonstrating how this can be done by manually editing the macro's XML - specifically by adding a child element to the <MetaInfo> section, like so:

      <Example>
<Description>Open Example</Description>
<File>\\aSERVER\aRootDir\path\to\Alteryx\Macros\Date Wizard\Date Wizard Examples.yxmd</File>
</Example>

One small caveat is that it doesn't support truly relative paths.  @PaulN explained in the discussion post that a relative reference here would search in the sample folders.

"Alteryx default behavior is to look for examples under .\Alteryx\Samples\02 One-Tool Examples or Alteryx\Samples\02 One-Tool Examples (or .\Alteryx\Samples\en\02 One-Tool Examples)."

Having said that, trying to reference a macro example in the same folder (using a relative reference) will throw an error given the following situation:

Package Structure:

Date Wizard.yxmc XML edits:

      <Example>
<Description>Open Example</Description>
<!-- THIS WORKS -->
<File>\\aSERVER\aRootDir\path\to\Alteryx\Macros\Date Wizard\Date Wizard Examples.yxmd</File>
<!-- THIS DOESNT
<File>Date Wizard Examples.yxmd</File>
<File>.\Date Wizard Examples.yxmd</File>
<File>./Date Wizard Examples.yxmd</File>
-->
</Example>

This shows a link in the Macro description but yields an error (shown below) when it is clicked.

Once again, this works fine with an absolute file path reference.

Here is ultimately what I am suggesting:  Can we add an option to the Interface Designer (that updates the XML) and have it allow relative paths?  Allowing relative paths would obviously be essentially to maintaining the macro's ability to be "lift-and-shift" when packaged/moved/uploaded to servers/galleries etc.

I'm assuming the option could look something like this, similar to the "Help" file -only it would show link in the macro description...

Interface Designer Suggestion

In conclusion, this would be very useful in providing links to example workflows for custom macros that may be complex and/or not self-explanatory.

Cheers,

Taylor Cox

## Run macros in debug mode

Despite being an Alteryx user for 2 and a 1/2 years this is something I have only recently came across but it does not appear that you are able to use debug mode appropriately with macros.

What I mean is, I have a macro input which drives a series of drop down boxes. In debug mode my drop down boxes will not populate. Now I understand why, Alteryx doesn't know what the input is so it doesn't generate the meta data for the debug mode drop downs.

What I suggest Alteryx do is automatically convert your macro inputs for file browses for the purpose of debug mode (I had to do this myself manually and it was a tedious task, not only to set up but then maintain two separate versions, one essentially an application and one a macro).

Or, by default debug mode uses the macro input data to run through debug mode as.

Ben

## Monetary Unit Sampling

Using R tool, I created Monetary unit sampling macro. Auditors often use MUS methodology to select samples from population for testing.

Check it out and let me know if you have any suggestions or comments.

• Category Macros

## Allow "optional incoming connections" to actually be optional for batch macros

I decided to get real fancy when building a standard macro the other day. I checked the box on my macro input that made the connection optional:

It worked really well. My macro then became more complex, so I changed it to a batch macro. To my great surpise/astonishment/shock, the optional incoming connection is no longer optional:

The standard macro is working as expected on the left, but the batch macro is producing an error because my optional connection is requiring that something be connected to it.

I've been told that the code to make it optional is not there for batch macros and that this would be a product feature/improvement.

Completed Ideas

• ## That

Top Starred Authors