Alteryx Designer Desktop Ideas

The idea is to store credentials, login/pw in a "credential alias".

 

Then, those credential aliases can be used in :

-traditional aliases/connection

-in database aliases/connection

-hdfs aliases/connection

-API

-on user aliases for connected controllers/gallery

...etc.

 

The idea is that I only have to change the credentials once for all the connection type (on Hive, I have the in db alias, the traditional alias and even an HDFS alias using exactly the same credentials !! and I have to change all that manually).

 

When using the transpose and cross tab tools, I find that I frequently need to reorder the columns selected in the "Key Columns" and "Group data by these values" sections of the tools respectively by using a select tool. It would be helpful to provide users with the ability reorder fields displayed in these tools similar to the functionality provided in the select, join, append, summarize tools etc. Currently the tools default to outputting these columns in the order they come in through the incoming data stream. 

 

 

 

@RithiS ,

 

I'm a fan of using DETOUR tools in Alteryx.  I often place "test" code into a standard workflow and opt to use it or not based upon a detour.  The challenge is that adding a detour and detour end invariably leads to having to re-route connectors (default of adding tools is to connect to the left).  Here's a picture:

 

 

What I'd like to do is SELECT the tool or tools that I want to connect around (in this case, just the formula tool).  I'd like to right-click and DETOUR.  The detour and detour end would be added (putting the selected tools in the path of the RIGHT option.  This would greatly speed up the tool configuration process.

 

If you want to go for extra credit, you could modify the GUI to express which direction a detour is travelling in a standard workflow (e.g. make connections wireless or dashed when not selected).

 

Cheers,

 

Mark

 

@Claje @Hollingsworth @SeanAdams 

When creating a workflow I generally open a "TEMPLATE" first and then immediately save it to the "NEW WORKFLOW NAME".  My template includes all my preferences that aren't set naturally within the user settings and won't get RESET by them either.  It has a comment box and containers as well as logos and copyrights.  It would be nice to have ready access to this feature.  Maybe others have standards that they want applied to all users and their workflows too.

 

Thanks,

 

Mark

Hi there Alteryx team,

 

When we load data from raw files into a SQL table - we use this pattern in almost every single loader because the "Update, insert if new" functionality is so slow; it cannot take advantage of SSVB; it does not do deletes; and it doesn't check for changes in the data so your history tables get polluted with updates that are not real updates.

 

This pattern below addresses these concerns as follows:

- You explicitly separate out the inserts by comparing to the current table; and use SSVB on the connection - thereby maximizing the speed

- The ones that don't exist - you delete, and allow the history table to keep the history.

- Finally - the rows that exist in both source and target are checked for data changes and only updated if one or more fields have changed.

 

Given how commonly we have to do this (on almost EVERY data pipe from files into our database) - could we look at making an Incremental Update tool in Alteryx to make this easier?    This is a common functionality in other ETL platforms, and this would be a great addition to Alteryx.

 

 

 

To add the capability to hard rename the columns in all modes 

Would like to be able to reference the UserID of the person running the workflow within the workflow itself, usually for authentication purposes.

 

For example, we use the Publish to Tableau Server tool. The main developer will embed their password in the tool and then publish it to Gallery. We are wanting to authenticate if the person running the workflow on Gallery can actually publish to Tableau Server before publishing, not just the person who published the workflow in the first place. 

 

Another example is that we are needing to upload data to our data lake through APIs and need to pass in user information of who is publishing to that package through Alteryx, and check that they can indeed publish there. 

 

Basically, we need to have logic within the workflow that is referencing who is running the workflow. 

 

We understand that this would most likely only be supported when workflows are run on Gallery, as there isn't a UserID tied to someone when running on a local machine. 

I feel like I must be missing something, but saw a similar suggestion for TDE outputs, so maybe this really doesn't currently exist. We sometimes add descriptions to fields we create, and some inputs come with descriptions, but we can't seem to get them into the final database using the Output tool. Can there be a checkbox to persist the metadata along with the data when writing to a database?

Hi Everyone,

 

Many workflows I work with along with those of my colleagues, use big databases in order to get some data. After a few steps down stream and testing, we normally just add an output and then open up that data in a new workflow to save time running the original workflow. Not that this is much of a burden, but I am used to copying and pasting tools from workflow A to workflow B, but you can't do that with the output, because in workflow B the output needs to be converted to an input. I just think it would be a cool added feature if possible. Anyone else agree?

 

Thank you,

Justin

 

 

As we do more work analyzng the canvasses that our folk are producing - it's becoming more and more necessary to have a well documented definition and schema for the XML that is used for Alteryx Canvasses.

 

Please could you publish the full XML definition and schema for Alteryx canvasses - this will allow groups to perform deeper analytics on how people are using Alteryx, automate quality checks; look for learning gaps; scan for dependencies etc?

 

Note: this relates to an idea from @dataprep here: https://community.alteryx.com/t5/Alteryx-Designer-Ideas/Documentation-tool-list-fileformat/idi-p/184...

 

cc: @revathi @LizaNemchynova @ydmuley

I would like to be able to use the join tool to join on inequalities.  We could join two tables, A and B on A.value is >= B.value1 AND A.value <= B.value2.  This would replicate the "between" function in SQL.  The equvalent feature in Tableau is pictured below.

Originally posted here: https://community.alteryx.com/t5/Data-Sources/Input-Data-Tool-Can-we-control-use-of-Cursors/m-p/5871...

 

Hi there,

 

I've profiled a simple query using SQL Server Profiler (Query: Select * from northwind.dbo.orders; row limit: 107; read Uncommitted: true) and interestingly it opens up a cursor if you connect via ODBC or SQL Native; but not by OleDB - full queries and profile details are on the discussion thread above.

 

However - in some circumstances a cursor is not usable - e.g. https://community.alteryx.com/t5/Data-Sources/Error-SQL-Execute-Cursors-Not-supported-on-Clustered-C... because SQL doesn't allow cursors on columnstore indexed tables & columns

 

Is there any way (even if we need to manually adjust via the XML settings) to ask Alteryx not to create the cursor and execute directly on the server as written?

 

Thank you

Sean

Hi Alteryx User and Alteryx Dev team,

 

I saw there are number of posts from the community asking for solution to calculate the NetWorkDays (e.g. similar to the networkdays in excel which to calculate the number of days different between the two days excluding weekend and holidays.)

 

Although we could build a macro for it, the performance is not ideal, especially when the data set is huge and/or the date range required is far apart from each other because there is currently NO a build-in function in Alteryx.  Alteryx will have to expand the date range by date and check whether each is a weekend or holiday.   It will an excellent idea if a build-in function for Networkdays could be built to minimize this hassle from everyone around the world. 

 

We are looking forward this idea could be take forward.

 

Thanks

Eric

I would like Alteryx to create an internship support program that provides a license similar to a trial but for an extended period, say 6 to 8 weeks, and tied to core certification. you could repackage much of the existing training into a curriculum aimed at educating new users sufficiently on the elements necessary to pass the Core certification within a short time frame.

 

Our organization just launched an internship program and had our first group of interns start 5 weeks ago.  I had to come up with a plan that provided the intern a valuable experience.  I decided to make Alteryx Core certification a key objective and put him on a spare license we had for the duration and worked with him to get his core. 

 

I think this could be a great marketing tool for Alteryx.  It would get more people entering the workforce educated about your product so that no matter where they end up they might already be a fan and suggest the tool as a solution in a new job that doesn’t currently know about you.   Conversely it gives interns a certification that shows they know more than the other applicants for a job where Alteryx is already a tool.  I am sure there are tax benefits to Alteryx as well for each license used.

 

This is kind of how we discovered Alteryx, we had issues with volume of data and technology limitations (Excel) and someone had used Alteryx at a prior company and suggested we try it out.  We purchased a couple licenses, then within a couple years we had 16 licenses.  You can’t sell someone who doesn’t know you exist…the internship type license is a good idea to expand the list of people in the workplace who know you exist.  Even better they will have have reached a level of knowledge, core certification, to have a basic appreciate your value.

 

Hi,

 

This is a small thing but it really messes with my OCD. It would be great if we could manually move the connection lines between tools , this would make large workflows a lot nicer to look at and easier to follow. 

 

I am aware of the wireless tool but i like to see connections, just want them a bit neater.

 

Thanks

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

Hello!
Currently when you share a workflow that contains a Directory tool, it will instantly fail if you do not setup the directory tool to point at a similar folder structure. This is expected, but can make it painful to share workflows between multiple users, especially when a shared network drive and dynamic paths cannot be used. 

 

What I propose as an addition to Alteryx Designer would be the option to 'convert to yxdb' / 'cache and replace' any tools that are at the start of a workflow, similar to the cache and run workflow option:

What i expect this to do is to containerise the tools previously used, and create a new file within a temporary location, and replace the containerised tool connection with a new data input to that file:

 

Why this would be fantastic, is that it would allow me to now export the workflow, including the file that has been created:

and I could then share that with a colleague.

 

Kind Regards,

Owen

 

 

Microsoft Office provides a facility in all its apps to make the loading of frequently used files a breeze. In the FILE OPEN function the user can "PIN" a previously opened file so that it is always easy to find and load.  This would make it easier to manage and retrieve Designer files. 

 

This is what PINNING looks like in Excel