Alteryx Designer Desktop Ideas

Hi,

A lot of companies now are deploying on both AWS and Microsoft Azure.

Alteryx supports AWS S3 object storage out of the box, it would be important to support Microsoft Azure blob as part of the native Alteryx product as well. 

Cheers,

Adrian

Trying to solve some use cases, I realized that I had to simulate the factorial behaviour.

Having a factorial formula can make this process easier.

Thanks!

When you use Create Points tool - you then almost always need to use a Select tool to rename that point.

Can we please add a single text field to the Create Points tool - which would then allow us to create and name a point in one step?

When we create new workflows, we like to have them in our company template, to stnadardise documentation. This makes it easier for a supervisor to review, and for a colleague to pick up the workflow and understand what is going on. For instance, we have all data input on the left, and all error checks and workflow validation on the right, and a section at the top with the workflow name, project name, purpose etc. We have a workflow that we use as a template with containers, boxes and images all in the appropriate places

It would be great if there was an option to select a workflow as a template. When a new workflow is opened, it would load this template rather than having a blank canvas.

Statistics are tools used by a lot of DB to improve speed of queries (Hive, Vertica, etc...). It may be interesting to have an option on the write in db or data stream in to calculate the statistics. (something like a check box for )

Example on Hive : analyse {table} comute statistics; analyse {table} compute statistics for columns;

Alteryx offers the ability to add new formulae (e.g. the Abacus addin) and new tools (e.g. the marketplace; custom macros etc) - which is a very valuable and valued way to extend the capability of the platform.

However - if you add a new function or tool that has the same name as an existing function / tool - this can lead to a confusing user experience (a namespace conflict)

Would it be possible to add capability to Alteryx to help work around this - two potential vectors are listed below:

- Check for name conflicts when loading tools or when loading Alteryx - and warn the user.   e.g. "The Coalesce function in package CORE Alteryx conflicts with the same function name in XXX package - this may cause mysterious behaviours"

- Potentially allow prefixes to address a function if there are same names - e.g. CoreAlteryx.Coalesce or Abacus.Coalesce - and if there is a function used in a function tool in a way that is ambiguous (e.g. "Coalesce") then give the user a simple dialog that allows them to pick which one they meant, and then Alteryx can self-cleanup.

cc: @JarrodT  @NicoleJ 

It would be great if we could have a Windows Active Directory data connector tool added to the standard Alteryx toolset.

MS Excel Power Query and PowerBI both can connect to Active Directory for use as a data source, but are both very cumbersome to use.  Having a connector in Alteryx that can read AD data into a workflow would be super helpful for a long list of use cases.  A couple that are top of mind for me are:

-Leveraging group membership info for dynamic distribution of reports or datasets

-Being able to build reporting and dashboards about the organization (useful for Tech audit, HR, etc.) 

I've seen links to an old project on GitHub of someone that started development on this, but the method (just copy these random .dlls into your program directory) is seriously frowned upon by any enterpise IT.  Would be great if Alteryx could pick up that work, polish it a bit and add it to the actual Alteryx Designer toolset.

Hello all,

I really love the DCM feature present in the last two releases. However, I have noticed the Generic ODBC Connection is missing :

Classic Connection Manager :

Data Connection Manager :

Best regards,

Simon

As of today, for a full refresh, I can :

-create a new table

-overwrite a table. (will drop and then create the new table)

But sometimes, the workflow fails and the old table is dropped while the new one is not created. I have to modify the tool (setting "create a new table")to launch it again, which may be a complex process in companies. After that, I have to modify it again back to "overwrite".

What I want :

-create a new table-error if table already exists

-overwrite a table-error if table doesn't exist

-overwrite a table-no error if table doesn't exist (easy in sql : drop if exists...)

Thanks!

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.

Desperately looking for a way to connect to SQL Server Analysis Services through Alteryx as more and more of our large datasets from our older systems are moving to here in the next few months. We can connect using PowerBi with limitations (connecting 'Live' does not allow merge and connecting with Import, you need to use MDX or DAX syntax). We run into import and export limitations, too. We are not allowed access to the underlying tables, but the tables with the measures, dimensions and fields. PowerBi is a big step up from pivot tables, but Alteryx would be so much better. Ideas for connecting this up are are welcome!

Extend the MongoDB tool to work with Atlas MongoDB instances.

It would be really nice to be able to easily trace a selected field through a workflow (see below, trace in green). This would greatly help with troubleshooting.

I would really love to have a tool "Dynamic change type" or "Dynamic re-type" which is used just as "Dynamic Rename".

• "Take Type from First Row of Data": By definition, all columns are of a string type initially. Sets the type of the column according to the string in the first row of data.
  

  Col 1	Col 2	Col 3	Col 4
  Double	Int32	V_String	Date
  123.456	17	Hello	2023-10-30
  3.4e17	123	Bye	2024-01-01

• "Take Type from Right Input Metadata": Changes the types of the left input table to the ones by right input.
• "Take Type from Right Input Rows": Changes the types based on a table with columns "Name" and "New Type".
  

  Name	New Type
  Col 1	Double
  Col 2	Int32
  Col 3	V_String
  Col 4	Date

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

I propose another wildcard, %ErrorLog%, that would simply output the error codes and narratives instead of having to use the %OutputLog% to see these.  I'd rather not have a 4 MB text email depicting every line of code and action in the module when all I really need to see are the errors.

Hello,

More and more databases have complex data types such as array, struct or map. This would be nice if we could use it on Alteryx as input, as internal and as output, with calculations available on it.

https://cwiki.apache.org/confluence/display/hive/languagemanual+types#LanguageManualTypes-ComplexTyp...

Best regards,

Simon

I rarely use the Group By tab on batch macros, but it's unfortunately always the first tab that pops up. When I have a questions tab on a batch macro, it would be great if it appeared first (ie I should see the questions tab when I click on my batch macro.) Thanks!

We see canvasses every day where dozens fields are brought into a canvas or a macro, but never used - and this just creates slowness for no good benefit.

Given that one of the selling features of Alteryx is the speed of processing  - could we look at three improvements to the Alteryx engine & designer:

• easiest: Keep track of every field brought in / created - and if they are not used in an output, then throw a warning at the end of the execution process
  • For example - you bring in fields a,b,c - you create field d and e during the flow in formula tools
  • Field d is never used as an input to any filters or formulae - and it doesn't appear on any output - so it's just waste
  • Field a and b are part of the output, so they are fine
  • Field c is never used at all - so that's just waste.
  • Field e is used to filter the records before output - so this one is fine.
  • So we've immediately found 2 fields that we can eliminate and make this canvas faster
• Medium: Ignore the unused fields in the execution engine
• Hardest: Tell the users that their field is unused in Alteryx Designer by doing a lineage analysis of the tools, just like software environments like Visual Studio do.    This may require a change to the engine & to designer 'cause we would need to make each tool capture the full detail of the fields that they know in their configuration in order to do this trace.