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
When bringing data together it is often needed to assign a source to the data. Generally this happens when you union data and need to know things later about the data for context. It would save time to generate a source field that is assigned based upon the input connections of the union tool. Perhaps when unioning data you can assign a name to each input stream?
I'd like to see Alteryx allow a second install of your license on a second, personal machine. Tableau allows this and IMO is why there is such a robust online / blog community around that product.
For those of us that work at mid-size to large organizations, there are often strict rules governing internal data and use of cloud-based data sources. If I discover some new trick I'd like the share with my fellow Alteryx analysts outside of my company, I have no clear way to do that the same way I can with Tableau where I can do it at home not using my company's data.
Being able to learn new features and test things out on commonly available public data (ever notice that Superstore data set everyone who gets Tableau has?) would accelerate what we're able to do with the community site here and the larger analytics blogging community.
Currently the Throttle Tool allows control to a number of calls per minute. Some APIs include a limit to the calls per hour and a combination of throttles. I would love to see the option to choose the number of calls per hours and have 2 limit controls (eg 100calls per minute and 100calls per hour)
When a tool's input connector is already attached to a data stream that only accepts a single connection, attempting to attach a 2nd data stream with the same fields should automatically insert a Union tool. This would be similar to the way an Action tool is automatically added when you connect an Interface tool to another tool.
I was recently surprised to find that Alteryx doesn't already havea connector to upload to SFTP sites. I've managed to work around it with RunCommand and some external programs, but it's very cumbersome. A simple SFTP upload connector would be a great addition to Alteryx.
At TargetSmart, we create a lot of CSV deliverables for our customers. Since Alteryx differentiates between blank strings and null values (a good thing), the CSV output is not consistent between the two without an explicit multi-field formula step to set all null to empty strings (or vice versa). This is an easy fix for us. However, in some cases we have very large files with thousands of fields and millions of records. For these instances, the workflow run-time is greatly increased by the multi-field formula. If possible, I was wondering if adding a checkbox option to CSV output steps (“Make null/empty consistent” or “Never quote empty/null values”) would possibly be a more efficient approach as the check could be part of the output step (which I assume is native C++) versus the Multi-field formula (which I assume has some level of inefficiency in interpreting the formula dynamically).
I know you can add a field for "today" and then use that field to append the filename, so the output ends up as Ouput_Date.xlsx, but it would be great to be able to do that without adding a new field for the current date. If it were simply an option in the filt output settings dialog, that would be great.
The capability to input/output R Datasets via the input/output tools, together with all the other data formats as well (like csv, Excel, SAS, SPSS, etc).
I would like to see the same functionalitly that the Output Tool has in the Render tool. In the Output Tool, you can specify the Excel Worksheet along with the Sheet Name that you want to output too. Meaning Same Worksheet, different tab:
C:Output FilesExample_Worksheet.xlsx|Report_1 C:Output FilesExample_Worksheet.xlsx|Report_2
This functionality is not currently available in the Render Tool and would be very useful and cut out some manual operations on the back end that requires us to copy/paste from one file to another.
I tried using the Section Break technique that was offered as a suggestion, but it did not perform what I needed.
Hi
Wanted to control the order of execution of objects in Alteryx WF but right now we have ONLY block until done which is not right choice for so many cases
Can we have a container (say Sequence Container) and put piece of logic in each container and have control by connecting each container?
Hope this way we can control the execution order
It may be something looks like below
Configurable hotkeys/keyboard shortcuts would be awesome. For instance, select/deselect highlighted fields or remove prefix are two commands that I use frequenctly but which are buried in menus.
Being able to assign hotkeys to favourite tools would be another time saver. Imagine, ctrl-alt-F and a formula appears under the cursor!
I know this has been suggested before, but it would be great if calculations and transformations could be cached between workflow executions. Perhaps the browse tools could be configured as caches. Any spot that has a browse tool fixes the value of that node between runs provided that there are no upstream tool changes. The cache could be optional (or flushed) to allow for dynamic input data that could change between executions, even if the tool chain didn't.