Be sure to review our Idea Submission Guidelines for more information!
Submission GuidelinesHello,
After used the new "Image Recognition Tool" a few days, I think you could improve it :
> by adding the dimensional constraints in front of each of the pre-trained models,
> by adding a true tool to divide the training data correctly (in order to have an equivalent number of images for each of the labels)
> at least, allow the tool to use black & white images (I wanted to test it on the MNIST, but the tool tells me that it necessarily needs RGB images) ?
Question : do you in the future allow the user to choose between CPU or GPU usage ?
In any case, thank you again for this new tool, it is certainly perfectible, but very simple to use, and I sincerely think that it will allow a greater number of people to understand the many use cases made possible thanks to image recognition.
Thank you again
Kévin VANCAPPEL (France ;-))
Thank you again.
Kévin VANCAPPEL
As I previously mentioned here, I think that CReW (Alteryx) Runner could hugely benefit from additional enhancements and documentation that would be made for it, especially by adapting certain functionalities found in AlteryxEngineCmd.exe to AlteryxRunner.exe.
Enhancements
Encoding
As you might have already noticed while using the Alteryx Runner (also documented in this page), the AlteryxRunner.exe executable that is being used by Alteryx Runner does not produce the log file in UTF-16 (default Alteryx log output encoding) or UTF-8 encoding.
Therefore, if there exists a tool in your workflow that could produce a message that includes characters that are not supported by the limited Latin code pages (not including Extended Latin) or only supported by UTF-8 / UTF-16 code pages (same applies to workflow/analytic app name, input file names, output file names and directory names), you will notice that the output log is cut off exactly at that character, even if you use an installer such as this, which modifies the input read options of the Read Results section in the Run Command tool in the macro to read the log file produced by the AlteryxRunner.exe in a UTF-8 encoding.
This limits the way in which users can name their files, directories and workflow names, produce custom messages, or render the Runner tool unusable in certain languages.
As the output encoding settings are directly stored in the AlteryxRunner executable, this is unfortunately not an option that can be changed by the end user and requires direct modification to the AlteryxRunner.exe executable file directly from Alteryx development team.
While not being sure if AlteryxRunner.exe is capable of executing workflows or analytic apps that contain characters in their names or their directory names only supported by Extended Latin / UTF-8 / UTF-16 code pages, I would expect that support to be also added in case it's not already there.
Parameters (Command Line Arguments)
- While trying to find if AlteryxRunner.exe supports any command line arguments, I noticed that it is not possible to run an analytic app with custom values (or even if there is, there's no documentation for it, something I have written about below) via AlteryxRunner.exe, so it would be great to be able to run a YXWZ file with custom values (either using an XML file generated while the workflow is running or a "raw xml data stream with no quotation marks or line feeds" provided in the Runner tool as a new option (a text box for XML File Full Path and another one for Raw XML Data Stream toggled by two radio buttons in a check box group named This workflow is an analytic app) added to the interface of the Runner tool in addition to the workflow full path, already included as a text box interface tool). This would save the users from having to generate an analytic app from a template analytic app (at least in some cases where no advanced modifications to the workflow XML would be necessary) just to be able to change the app values stored in the app.
As already specified in the Encoding section above, I would also expect (at least) the XML file (even if not Raw XML Data Stream) to be able to be read in using UTF-8 encoding.
- I think that users should also be able to specify whether to run a workflow or analytic app using E1 or AMP (overriding the workflow settings), just like in the executable AlteryxEngineCmd.exe. In addition to this, if the AMP flag is passed, there should also be an option (or a 3rd option in addition to E1 and AMP) to pass an Engine Compatibility Mode flag.
- As a final addition, I believe it should also be possible to optionally specify the Memory Limit if desired using an additional flag.
I also think that the two last features should also be added to AlteryxEngineCmd.exe, which could benefit from additional enhancements including but not limited to these suggested in this idea post.
Documentation
Parameters
As you might have noticed while reading the two documentations Run Workflows by Command Line and Runner Tool, while there is an advanced documentation on the use of AlteryxEngineCmd.exe, only the use of the Runner Tool itself is documented and not AlteryxRunner.exe. Some of the enhancement requests here are directly a result of this situation (these features could already exist in AlteryxRunner.exe but we would not be aware of it if these were not documented). While such a documentation would not be needed by the Alteryx Designer users (as those arguments could be passed by the choices users make in the macro interface), it might help better understand the capabilities of the executable that makes it possible for a macro such as Alteryx Runner to exist in the first place.
Would be nice to have a way to cache-uncache all inputs or a selected group of tools. Caching and Uncaching workflows with many input tools or slow data-read tools gets to be a bit cumbersome. Would be a nice QoL improvement :)
I looked around for something like this but didn't see a solution, so thought I'd recommend. Please let me know if something like this exists already natively in designer desktop.
I want a feature to enable join by custom conditions. Currently, in Join tool, allowed condition is only equality of specific fields and specific position, however, in SQL, we can join data by much more flexible conditions like;
SELECT TableA.id FROM TableA INNER JOIN TableB ON TableA.id=TableB.id and TableA.value > TableB.value
Of course, my idea can be easily realized by using combination of Appendix Field + Filter tool, but I meant to say is that Appendix-Fields is quite expensive operation in calculation cost, and it would generate many unnecessary records, which is annoying us in case of handling a huge dataset.
I suppose this kind of flexible conditions can be specified by using expression editor, thereby configuration window of this feature would look like the below image; Adding one more radio button option, and expression editor similar to one used in Filter tool.
Any positive/negative feedback on my idea would be appreciated. Thank you for your attention!
If you cancel a workflow while its writing into a file, the file creation will not be rollbacked and hence a partial file would have been created.
This is problematic when working with incremental load relying on file from the past.
Problem: In certain workflows, it becomes necessary to arrange columns in a specific order for the output. While achieving the desired order for a fixed number of columns is feasible using the select tool, difficulties arise when dealing with dynamic outputs that introduce new columns during each workflow run.
Example: Consider the following scenario: the INPUT data for the select tool includes a set of Question/Answer columns. However, with every run of the workflow, new columns of this type are introduced. The challenge is to ensure that Question N and Answer N columns are grouped together in the OUTPUT dynamically. Unfortunately, this task is not easily accomplished using the current capabilities of Alteryx.
INPUT:
Company | Question 1 | Question 2 | Question 3 | Answer 1 | Answer 2 | Answer 3 |
Contoso | Blah | Bleh | Bly | N | Y | N |
DESIRED OUTPUT:
Company | Question 1 | Answer 1 | Question 2 | Answer 2 | Question 3 | Answer 3 |
Contoso | Blah | N | Bleh | Y | Bly | N |
With Python/Pandas, this problem can be easily resolved by assigning index values to each column and then sorting the columns based on the assigned index:
So, based on the Python solution, if Alteryx could do the same, it would be great. I personally think that if the Dynamic Rename tool could held the Index Info, and the select tool could also held the Sort option, this would work.
Dynamic Rename: Already can hold Description info, could hold Index Info.
Select tool: Could sort by index and hold this info when the workflow is saved.
Hope this all make sense.
Thanks.
hi team,
Currently the join tool doesn't have option to join the data irrespective of its case sensitivity. this causes issues while doing the analysis.
This tool is widely being taking as a replacement of Excel Vlookup formula (which is also case insensitive),so can we have the similar functionality for Join tool also?
We can have an option like a radio button or checkbox to select if we want to have case insensitivity while joining.
Thanks
Hello All,
I'm using the dynamic input tool for SQL requests in my Workflow (WF).
I'm using the "Replace a Specific String" to replace elements in the SQL statement dynamically depeding on results of prevoius tools, user input etc.
So the statement looks like
select * from Schema_Name_xx where invoice_number = 'invoice_number_xx'
Since Schema_Name_xx is no valid Schema in the Database, the statement (= Validation) won't work. Only if I replace Schema_Name_xx by e.g. Invoice_Data_Current it will work, same with the invoice number, invoice_number_xx is replaced by e.g. 4711.
Therefore, validation makes no sense and will never work, only if the WF is running, the correct Schema is inserted in the SQL statement by the "Replace a Specific String" function.
It would be great to disable it in the users settings or wherever in the Designer, changing a config file would also be great :-)
Pls. note: I'm thinking (since I'm not allowed anyway ;-)) about changing/disabeling anything in the Alteryx Server settings.
Reason:
1. Speed: Validating a WF with SQL statements that don't work takes time (every time I save it), sometimes I get even a timeout...
2. WF error entries: Each upload with a failed validation creates an entry in the WF result list which makes it harder to seperate them from the "real" WF errors...
Thanks & Best Regards,
Thomas
In some cases, the information about incoming columns to tools are (temporarily) forgotten, e.g. if Autoconfig is switched off, if the incoming connection is temporarily missing, or if column names are generated dynamically and the workflow has not been executed, yet.
Many tools deal with that situation well, e.g. Selection, Formula, or Summarize. In these cases, the tools tell the user that they cannot find incoming columns, but they preserve the configuration so that the user still can (at least partially) work on these tools and important information on the configuration is not lost:
Example Select Tool
Other tools behave the opposite, for example Unique or Macro Input (an for sure many other tools). If the incoming columns are currently unknown to the Designer and you click once on the symbol, the entire configuration of this tool is lost. You might try to get the configuration back by pressing undo. This, in most cases does not work. Or, even worse, you find out what happened later when it's too late for undo. In this case, you either have an old version of that workflow to look up the configuration or you have to re-develop it. In any case, this is unnecessary and time-consuming software behaviour.
Example Unique Tool
I wasn't sure whether I should report this as a bug or a feature enhancement. It is somehow in between. Two aspects tell me that this should be changed:
Please make sure that all tools preserve their configuration also if information on incoming columns is temporarily lost.
Containers are a great feature. They allow us to create larger workflows in smaller canvases, and manage the flow and appearance of our work. However the design whether intentional or flawed that allows the container window to interact with the layers behind it is annoying. Connection wires should not redirect within a container because of things on the canvas behind the container. Likewise if I have a container open, I should not be able to grab a tool or container behind the open container through the container canvas. Please fix this flaw.
Alteryx gods,
It would make me even happier than I am now if it were possible to tailor the completion messaging in the Interface Designer when an analytic app completes.
Currently, we use rendering etc, but sometimes we simply want to be able to create a bespoke completion message.
My example is as follows:
In the app you have the option to download files, or have them emailed to you. If you choose download, the final display is the render tool with the documents listed, however, if you choose email I want nothing to show but the final window with the message "Please check your email" or something. There may be more than one option, and so being able to dynamically change these messages would be very useful.
Help me Alteryx gods, you're my only hope.
*beep boop boop*
I am trying to add additional functionality to my existing workflow.
We have a common workflow pushed to the Alteryx server and there will be multiple people running this workflow.
Every time the workflow is run, the expectation is that an automatic email should be sent to the person who has triggered it(and won't be sent to multiple other people).
Currently, we have it set up using the Email tool but I do not see an option to dynamically update this “To” field to automatically use the email of a person running the workflow on the server.
As mentioned in detail here, I think that the addition of a "run as metadata" feature could be very helpful for making the analytic apps more dynamic in addition to enabling the dynamic configuration of the tools included in analytic apps chained together in a single workflow using control containers, therefore mostly eliminating the need to chain multiple YXWZ files together to be able to utilize the previous analytic app's output (this of course doesn't include the cases where a complex WF/App would have to be built by the previous app in chain to switch to it, but Runner helps solve this issue to a certain extent provided you don't have to provide any parameters/values to the generated WF/App).
The addition of this feature would be somewhat similar to running an app with its outputs disabled, without having to run the entire app itself, but rather only certain parts specified by the user in a limited manner. Clicking the Refresh Metadata button (which will be active only if there is at least one metadata tool in the workflow) will update the data seen in the app interface (such as Drop Down lists, List Boxes etc.), provided the user selected the up-to-date input file(s) (or the data in a database is up-to-date) where the data will be obtained from.
To explain in detail with a use case, suppose you have two flows added to separate Control Containers where the second CC uses the field info of a file used in the first CC to enable the user to select a field from a drop down list to apply a formula (such as parsing a text using RegEx) for example. After specifying the necessary branch in the first CC where the field info is obtained, the user could select these tools and then Right Click => Convert to Metadata Tool to select which tools will run when the user clicks on the Refresh Metadata button. The metadata tools could of course be specified across the entirety of the workflow (multiple Control Containers) to update the metadata for all Control Containers and therefore all tabs of a "concatenated app", where multiple apps are contained in a single workflow.
With this feature, all tools that are configured as metadata tools (excluding the tools that have no configuration) will be able to be configured as a "metadata only" tool or a "hybrid" tool, meaning a hybrid tool will be able to be configured separately for its both behaviours (being able to change all configurations for a tool without any restrictions in each mode, MetaInfo would dynamically update while refreshing metadata). Metadata only configuration of a tool could be left the same as the workflow only configuration if desired.
For example an Input File marked as a hybrid tool could be configured to read all records for its workflow tool mode and only 1 record for its metadata tool mode. This could be made possible with the addition of a new tab named Metadata Tool Configuration in addition to the already existing Configuration tab, and a MDToolConfig XML tree could be added to reflect these configurations to the XML of the tool in question, separate from the Configuration XML tree, and either one of those XML trees or both of them would be present depending on the nature of the tool chosen by the user (workflow tool, metadata tool or hybrid).
This would also mean that all the metadata tool configurations of a tool could optionally be updated using Interface tools. You could for example either update the input file to be read for both the workflow tool mode and metadata mode of an input tool at once, or specify separate input files using different interface tools. As another example, the amount of records to be read by a Sample tool could be specified by a Numeric Up/Down tool but the metadata tool configuration could be left as First 1 rows, without being able to change it from the App Interface.
Hybrid tool (note how Configuration and MDToolConfig has different RecordLimit settings):
<Node ToolID="1">
<GuiSettings Plugin="AlteryxBasePluginsGui.DbFileInput.DbFileInput">
<Position x="102" y="258" />
</GuiSettings>
<Properties>
<Configuration>
<Passwords />
<File OutputFileName="" RecordLimit="" SearchSubDirs="False" FileFormat="25">C:\Users\PC\Desktop\SampleFile.xlsx|||`Sheet1$`</File>
<FormatSpecificOptions>
<FirstRowData>False</FirstRowData>
<ImportLine>1</ImportLine>
</FormatSpecificOptions>
</Configuration>
<MDToolConfig>
<Passwords />
<File OutputFileName="" RecordLimit="1" SearchSubDirs="False" FileFormat="25">C:\Users\PC\Desktop\SampleFile.xlsx|||`Sheet1$`</File>
<FormatSpecificOptions>
<FirstRowData>False</FirstRowData>
<ImportLine>1</ImportLine>
</FormatSpecificOptions>
</MDToolConfig>
<Annotation DisplayMode="0">
<Name />
<DefaultAnnotationText>SampleFile.xlsx
Query=`Sheet1$`</DefaultAnnotationText>
<Left value="False" />
</Annotation>
<Dependencies>
<Implicit />
</Dependencies>
<MetaInfo connection="Output">
<RecordInfo />
</MetaInfo>
</Properties>
<EngineSettings EngineDll="AlteryxBasePluginsEngine.dll" EngineDllEntryPoint="AlteryxDbFileInput" />
</Node>
Please also note that this idea differs from another idea I posted (link above) named Dynamic Tool Configuration Change While the Workflow is Running in that the configuration is updated while the WF/App is actually running and for example the Text to Columns tool in the second CC is dynamically changed using the output of a tool in the first CC, unlike selecting an input file and clicking Refresh Metadata from the App Interface before the workflow is run.
Attached is a screenshot and an analytic app to better demonstrate the idea.
Thanks for reading.
Hello, I believe this feature will be useful for many people.
The idea is to select multiple instances of the same tool and the configuration that we set will be applied to all the selected tools. Furthermore, it will be useful to be an easy way to select all instances of the same tool across a workflow with a shortcut in order to edit them more easily.
I would like a new format option within the Designer function DateTimeFormat such that where a date is held in the database
e.g. 2023-01-01
DateTimeFormat([date],%o)
will return 1st not 1 or 01.
Workarounds exist, but are fiddly given the different options....1st, 2nd, 3rd, 4th.....
Not sure if API/SDK is the appropriate portion of the product that this enhancement would pertain to, but I thought that it was the most fitting option available.
I understand this is a long shot and would probably never happen, but I think it would be super cool if Alteryx had tools for blockchain development and web3 interaction.
The blockchain space is a complicated space, and every blockchain is a little bit different. So I am not sure exactly sure what this would even look like. But I imagine tools like connect wallet, query events, write transactions or other common blockchain actions.
I think as the blockchain space continues to grow, there is going to be an continued increase in interest in developing blockchain applications including companies that want to use blockchain.
With the state the blockchain industry is in at the moment, I am sure most people reading this would think its crazy, but if the blockchain industry does prevail in the long term, which I think it will, this could definitely be something to keep on the radar.
Think big!
I am suggesting an addition to the Auto Field Tool. Create an option that allows only auto sizing of the fields and does not change the field type. A check box that says Auto Size Only. The tool would recognize any fields that can be resized based on their incoming data field type and will not change the data type. The resizing function is very helpful to maximize workflow performance, but I currently do not use it much because it guesses wrong on the data types. This causes problems also when data inputs change. Whereas setting to auto size only, it can streamline the data but let the user be confident the data types would not change.
Thank You
I have tried to search for this Idea but not located one that is same or similar.
When searching for tools to use rather than having to click in the search bar at the top, it would be nice just to click on a blank part of the canvas and start typing for the tool that you need, then a suggest tool list pops up and you just click on the one you want to it appear.
Thanks
To embed the "Not ok" filter option in the browse tool
As of version 2023.1 once a workflow is locked, it cannot be unlocked. If Alteryx can unlock it, can it be made into a user option?
My idea has two parts. See the images for examples.
1. Add an option on the lock screen so the user can get an unlock passkey.
Passkey is either generated by Alteryx or set by user
2. Change the behavior when trying to open a locked file by giving the user an option to enter the unlock passkey.
Same behavior if there is no passkey
Dialog box with passkey input and cancel button if a passkey exists
This would be useful as a way to revise or edit a workflow or update the expiration date on the existing workflow without having to reload or resave a new file.
Looking for a tool to replicate the Goal seek functionality built into Excel.
Seems it could be solved by using R or iterative macros however a tool would make life much easier,