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
If the tables in the config window has lots of rows, it is quite complicated to find those of interest.
Please add a filter or search option (e.g. by the field name) to display only the relevant rows.
It would also be helpful to select or deselect multiple selected rows with one click.
Find an example from the "Select-Tool":
We have discussed on several occasions and in different forums, about the importance of having or providing Alteryx with order of execution control, conditional executions, design patterns and even orchestration.
I presented this idea some time ago, but someone asked me if it was posted, and since it was not, I’m putting it here so you can give some feedback on it.
The basic concept behind this idea is to allow us (users) to have:
This approach involves some functionalities that are already within the product (like exploiting Filtering logic, loading & saving, caching, blocking among others), exposed within a Tool Container with enhanced attributes, like this example:
The approach is to extend Tool Container’s attributes.
This proposition uses actual functionalities we already have in Designer.
So, basically, the Tool Container gets ‘superpowers’, with the addition of some capabilities like: Accepting input data, saving the contents within the container (to create a design pattern, or very commonly used sequence of tools chained together), output data, run the contents of the tools included in the container, etc.), plus a configuration screen like:
This should end a brief introduction to the idea, but taking it a little further, it will allow even to have something like an Orchestration layout, where the users can drag and drop containers or patterns and orchestrate them in a solution, like we can do with the Visual Layout Tool or the Interactive Chart tool:
I'm looking forward to hear what you think.
Best
When making any type of macro, it's important to test the functionality of the macro via a debug. This is accomplished successfully with normal tools, however there's a bug that will not allow the user to debug In-DB macros that use either of the following standard Alteryx tools:
If either of these tools are included in the macro you are building, an error message will appear not allowing you to open a debug.
Error message: Question Tool Load Error: A question tool with a tool id of XXX is missing the associated question data.
Of course, Macro input and output tools do not require any specific action/question tool associated with it. This is a bug. A user pointed out the XML issue almost 3 years ago here:
In summary: "It appears that the tool itself inserts a hidden Question attribute into the XML which can also be seen in Workflow Configuration"
Source:
Examples....
A normal macro, using standard tools:
After debugging a standard macro, the Macro Input/Output tools correctly change to a Text Input and a Browse tool. This allows the macro author to test the macro.
However, when trying the same thing with In-DB tools in a macro, an error message appears:
In-DB macro 1:
In-DB Macro error message (after clicking "Open Debug"):
It would be great if we could add example workflows to our macros, accessible in the same way as from the original tools (example hyperlink shown after single-clicking on a tool in the tool palette or when searching in the search bar).
There is a post on how to do it for custom tools How to add an example link in the custom tool (alteryx.com). The way described there has limitations and does not seem to work on macros: I was able to get the link to show up, but nothing happens when I click.
My suggestion, make it easy to add an example workflow to a macro, like it is to change the logo or add a help link.
We will not be enabling DCM for the time being (see https://community.alteryx.com/t5/Alteryx-Designer-Desktop-Ideas/Enable-auto-complete-predictive-typi...).
But, when you do not enable DCM, you get an annoying pop up every time you open Designer that says "DCM toggle is not enabled".
Please give us the ability to turn this pop up off.
I can't even count how often I looked at an Excel, CSV or even YXDB file, where I KNEW that it was generated by Alteryx, but I couldn't remember the workflow. Currently, I have to simply go through all workflows I ever build and see if I can find it.
Theoretically, I could use a text-search across all workflows and see if I can find the output names - problem here: Most of my output filenames are generated dynamically on the run.
It would be amazing if Alteryx could simply write the Workflow name (maybe even path) into the metadata of a file.
(Screenshot from Google, as my os is set to German)
How about, we write "This file was created with by "Create Controlling Reports.yxmd on 2023-02-06 with Alteryx Designer 2021.4.298434" in the field 'Comments'?
This would make it extremely easy to find what workflow the file generated. I think it would be an option to talk about "filepath" instead of filename, but the filepath could include the local machine name, which might include GDPR information.
@Community: Is there any additional information that you'd like to see in the metadata?
Best
Alex
Hi
The action of the 'tab' key in configuration window recently appears to have changed from indenting to a navigation function.
The user should be able to select which action the tab key performs.
Alternatively, tab should indent and shift-tab (or alternative) navigate. I'm not the only one who would appreciate the choice.
PuffinPanic
Currently when debug mode is entered in analytic apps and macros, the direct inputs to the app/macro when the error occurred are hardcoded into a workflow in debug mode, so that errors can be more easily detected.
However, inputs into analytic apps also create global variables which can be used in the more code-heavy aspects of Alteryx such as the Formula Tool. These are not updated in the same way which can cause workflows to break in debug mode - it would be really helpful if global variables could be updated in the same way as the inputs into tools are.
Today, I am able to take an excel file from a folder and drag it onto the canvas, which automatically creates an Input Data tool.
I would like to be able to drag an excel file right from outlook to do the same!
In the RecordID tool, provide additional options for the creation of the ID, specifically allow for the ID to 'Intervals'.
For example, Record ID every 10, meaning instead of creating an ID of 1, 2, 3, 4, 5 .... you could create an interval of your choosing, the most obvious would by 10 or 100 thus your ID's would then be 10, 20, 30, 40 .... or 100, 200, 300, 400, 500 ... etc.
I can be picky about how my workflows are laid out. Oftentimes, the connector between tools has a "mind of its own" as to what direction it goes and how it crosses other objects. I'd like to see the ability to control the connector lines with "elbows" that can be positioned in custom locations and directions, like an MS Visio diagram. Alternatively, add a simple "pin" tool could be added to the canvas and it's only function is to take in and send out a connector line by defining the input and output location. The input and output locations could be defined angularly/radial in degrees, for example. Image attached below of existing workflow with a "troublesome" connector and the concept of "elbows" and "pins" added as an alternate control mechanism. Both would be great! :)
Sometimes, Control Containers produce error messages even if they are deactivated by feeding an empty table into their input connection.
(Note that this is a made up example of something which can happen if input tables might be from different sources and have different columns so that they need separated treatment.)
According to the product team, this is expected behaviour since a selection does not allow zero columns selected. This might be true (which I doubt a bit), but it is at least counter-intuitive. If this behaviour cannot be avoided in total, I have a proposal which would improve the user experience without changing the entire workflow validation logic.
(The support engineer understands the point and has raised a defect.)
Instead of writing messages inside Control Containers directly to the log output (on screen, in logfile) and to mark the workflow as erroneous, I propose to introduce a message (message, warning, error) stack for tools inside Control Containers:
This would result in a different sequence of messages than today (because everything inside activated Control Containers would be reported later than today). Since there’s no logical order of messages anyways, this would not matter. And it would avoid the apparently illogical case that deactivated Control Containers produce errors.
Hi currently if you use the cross tab tool and the names of the new fields should have special characters they end up being replaced in the new headers with underscores "_", and then need to be updated in someway. It would be great if this was all done in the tool. In other words the new headers have the special characters as desired
The Edit menu allows you to see what your next undo/redo actions are. This is super helpful, however sometimes I decide to scrap an idea I was starting on and need to perform multiple undo's in a row. It would be great if we could see a list of actions like in the debug undo/redo stack menu then select how many steps we'd like to undo/redo.
For example, using the below actions, if I want to undo the Change Summarize Properties and also the Modify Summarize, currently I have to do that in two steps. I'd like to be able to click the Modify Summarize and have the workflow undo all commands up to and including that one.
When you start using DCM - you may have existing canvasses which use regular old connection strings which you want to migrate to DCM.
Currently (in 2023.1.1.123) - when you select "Use Data Connection Manager" - it shreds the configuration of your input tool which makes it difficult to just convert these from an existing connection to a DCM connection
The only way to then make sure that you don't lose any configuration on the tool then is to use the XML editing functionality of the tools and copy across your old configuration.
Could you please add the capability to keep my current tool configuration, but just change from using a regular old connection string to using DCM?
Many thanks
Sean
cc: @wesley-siu @_PavelP
Very often, I used a container to make notes about certain parts of the workflow. Some of the comments that I created are pretty long. Could the user have the possibility to have at least rows for the title of the container?
I have created a screen to show what I have in mind. Potentially users could have the ability to turn this option on or inside the container?
As an international organization we deal with clients in multiple-countries.
Name matches for names including Chinese characters generate a unicode conversation warning and are excluded from the fuzzy match.
It would be good if fuzzy match could be enhanced to handle Chinese characters.
Note: This idea doesn't strictly fit into any given category as it involves enabling support for something that affects numerous aspects of Alteryx's already existing spatial features.
I live in Australia. As do a large number of your users. Like me, many of those users use Alteryx to process spatial data. There is only one problem; we live on a roving continent. Every year our continent shifts ever so slightly but over time that shift becomes significant. For this reason we have our own continental system of spatial coordinate projections. It's called the Geocentric Datum of Australia or GDA.
Since 2000, the official Australian geodetic datum has been GDA94. However, according to the Intergovernmental Committee on Surveying and Mapping (ICSM), because the coordinates of features on our maps, such as roads, buildings and property boundaries (and so on), are all based on GDA94, they do not change over time. This is why they have since adopted a new datum: GDA2020. This has now become the standard for mapping in Australia, bringing Australia’s national coordinates into line with global satellite positioning systems.
A more detailed explanation of this can be found on the ICSM's website: What is changing and why? | Intergovernmental Committee on Surveying and Mapping (icsm.gov.au).
Of course Alteryx supports the more global WGS84 standard, which like GDA94 is a fixed datum. But there is up to a 1.8 metre discrepancy between GDA94 (and WGS84) and GDA2020. For spatial analysis projects that don't require metre accuracy that's not a problem. But imagine you are building a bridge, plotting the lanes of a road or programming a GPS enabled tractor. That 1.8 metre discrepancy between the real world coordinates and the projection is enough to cause problems.
And it is. Which is why we request that Alteryx include support for GDA2020 in its existing selection of spatial projections.
This will enable spatial datasets configured in GDA2020 to not require conversion and thus risk corruption or error. This includes providing the ability to configure GDA2020 as the spatial projection in the input tool and all spatial tools.
Doing so would go a long way to supporting your ever growing Australian user base and maintaining Alteryx's position as a trusted software for processing spatial data.
Please consider implementing a consistent case-sensitive option for all tools and functions.
To compare string values, including case-sensitivity: This post had a good description of the challenge, but the post has been archived:
For all the time I've used Alteryx, I thought that IF "test" = "TEST" would evaluate to false. Today I realised that isn't the case and I was surprised. I'm very surprised that "equals" performs like it does.
A few existing Ideas request case-sensitivity for individual tools:
Case insensitive option while joining two data sets
https://community.alteryx.com/t5/Alteryx-Designer-Desktop-Ideas/Case-insensitive-option-while-joinin...
Unique tool enhancement - deal with case sensitive data
https://community.alteryx.com/t5/Alteryx-Designer-Desktop-Ideas/Unique-tool-enhancement-deal-with-ca...
This new Idea requests system-wide consideration for case-sensitivity, for all tools and functions.
Current state:
These tools and functions are case-sensitive:
These tools and functions are NOT case-sensitive:
These tools and functions can be either case-sensitive or NOT case-sensitive, depending on the options used:
Current Challenges:
How do we easily identify Lower Case, Upper Case, Mixed Case?
How do we easily compare strings for equality, using case sensitivity?
Request:
Ensure all tools and functions include an option to ignore or consider Case
Create new functions for IsUpperCase, IsLowerCase, IsMixedCase
Create a new function for IsEqual, with an option to ignore or consider Case
See attached workflow, which
While the result window allows sorting and filtering, every time the user switches to another tool within the same run, the configuration is lost. It would be good if there was a 'Retain" button so that the user does not have to keep setting this each time the tool is switched or when the canvas is retriggered.
User | Likes Count |
---|---|
40 | |
32 | |
21 | |
10 | |
7 |