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
Pre-Filter as new option in Input Tool might reduce import data and allows to input only selected data (ie. for specific period or meeting certain conditions).
Cheers,
Pawel
Currently saving file output as PowerPoint is possible only doing workaround as in Megan's article (link below) using Render Tool. It might be more intuitive to implement PowerPoint to supported options in "Output Mode" dropdown.
Cheers,
Pawel
Add PowerPoint format file (ppt/pptx) into supported file type as direct connection in Input Tool.
PS. I know that we have workaround allowing to import PowerPoint slides into Alteryx but I'm describing automated solution :)
Cheers,
Pawel
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.
Currently the Databricks in-database connector allows for the following when writing to the database
This request is to add a 5th option that would execute
Why is this important?
While this request was specific to testing on Azure Databricks the documentation for Azure and AWS for Databricks both recommend using "Replace" instead of "Drop" and "Create" for Delta tables in Databricks.
Hyperion Smartview Connect
Hey YXDB Bosses,
Let's move forward with our YXDB. Maybe give AMP a real edge over e1. Here are some things that could may YXDB super-powered:
Just a little more craziness from me
cheers
Hi UX interested parties,
Here are some ideas for you to consider:
1. These lines are BORING and UNINFORMATIVE. I'd like to understand (pic = 1,000 words) more when looking at a workflow.
If you look at lines A, B, C in the picture above. Nothing is communicated. Weight of line, color of line, type of line, beginning line marker/ending line marker, these are all potential ways that we could see a picture of the data without having to get into browse everywhere to see the information. If we hover over the data connection, even more information could appear (e.g. # of records, size of file) without having to toggle the configuration parameters.
2. Wouldn't it be nice to not have to RUN a workflow to know last SAVED metadata (run) of a workflow? I'd like to open a "saved" workflow and know what to expect when I run the workflow. Heck, how long does it take the beast to run is something that we've never seen unless we run it.
3. I'd like to set the metadata to display SORT keys, order. Sort1 Asc, Sort 2 Desc .... This sort information is very helpful for the engine and I'll likely post about that thought. As a preview, when a JOIN tool has sorted data and one of the anchors is at EOF, then why do we need to keep reading from the other anchor? There won't be another matched record (J) anchor. In my example above, we don't ask for the L/R outputs, so why worry about the rest of the join?
4. Have you ever seen a map (online) that didn't display watermark information? I think that the canvas experience should allow for a default logo (like mine above, but transparent) in the lower right corner of the canvas that is visible at all times. Having the workflow name at the top in a tab is nice, but having it display as a watermark is handy.
5. Once the workflow has RUN, all anchors are the same color. How about providing GREY/White or something else on EMPTY anchors instead of the same color? This might help newbies find issues in JOIN configuration too.
6. If the tool has ERRORs you put a RED exclamation mark. I despise warnings, but how about a puke colored question mark? With conversion errors, the lines could be marked to let you know the relative quantity of conversion errors (system messages have a limit)
Just a few top of mind things to consider ....
Cheers,
Mark
Alteryx really needs to show a results window for the InDB processes. It is like we are creating blindly without it. Work arounds are too much of a hassle.
We really need a block until done to process multiple calculations inDB without causing errors. I have heard that there is a Control Container potentially on the road map. That needs to happen ASAP!!!!
Hello!
A quite minor, pedantic issue from me today.
Currently, the Oversample Field Tool's naming and configuration suggest that the tool can over sample data:
However, I would argue the tool under samples data instead.
Here are a few sources that explain this much better than I can:
And an image is taken from Medium:
Effectively either step is to create a similar (or same) number of records between each class. Under sampling is the process of taking samples from the majority class, and ending up with a smaller dataset than started with. Over sampling is the process of duplicating records within the minority class, and creates a larger dataset.
When using the Oversample tool within Alteryx, using the example workflow for reference:
When summarizing the input:
And the output:
It's clear that the data has actually been under sampled, in that random samples have been taken from the majority class to match the minority, rather than creating duplicate minority records.
I would suggest a quick renaming of the tool to "Undersample Field Tool", and documentation to not cause confusion to new users of the platform.
Kind Regards,
TheOC
Current:
Currently in Result window we have datacleanse, fileter and sort functionality which makes life easier.
We dont have column Rename and Data type change functionality. In order to do that we need to drag a tool for the same for Rename of column.
Expectaion:
Result Tool should be capable enough to Rename column and Data type.
It will save a lot of time ,
Idea: Add a Connection Line Routing Tool
Details
Connection lines get in the way. A routing tool could solve this problem simply by guiding the line through its position. The input would be the same as the output, but the direction of the input/output anchors should be configurable.
Hi Team,
Microsoft Outlook is extensively used for day to day operations. With more teams, adopting Alteryx within the firm. We wanted to explore the option of end to end automation and the outputs are directly triggered to external email domains however, due to firm restrictions we cannot send email to external/internal email domains without labelling the email. Is there way to in include email labelling/classification as part of emailing tool.
Tools should not error with Zero rows, often when working with macros it is possible to have a scenario where zero rows or columns is legitimate. Some tools are fine with this and some are not. In my case the Select Tool does not allow it so I have to create a Work around with a Text Input tool.
In Japan, the prople usually use the date format "yyyy/mm/dd". But there is no preset in Date tool. So I usually use custom setting, but it is the waste of time.
So please add yyyy/mm/dd format to the preset in Date tool configuration for Japanese people.
On the UNION tool, allow for deselecting columns that aren't relevant. Leave the union exactly as it is, and you could go into the manual configuration. Align the columns just as you would in the manual configuration. The addition would be that you have the behavior like you see in a join tool where you could deselect C1, C2, C3.... Cx.
Too many times I have a union and there are fields I simply don't even want to bring in, but then have to add a select tool right after in order to remove them.
Alteryx Server is great, but very costly. Having the ability to install the Alteryx engine without the Designer, thus allowing you to share Workflows/Apps with users directly. This could be licensed on a per user basis as well, but a reduced cost.
This also allows for some more advanced workflows that do not work in the Gallery.
Please add a data validator workflow.
Suggested features will be the following:
1. Add validation name and set the field/s of your data you want to validate. (it can have more than one validation name on one workflow)
2. On the selected validation(name). Add features that will check/validate the information below:
A. Verify data type
B. Contains Null
C. Max and Min string length
D. Allowed values only, else it will give you an error
E. Regex expected to match and not allowed to match.
3. It can have two(2) outputs. One is True(which is match) and False(which is fail over/error).
In the tools that embed the "Rename" option (Select, Append Fields, Join, Join Multiple), copying the new name will copy all the information of the field configuration : tick/untick, original field name, type, size, new name and description.
Renaming the field "Rename_Field"
In my opinion, it should copy only the new name. This would be useful, especially because when you change the name of a field, it isn't automatically changed in subsequent tools, so copying it to replace it in those tools is faster than retyping it every time.