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
This is purely aesthetic but it would be great to have a button to auto format tools positions on the canvas. The idea would be similar to a feature many IDE's come with to auto format code so that the indentation is corrected and duplicate return characters are removed.
We currently have the Align and Distribute capabilities which is great. This could be expanded to the entire workflow so that the canvas could look at which tools connect to which and structure their positioning around that. I think it would be a great clean up feature after finishing a workflow.
If an Output Data tool fails, there are frequently other processes within the workflow that depend on the status (success|failure) of the output. I find myself having to build a macro or some other overengineered method to validate the status of the Output Data tool. Instead, please put an output anchor on the tool. Then, if there's an error, no downstream process will run and this will greatly simplify error handling. Thank you.
It would be very helpful if there was a tool that could stop the workflow without throwing an error. Currently, you can use the message tool to throw an error on a certain condition, and then enable the "Cancel Running Workflow on Error" option in the Runtime settings, but when the workflow is stopped in this way, many other tools don't function such as the Output Data and Email tools. Simply adding a tool that stops the workflow without erroring that also allows the other tools to finish their job would be great.
To enable a check mark kind of option to lock or edit the configuration window of each tool.
It could be very useful to keep safe the settings in the configuration window.
Alteryx Gods,
Following a discussion with a person with whom I spend way too much time, @Jeff_Neklason , we were wondering would it be possible to allow users to drag and drop the position of the actual sections at the top of the designer?
Some users find they use the Developer section more than the Parse section, for example, and it would be beneficial if they could move the Developer section to the left to be more easily accessible.
Thank you Alteryx Gods.
I love you.
Kisses.
xxx
Hello Alteryx Dev Gurus -
We are migrating and some workflows that used to successfully update a datasource are now giving a useless error message, "An unknown error occurred".
Back in my coding days, we could configure the ORM to be highly verbose at database interaction time to the point where you could tell it to give you every sql statement it was trying to execute, and this was extremely useful at debug time. Somewhere down the pipe Alteryx is generating a sql statement to perform an update, so why not have something on the Runtime tab that says, 'Show all SQL statements for Output tools'? Or allow it on an Output tool by Output tool basis? If this was possible by changing a log4j properties file 15 years ago, I'm pretty sure it can be done today.
Thank you for attending my TED talk on how allowing for detailed sql statements to bubble back up to the user would be a useful feature improvement.
To increase Performance on some old Buissness Logic, i am trying to switch an existing system to In-DB tools. This has given me a lot of headache because there is no Multi-Field Formular Tool in the In-DB section. It is a very tedious job to run through every workflow to manually set the same regex for a table with more than 20 Fields.
I have had the idea to implement such a tool myself but i think this could be helpful for other developers in Alteryx Desktop too, so i am bringing this up here.
The Idea is to have a similar approach to the new Multi-Formular Tool like the other already existing Tool in Preperation.
Hello,
A lot of time, when you have a dataset, you want to know if there is a group of fields that works together. That can help to normalize (like de-joining) your data model for dataviz, performance issue or simplify your analysis.
Exemple
order_id item_id label model_id length color amount
1 | 1 | A | 10 | 15 | Blue | 101 |
2 | 1 | A | 10 | 15 | Blue | 101 |
3 | 2 | B | 10 | 15 | Blue | 101 |
4 | 2 | B | 10 | 15 | Blue | 101 |
5 | 2 | B | 10 | 15 | Blue | 101 |
6 | 3 | C | 20 | 25 | Red | 101 |
7 | 3 | C | 20 | 25 | Red | 101 |
8 | 3 | C | 20 | 25 | Red | 101 |
9 | 4 | D | 20 | 25 | Red | 101 |
10 | 4 | D | 20 | 25 | Red | 101 |
11 | 4 | D | 20 | 25 | Red | 101 |
Here, we could split the table in three :
-order
order_id item_id model_id amount
1 | 1 | 10 | 101,2 |
2 | 1 | 10 | 103 |
3 | 2 | 10 | 104,8 |
4 | 2 | 10 | 106,6 |
5 | 2 | 10 | 108,4 |
6 | 3 | 20 | 110,2 |
7 | 3 | 20 | 112 |
8 | 3 | 20 | 113,8 |
9 | 4 | 20 | 115,6 |
10 | 4 | 20 | 117,4 |
11 | 4 | 20 | 119,2 |
-model
model_id length color
10 | 15 | Blue |
20 | 25 | Red |
-item
item_id label
1 | A |
2 | B |
3 | C |
4 | D |
The tool would take :
-a dataframe in entry
-configuration : ability to select fields.
-output : a table with the recap of groups
<style> </style>
field group field remaining fields
1 | item_id | False |
1 | label | False |
2 | model_id | False |
2 | color | False |
3 | order_id | True |
3 | link to group 1 | True |
3 | link to group 2 | True |
3 | amount | True |
Very important : the non-selected fields (like here, amount), are in the result but all in the "remaining" group.
Algo steps:
1/pre-groups : count distinct of each fields. goal : optimization of algo, to avoid to calculate all pairs
fields that has the same count distinct than the number of rows are automatically excluded and sent to the remaining group
fields that have have the same count distinct are set in the same pre-group
2/ for each group, for each pair of fields,
let's do a distinct of value of the pair
like here
item_id label
1 | A |
2 | B |
3 | C |
4 | D |
if in this table, the count distinct of each field is equal to the number of rows, it's a "pair-group"
here, for the model, you will have
-model_id,length
-model_id,color
-length,color
3/Since a field can only belong to one group, it means model_id,length,color which would first (or second) group, then item_id and label
If a field does not belong to a group, he goes to "remaining group" at the end
in the remaining group, you can add a link to the other group since you don't know which field is the key.
<style> </style>
field group field remaining fields
1 | item_id | False |
1 | label | False |
2 | model_id | False |
2 | length | False |
2 | color | False |
3 | order_id | True |
3 | link to group 1 | True |
3 | link to group 2 | True |
3 | amount | True |
Best regards,
Simon
PS : I have in mind an evolution with links between non-remaining table (like here, the model could be linked to the item as an option)
Hello,
As of today, DCM is great to store credentials. But once we want to dive deeper in technicity, like using macros or Applications, it's really bad. One of the things I hate is that we can't retrieve any informations from the DCM connection, just the id. Not good for logs, really bad for understanding and have some conditional logic related to connection type or name.
Here an example
Nice, I managed to retrieve an id but I have no idea of what it means : what kind of connection? what's name?
Best regards,
Simon
Hello
Cartesian product is a common issue when joining dataset with a bad key. What I suggest is an option to check if there will be a cartesian product on the join tool.
-there is a label "Cartesian product (non join key uniqueness) detection"
-under it a drop down menu with three choices
-do nothing
-fail
-warning
Algo :
if do nothing==> well... do nothing more than actual behaviour.
if "fail" or "warning" : count distinct of join key versus count row on each side of the join. If none is unique, display a warning or an error message.
Best regards,
Simon
Requesting a reduced-cost, read-only license to allow for additional users in our organization be directly review workflows for UAT and control testing. Currently, the only individuals who can see the detail of Alteryx workflows directly are those with a full designer license or temporary trial license. In our Alteryx control structure, we have additional reviewers confirming the workflow who do not have licenses, which requires copious amounts of screenshots and/or direct meetings with our licensed designers to walkthrough the flows step-by-step. It would be much more efficient to provide a license that would allow folks to click through the integrations themselves, potentially allowing for comments and annotations, but without the ability to make direct changes. This would be much more cost efficient for our organization and allow for better workflow review and control.
I find it extremely annoying having to individually disable/enable control containers in a workflow. It would be nice if there was a way to select all control containers that I want to disable/enable and then be able to right click and do it quickly in one motion. This would save me a lot of time when working with 10+ control containers.
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.
Lets say you have a row of 10 filter tools vertically and there's a select tool coming out of each input for each filter. It can get dizzying to tell the difference. It would be great to be able to select a colour for tools when on the canvas so e.g. in the above I could say " my green selects are the true and my red selects are the false"
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,
Hello all,
As of today, if you have admin and non-admin version of Alteryx Designer installed on your computer, and install Business Intelligence Suite, you are able to run either version. It will not run both versions. This means whatever reason you installed admin and non-admin version, Business Intelligence Suite will run with only one Designer.
I installed my computer Alteryx Designer 22.3 non-admin and 23.1 admin versions, both Predictive Analytics. I also installed BI Suite admin version, and BI suite non-admin version. Alteryx will uninstalled admin version, and kept non-admin version of the BI Suite. So, I can use BI Suite only with non-admin version now.
I'm bringing this idea for your vote to make available for both profiles/versions within Designer.
Thanks for voting
Similar to being able change the parameters of a tool using the interface tools, it could be very useful if Alteryx Designer had an option where the configuration of a tool can be modified by another tool's output (which can only consist of one row & column and may include line breaks/tab characters, only first row is used if there are multiple rows) while the workflow is running, therefore reducing the need to chain multiple apps.
This feature could be made possible as the "Control Containers" feature is now implemented, and it could work like below:
Suppose you need to write to a database and may need to specify a Pre-SQL statement or Query that needs to be dynamically changed by the result of a previous tool in the workflow.
In this case, as the configuration of a tool in the next container needs to be changed by the result of a previous formula, there would need to be an additional icon below the tools, indicating that the tool's result can be used for configuration change.
This icon which will appear below the tools will only be visible once at least one Control Container and an Action tool is added to the workflow, and will automatically be removed if all the control containers are removed from the workflow. User can change the configuration of the destination tool using an action tool, which must be connected to a tool in a container that will be run after the one it is contained in has finished running, as a tool (or several tools) that is contained in the next CC in the workflow needs to be dynamically modified before the container it is contained in is activated.
If a formula tool containing multiple formula fields is added to the action tool, the user will see all the formula outputs similar to connections (i.e. [#1], [#2]...) that can be used as a parameter.
The screenshot below demonstrates the idea, but please note that this is a change where adding an action tool may not mean that this workflow will need to become either a macro or an analytic app, so a new workflow type may or may not have to be defined, such as "Dynamic Configuration Workflow (YXDW)". Analytic Apps and Macros which utilize this feature could still be built without having to define a new workflow type.
Providing user the ability to paste a tool with one of the three options regarding connections:
- Paste with Incoming Connections,
- Paste with Outgoing Connections (where applicable),
- Paste with Both Connections (where applicable)
could make it easier to configure the workflows where many incoming and/or outgoing connections are necessary for a specific source or target tool (i.e. a certain mapping table joined to several data streams in the same workflow after being modified with a formula tool to match with a specific stream).
I have a use case where I am transitioning workflows to someone -
One workflow leverages the outputs of one workflow as inputs in to another - it would be awesome if I could include a link on a tool or comment box that would automatically open the exact output tool. Right now I am taking pictures and mentioning the names of files and tool-ids. Seems like it would be an easier way.
Consider, for a moment, Standard Macros as old-school Subroutines in which you would have a library of Subroutines that could be invoked from numerous code sets. Each Subroutine could have any number of arguments, and when the Subroutine is invoked, the calling code provides the arguments and their values to the Subroutine.
You can do this in Alteryx - but with a very large but. The source field names being passed to the Standard Macro have to be the same field names the Standard Macro is expecting. To make the Standard Macros more "library friendly" - allow the calling workflow to alias fields in the dataset for the sole purpose of sending them to the Macro.
Example: Standard Macro that returns a Vendor ID based on a Location and Item Number.
Macro Input: Location ID, Item Number
Calling Workflow has: Purchase Location and Item Code
The Macro on the calling workflow would have a mapping:
Data Set Object | Macro Input Object |
Purchasing Location | Location ID |
Item Code | Item Number |
User | Likes Count |
---|---|
16 | |
7 | |
5 | |
5 | |
3 |