This site uses different types of cookies, including analytics and functional cookies (its own and from other sites). To change your cookie settings or find out more, click here. If you continue browsing our website, you accept these cookies.
The #bandofsolvers community has come up with many creative ways to determine if an 'output' action is complete before proceeding with next steps. However, what we really need is an optional output anchor added to (all?) tools in this class.
For example, currently if we need to Output Data to the same file 3 times, we have to put logic in place to make sure that the 3 updates happen in the correct sequence and do not interfere with each other. Or if we need to Render a file and perform additional modifications or file actions on that new file (e.g. ACL using icacls), we have to put checks in place to wait for the render to complete and make sure the file is freed by the write step.
However, if we could have at minimum an optional output anchor pass a Boolean flag indicating the 'output' class tool is complete, that would help tremendously! Even more helpful would be a xml/json object containing the tool configuration. Additionally, data/metadata 'pass-through' could be helpful in some situations as well.
I understand that this simple request could be significant change to the structure of the program, but throwing it out there for the 'Idea' space! 🙂
As well as using keyboard shortcuts, many of us are using a mouse / keyboard with program specific assignable shortcut buttons. It is a serious boost to productivity. The ability to instantly enable / disable would be a great tool large complex workflows. In general, it would be great to expand the keyboard shortcuts to offer more Alteryx specific advanced functions.
Add a new feature to develop your own customized decision tree with Insight. So instead of using a tree generated with the Decision Tree tool a user can generate a tree with custom splits and save the splitting rules as a model to score later a new dataset. This will provide user the ability to enhace a tree with business knowledge.
The add to / remove from container behavior needs to be modified. I have frequently had the application completely rearrange my workflow because of it. I was just deleting a handful of closed containers when the application removed all my tools from their individual containers and wrapped everything in one big container completely screwing up my entire workflow. This happens a lot. Now I have to reorganize the workflow. This is one of my biggest frustrations with the application.
It would be very useful for me If I could consolidate in the same output two different inputs: 1- the whole output flow; 2- The summarize from the output. That would save some time from doing pivot table analysis for instance.
It will be great to make visibility of workflow execution results to other users in same subscription.
As of now, only schedules are visible to all users in a subscription, but not the workflow execution results executed by a user to other users in same subscription.
This will avoid duplicate execution of same workflow by multiple user in a team as it will provide option to cross check the execution results by other users, if executed already, before execution of same workflow.
I appreciate being able to write to an ESRI File GeoDatabase. It would be even better if in the process of writing to an ESRI File GeoDatabase I could identify fields to index and have them indexed when writing to the File GeoDatabse. Currently I have to add the index in ArcGIS after the fact. Writing to an ESRI File GeoDatabase currently adds a spatial index automatically, but I'm talking about an attribute index here.
The drop-down interface tool currently allows you to allow the user to select field names from a connected tool.
However, a very common use case is not currently supported - select VALUES from a connected too (i.e. the values in a specific column).
There are several workarounds (including chaining the app and using an alteryx DB or transposing values into fields) - however given how common this need is, it seems to be valuable to support this directly.
I have been developing and accumulating custom functions over the years and they have proved to be very useful. I am submitting these here. I hope they are found to be beneficial.
Functions included in the attached file include:
StandardDate(String) - Transforms any valid string to the standard date format yyyy-mm-dd
FileDirDepth(Path) - Returns the zero based depth of the path (zero being the root)
FileGetFolder(Path, Depth) - Returns the folder name given the zero based depth in the path (zero being the root)
LeftPart(String, Separator) - Returns the left part of a string up to the first separator
RightPart(String, Separator) - Returns the right part of a string after the first separator
Split(String, Delimiter, Index) - Returns the zero indexed part of a delimited string
CleanSpace(String) - Trims string and replaces multiple spaces with a single space
UnicodeToASCIIBasic(String) - Replaces all Unicode Characters with ASCII Basic equivalents
InList(Variable, List) - If Variable is in List returns True. List must be pipe delimited
IsValidEmail(String) - Returns True if string is a valid email format
IsUUID(String) - Returns True if string is a valid UUID
To make these functions available in Alteryx, place the attached xml file in the folder C:\Program Files\Alteryx\bin\RuntimeData\FormulaAddIn if you have a standard installation. If the install is non-standard, find the \bin\RuntimeData\FormulaAddIn folder and place the attached xml file there. Ateryx will need a restart for the functions to be available.
One of the issues I've recently ran into, and discussed with my Customer Success Manager, is Alteryx's inability to natively connect to Snowflake for In-DB Processing using Snowflake's latest ODBC driver versions.
As noted in the Alteryx Help Page below, Alteryx has only been validated to natively support ODBC driver version 2.13.06.00.
As noted per my Alteryx Community ticket below, the Technology Platform team at my company has informed me that they cannot revert our existing Snowflake driver version (Version 2.17.0) to an older version.
If an organisation wants many Designer users to have the same macros available to them, they have to set up their own network drive to save the macros to and share that drive to all users and ensure each user has read access to it and then maps that drive to their macros.
Instead of relying on this shared drive architecture, macro builders should be able to publish their macros to a collection in Gallery and then end users should be able to map that collection to their Macros in Designer.
It would keep the sharing of macros within the Alteryx platform and make sharing macros much more intuitive and frictionless.
Pretty much every coding framework supports this. If we really want Alteryx to embrace no-code, we've got to have some ability to control commit / rollbacks across transactions. As it stands currently, it is pretty easy to write out parent records, fail to be able to write out children, and wind up with a database state that makes the end users very sad.
Back when I used to do more coding, some of the ORMs had the ability to return back to you a natively generated primary key for new rows created; this could be really useful in situations wherein you wanted / needed to create a parent / child relationship or needed to pass the value back to another process for some reason.
As it stands now, the mechanism to achieve this in Alteryx is kind of clunky; all I have been able to figure out is the following:
1) Block until done 1.
1a) Create parent record. Hopefully it has an identifying characteristic that can be attached to.
2) Block until done 2.
2a) Use a dynamic select to go get the parent record and get the id generated by the database.
3) Block until done 3.
3a) Append your primary key found in 2a. Create your children records.
I mean it works. But it is clunky, not graceful, and does not give you any control over the transaction, though that is kind of a more complicated feature request.