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 you render out to an excel file, the excel file is created as a new file. You cannot render to an existing excel file.
I'd like to see this functionality. I have a client who has a workbook with multiple formatted sheets and they'd like to render an addiitional sheet of formatted data out from Alteryx into the existing workbook.
Trying to solve some use cases, I realized that I had to simulate the factorial behaviour.
Having a factorial formula can make this process easier.
Thanks!
Changing the Macro Input tool in an existing macro is dangerous and can result in unmapped fields or lost connections in workflows using the macro. For example, we have a widely used macro for which we'd like to change the name of an input field, change it's default type from Date to DateTime, make it optional while keeping other fields mandatory. Currently, we cannot find a solution which would not require us to fix each workflow using the macro after changing it. We should be able to change the field names, field types (e.g. String to V_WString, Date to DateTime), select optional fields and do other modifications to Macro Input without having to update each workflow using the macro. The new Macro Input UI could be enhanced with a window similar to that of Select tool's. Technically, the Macro Input fields could have a unique ID by which they would be recognised in workflows, so the field names would just be aliases that could be changed without losing the mapping. In summary, we are restricted to our initial setup of Macro Input and it is very complicated to change it afterwards, especially if the macro is used widely.
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
For in-DB use, please provide a Data Cleansing Tool.
It would be helpful to be able to filter within the results window of a Browse tool for all "Not OK" records (records with leading/trailing spaces, embedded newlines, etc.) I can already filter for null and empty values, but this would be helpful for cleaning up data. I want to see the "dirty" data before taking out leading/trailing spaces or embedded new lines to see if there is something I'm missing in the data that needs to be further parsed or modified.
We see canvasses every day where dozens fields are brought into a canvas or a macro, but never used - and this just creates slowness for no good benefit.
Given that one of the selling features of Alteryx is the speed of processing - could we look at three improvements to the Alteryx engine & designer:
From what I can tell using ProcMon, presently when using the Directory tool to list files (including subdirectories) the Alteryx Engine runs a single threaded process.
When you're trying to find files by checking recursively in large network paths, this can take hours to run.
It would be great if the tools would split up lists of directories (maybe by getting two or three levels down first) and then run each of those recursive paths in parallel.
While it is possible to do this using a custom Python or cmd->PS command, it would be great if this could just be a native part of the application.
I would like to suggest creating a fix to allow In-DB Connect tool's custom SQL to read Common Table Expressions. As of 2018.2, the SQL fails due to the fact that In-DB tools wrap everything in a select * statement. Since CTE's need to start with With, this causes the SQL to error out. This would be a huge help instead of having to write nested sub selects in a long, complex SQL code!
Hi Alteryx community,
It would be really nice to have v_string/v_wstring and max character size as a standard for text columns.
it is countless how many times I found that the error was related to a string truncation due to string size limit from the text input.
Thumbs-up those who lost their minds after discovering that the error was that! 😄
It would be great to have an option in the Output Data tool to write the workflow name to the Info properties of Excel outputs.
Maybe something like this:
So that whenever you open an Excel file you always have a way of finding the name of the workflow that created the file.
This would make it so much easier as I often have to share Excel files with colleagues and customers and then need a way of tracking them back to workflows weeks or months later.
Hi,
I'm not finding it anywhere as a current option, but my company uses branded PowerPoint slides using our logo, these slides are in 16.:9 (widescreen) for slide size, but Alteryx won't output to that size even if I choose custom for page size & have Widescreen selected as an option. Could there be an Advanced Options button added that would allow users more output choices, like choosing the 16:9 ratio size output? Without it, I'm having to output the largest map I can create (13 x 9.75 in Report Map tool) and then stretch/shrink to get it to fit the 16:9 slide...for every single map/slide (currently making 40 maps at once).
Is there a work around to accomplish my goal currently? And if not, could the option be added to the Render tool? Thank you!
The drop down\list box have numerous ways to list values. One of them that I like is connecting to an external source. You simply have an external source file with a Name column and a Value column. It will display the data in the Name column and pass the data in the Value column. Now suppose instead of connecting to an external source I wanted to use connected tools. Currently, I would have to crosstab this data and the drop down\list box would display and pass the column names.
What if the drop down\list box could have an additional option added where you could connect tools and it would act identically as an external source (display the data in the Name column and pass the data in the Value column). This would be much easier and more functional!
When you use Create Points tool - you then almost always need to use a Select tool to rename that point.
Can we please add a single text field to the Create Points tool - which would then allow us to create and name a point in one step?
It would be nice to be able to concatenate numeric values (integers, doubles, etc.) directly in the Summarize Tool.
I know this would involve converting it to a string on the backend, but I don't believe there would be any data loss when going from numeric to string. I know this can be done by using other tools like Select of Formula to convert to string before the summarize but I don't see any reason why this couldn't be accomplished in a single tool.
Thanks,
Paul
Hello,
It would be very helpful to have a search box for field names in the summary tool, I think it would help decrease errors by selecting fields by mistake with similar names and will help gain a couple of seconds while looking around for a specific field, particularly with datasets with a lots of them.
Like this:
This request is super simple! I love how Alteryx displays the row count and size of the data passing through each tool at run time. Can you set the default formatting for the row count indicators to be #,###? Without the commas, it's hard to easily check the row count once you get more than 6-9 digits.
In the example below, it would be so much more readable if it displayed as 75,640,320.
Extend the MongoDB tool to work with Atlas MongoDB instances.
Hi all,
When debugging an error, we need to verify tool by tool in a sequence to better understand what is really going on.
Sometimes the tools are miles away from each other. Imagine a gigantic workflow with a lot of connections going back and forth and wireless connections everywhere to help the workflow organization. Here is an example with more than 1300 tools:
My idea is to have a shortcut showing all the previous/next tools and by selecting the previous/next one you go directly to them.
Something like this:
What do you guys think about that?
Best,
Fernando Vizcaino
We have 'CountDistinct' and 'Concatenate' options within Summarize tool.
But 'Concatenate' displays all the instances of value for a Grouped field, this might include lot of duplicates.
It would be great to have an option like 'ConcatDistinct'.
For example -
Group by 'Branch' and 'ConcatDistinct' Customer should result as Figure 1 instead of Figure 2 -
Figure 1-
Figure 2-
While this is achievable in different ways currently with a set of tools, but it gets tedious when number of fields is large from which distinct values are to be captured.
Thank you,
Rohan.