Alteryx Designer Desktop Ideas

Hi there,

 

We often get the following error message from the download tool 

"00:00:23.555 - Error - ToolId 106: Error in libCURL: You have found a bug.  Replicate, then let us know.  We shall fix it soon."

 

Unfortunately this seems to be a transient error so we've not been able to replicate this in a useful & repeatable way.  However - we see this happening at least a few times per week on one of our servers, so this is a continuing issue.

 

Please could you provide more detailed error messaging on the download tool so that this error can be debugged and/or replicated?

 

Many thanks

Sean

TIBCO Data Virtualization is a Data Virtualization product focused on creating a virtual data store consolidating data from throughout the enterprise.  It can be accessed via a SQL query engine, and has a variety of supported connectors, including an ODBC driver.

 

This data source can be connected to via ODBC in Alteryx today, but error messaging is unclear/unhelpful, and attempting to use the Visual Query Builder causes Alteryx to crash.

 

Adding TIBCO Data Virtualization as a supported ODBC connection would empower business users to leverage this product and easily utilize this enterprise data store, enhancing the value of the Alteryx platform as a consumer of this data.

The Multi-Field formula tool has three really powerful features that it supports:

[_CurrentField_]

[_CurrentFieldName_]

[_CurrentFieldType_]

 

These are really powerful within Multi-Field formulas because they allow for a dynamic process to apply across multiple fields.

 

However, they would also be very helpful in regular formulas and Multi-Row formulas, for code transportability.

 

A basic example:  I have a Longitude field that is a string.  I need to set it to a value of 0 if there is a null value.

 

My formula today:

IF ISNULL([Longitude]) THEN 0 ELSE [Longitude] ENDIF

 

Now lets say I want to use the same formula somewhere else, but for Latitude instead.

 

 That formula looks like:

IF ISNULL([Latitude]) THEN 0 ELSE [Latitude] ENDIF

 

If I could use [_CurrentField_] instead, that would allow me to instead write both formulas as:

 

IF ISNULL([_CurrentField_]) THEN 0 ELSE [_CurrentField_] ENDIF

 

This code can easily be copied for any field that requires replacing Nulls with 0s, and doesn't require refactoring to use a Multi-Field formula instead.

 

This also means that if I later change my field name, the code will remain consistent.  This not only speeds up development time and flexibility, but more readily allows for validation that the existing code has not changed.

Currently - in order to run a series of Alteryx processes which have start-finish dependancies, you have to hack this by putting each sub-process into batch macros with fake inbound and outbound controls and a fake control parameter.   Additionally, alteryx forgets the mapping of parameters if you move stuff around, and you have to re-link it all up again, running each step 1 by 1 until the next one fails.

 

some may say "just use Block until done"

- this only partially solves the issue if your dependency chain is one deep (e.g. create the table; and then send a summary of errors found in the table)

- this doesn't create any ability to encapsulate flows to create simplicity - so it drives the user towards having increasingly bigger and more complex canvases

 

If we could create a new macro-type or container-type which just allows start-to-finish dependency chaining like a sub-procedure, and which just passes on what was in the input stream directly to the output stream - this would materially improve the ability to simplify flows; and at the same time it's a cheap and easy way to allow for detailed dependency and flow control.

 

Happy to talk through this live with the team if that makes sense?

 

Thank you

Sean

 

In the Gallery, the File Browse tool returns the file location on the server where the file was uploaded. This allows the file to then be read in as input to a workflow.

If you need the file path of the original file location, you have to add a Text Input for the user to manually add it.

 

In my case (#00293302), I used a chained app to populate a list box for the user to select the Sheet Names they would like to process through the application. Unfortunately, since I was not able to capture the original file location the application errored out. This is due to the second app using the file location on the server where the file was uploaded, which is provided by the first workflow. This file location (from the Browse tool) is a temporary file location, where inputs are immediately deleted after processing.

 

Want to test this out? Create an application where you Output the file path from a File Browse tool.

 

i know.....grrr, this doesn't match your original file location!

 

Thank you,

Mark

Hi,

     I would like to see Global Variable being made available in Alteryx. I have seen the Global Constant being made available under Workflow "User" configuration. But this is constant and needs to be defined at Design time.

How about a Process Id that needs to be auto genearted and the same needs to be available across the formula tools used with in the workflow.

With the continued growth of Graph Databases, it would be nice for Alteryx to creates a new tool set that would allow input/output connectors for Graph Databases like Neo4j which software tools like Pentaho and Talend already have.

 

Keith. 

It would be great if we users could have the ability, ideally in a simple interface (maybe workflow option) to create .yxi macro installers. This would allow us to create and really simple, quick and straightforward way on installing macros in Alteryx rather than having to copy into certain directories or add through the user settings.

 

I know we can edit the XML on @AdamR_AYX CREW Macro installers etc. but this would make it really simple for single macros.

 

I'm assume this might already be on the road map, but will be useful to discuss.

 

YXI Files Intro Blog: https://community.alteryx.com/t5/Engine-Works-Blog/YXI-Files-in-Alteryx-10-5/ba-p/20773

 

Discussed briefly on Twitter by @Joe_Lipski, @chris_love @jdunkerley79 @danielbrun2 but probably better to bring the discussion here: https://twitter.com/Joe_Lipski/status/811907135516852224

I utilize the Workflow Events quite a bit, but the standard options fall short in a few critical cases.

 

For example: I use the events to send me an email after the workflow runs with errors.

Usually that is all I need.  But, I have run into a few situations where the workflow didn't run at all - thus, no email was sent.

 

One such instance was on our server.  While still initializing (before it even hit tool #1) the job hung.  It sat like that for over a day before I noticed that there were no jobs running through a particular worker at all and saw this one sitting there. 

A second such instance was recently when I changed Persistence Options and accidentally deleted the source for a scheduled job.  The workflow marked itself complete in the scheduler and gave an error message of "Corrupt: Internal Error in PersistenceContainer......"

I realize that these are unexpected events and application errors (which I've worked with support on); but it would add great value to have that fallback mechanism to let us know the error happened.

 

Understandably, it would probably take a lot of work to engineer a schedule monitor that would catch this - but I think it would be worthwhile.

One option to do this: have an Event to email or run a command if a workflow hasn't started within a certain grace period after its scheduled time.

 

 

Could Alteryx create a solution or work around for their tools to retry the queries with Azure DB connectivity outages.

If there are intermittent, transient (short-lived) connection outages with cloud Azure DB, then what action can we take with Alteryx to retry the queries.

Examples of retry Azure SQL logic:

https://docs.microsoft.com/en-us/azure/sql-database/sql-database-troubleshoot-common-connection-issu...

“2. Applications that connect to a cloud service such as Azure SQL Database should expect periodic reconfiguration events and implement retry logic to handle these errors instead of surfacing these as application errors to users”.

SQL retry logic is a feature that is not currently supported by Alteryx.

 

For further information please see [ ref:_00DE0JJZ4._5004412Star:ref ]:

 

Hi Alteryx Support,

 

We are experiencing intermittent errors with our Alteryx workflows connecting to our Azure production database with Alteryx Designer v2018.4.3.54046.

 

Is there anything we can do to avoid or work around these intermittent / transient (short-lived) connection errors, such as, changing the execution timing or the SQL driver settings.

 

Or can we incorporate examples of retry Azure SQL logic:

https://docs.microsoft.com/en-us/azure/sql-database/sql-database-troubleshoot-common-connection-issu...

“2. Applications that connect to a cloud service such as Azure SQL Database should expect periodic reconfiguration events and implement retry logic to handle these errors instead of surfacing these as application errors to users”.

 

https://docs.microsoft.com/en-us/azure/sql-database/sql-database-develop-error-messages

https://docs.microsoft.com/en-us/azure/sql-database/sql-database-connectivity-issues

 

 

Salesforce Import process, which contains 25 Workflow modules, completed with errors on:

Mon 25/02/2019 23:27

 

Error 1

2019-02-25 23:11:23:

2.1.18_SF_MailJobDocument_Import.yxmd:

Tool #245: Error opening connect string: Microsoft OLE DB Provider for SQL Server: Login timeout expired\HYT00 = 0; Microsoft OLE DB Provider for SQL Server: Invalid connection string attribute\01S00 = 0.

 

Error 2:

2019-02-25 23:26:31:

2.1.25_SF_ClientActivityParticipant_Import.yxmd:

Tool #258: Error opening connect string: Microsoft OLE DB Provider for SQL Server: Login timeout expired\HYT00 = 0; Microsoft OLE DB Provider for SQL Server: Invalid connection string attribute\01S00 = 0.

 

 

Salesforce Import Workflow completed with errors on:

Wed 27/02/2019 23:24

 

Error 3

2019-02-27 23:06:47:

2.1.17_SF_MailJobs_Import.yxmd:

DataWrap2ODBC::SendBatch: [Microsoft][SQL Server Native Client 11.0]TCP Provider: The specified network name is no longer available.

 

 

Regards,

Nigel

Hi,

 

With multiple Workflows open, I'd like to be able to grab one of the Workflow tabs and drag it out on to the desktop.  This act would then cause a new Alteryx Window to open up with the Workflow that was pulled out.  Just like when you have multiple tabs open in I.E. and you drag a tab out and drop it on the desktop - you end up getting another I.E. opened up and the tab you dragged out is in the newly opened I.E.

 

This would be handy because I'm often wanting to copy/paste tools, formulas, etc. and it would be nice to do that w/o flipping from one tab to another.

 

I know I can right-click and open another Alteryx but when opening several - they all open in the same one.

 

Thanks,

 

Brad

While challenge 41 was fun to calculate weekdays between 2 dates, there should be a formula similar to networkdays in excel to do the same function

I've come across multiple requests for help that relate to dates.  Having to know that "2016-05-04" is the only way to get May 4th, 2016 into a date field is sometimes a challenge for new users.  When they begin to use date functions and now have to learn adding and trimming etcetera the complication factor increases.  Then we date time format and have to do all of this in English (my one and only language), makes me think that there is room for improvements.

Idea:   I think the Interface Designer's "Test View" window should allow control parameters to act like "Text Boxes" and allow the designer to manually edit, or type a control parameter for use in a debug module.
 
When designing batch macros, there currently is not an easy, built-in way to test or debug their functionality.  There are two reasons to build a batch macro:
1) to reconfigure the macro at run time, just as if they were the answers to questions in the macro GUI;
2) to group the records going in the macro inputs into batches.
If I am designing a macro to perform the 1st function -- reconfigure the macro at run time -- I need to be able to test its functionality in a debug module.
 
The Interface Designer's "Test view" window should provide this ability by allowing you to type an example control parameter value.  However, the Test View window only allows you to "dropdown" to a value via a dropdown box.  This dropdown box is always empty, thus never allowing you to enter a test control parameter.  I think the Interface Designer's "Test View" window should allow control parameters to act like "Text Boxes" and allow the designer to manually edit a control parameter for a debug module.
 
I've attached a screenshot of a simple, two control parameter batch macro.  As you can see, in the Interface Designer, I don't have a way of inputting a value in either control parameter field to open a debug module.
 
 

 

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

One of the most common causes for Admin trauma for our central Alteryx Gallery team - is dealing with drivers that may not be on the server; or a particular worker; or on a designer.

 

What we're looking for, is for the Alteryx team to maintain a packaged set of drivers as a single installer - which we can download at the same location as the Alteryx designer / server versions.

 

This would allow us to have 1 version of all drivers across ALL designer clients; as well as on our workers and servers.

 

CC: @rijuthav @jithinmony @HengHe @RajK @ydmuley @revathi @Deeksha @MPistone @Ari_Fuller @Arianna_Fuller @JoshKushner @samnelson @avinashbonu @Sunder_Sriram @Rahul_Thakur @Rahul_Singh

While Alteryx does have a UNION set operator, it only currently has an Inclusive Union

 

the other two set operators, Intersect & Except, and an exclusive Union would be helpful if they can be added.

• Exclusive Union: Union two sets, but eliminate full duplicates (across the full row)
  • Although this can be done with a union, followed by a distinct - you have to do a distinct across all columns
  • This is the difference between SQL "Union" and SQL "Union ALL"
• Intersect:  This is the intersection of two sets - where the full row (all columns) are identical
• Except: This is where the row in 1 set is not in the other.

 

Intersect is particularly helpful for operations like looking at multi-column reference data to see if any fields at all have changed (like a slowly changing dimension).

 

CC: @rijuthav @jithinmony @HengHe @RajK @ydmuley @revathi @Deeksha @MPistone @Ari_Fuller @Arianna_Fuller @JoshKushner @samnelson @avinashbonu @Sunder_Sriram @Rahul_Thakur @Rahul_Singh

When building an Alteryx Macro - one of the tough parts is that the input data you put into the Macro Input is used for testing, but you cannot set the type.

 

So for example - I want to test with the value 1, and Alteryx automatically assumes this is a Byte.

However 1 is just a useful test value, but I need this to be an int 64.

 

Can we provide the option to strongly type the macro inputs - this way, we can give advanced users the ability to control the type on Macro Inputs, and not run into this sort of issue with test data implicitly defining the type?

 

Note: this is similar to the idea here:

https://community.alteryx.com/t5/Alteryx-Product-Ideas/Set-data-type-in-Text-Input-tool/idc-p/115209...