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
Please enhance the Join Multiple tool to include an option of:
"left outer join all on input 1".
Such a tool would be massively advantageous when data granularity is defined by one dataset (input 1) and many subsequent tables just need to be joined onto that input.
As-is, I have had to manually perform dozens of join + union sequences which seems both untidy and inefficient.
Such a feature would likely be more useful than existing options of full outer joins / inner joins which currently the tool allows.
I love the new (relatively) ConsumerView Decoder Tool! I used to do it the hard way, and it was fragile.
However, one thing is still missing: the Mosaic fields (MOSAIC HOUSEHOLD and MOSAIC ZIP4) - these are output from the tool as nulls. So, not only do you not get it decoded, you have to join back to the input to get the fields back as they were.
First, at least please pass them through as they were.
But preferably, decode them to the Mosaic Segment/Group names.
I realize (or couldn't find) the source for the Mosaic segment definitions is not currently in a Calgary database, but the tool is in the Calgary group.
I was able to add the following lines of R script to get the importance of the variables used in the cluster analysis. This will allow the user to see what variables are important in determining the clusters they have.
The script I added is below. It is pretty basic and could used spruced up by an Alteryx engineer as far as column naming, accounting for contingencies, and making it a reporting function. I think this would be a valuable feature for future versions of this tool.
library(FeatureImpCluster)#load library
FeatureImp_res <- FeatureImpCluster(clus.sol,as.data.table(the.matrix)) #Use FeatureImpCluster to take the cluster model (clus.sol) and data (the.matrix) to get variable imp.
FeatureImp_df <- as.data.frame(FeatureImp_res$featureImp) #turns features from a list to dataframe
FeatureImp_df_rn <- tibble::rownames_to_column(FeatureImp_df, "Variable") #Adds the variable name to the importance scores
write.Alteryx(FeatureImp_df_rn, 3) #outputs dataframe in output #3
Hello
I have searched the community but haven't found any obvious solutions to this.
When using a cross tab I often find that there shouldn't be any aggregated values and if there is it means there is an issue with my data or workflow.
Therefore I think a useful feature would be an option for the cross tab tool to be able to return an error if it trying to aggregate any values.
I have a work around by using a summarize tool to count the non unique records and then a test to see if there are any duplicates but I think this could be a useful addition to the tool.
Thanks
The macro input tool asks for a template input that is either a text or file input. A perfect template can be hard to come by and so I wonder if the macro input could just ask how many columns are expected and the type and size that this column should be. I feel this would be more intuitive and easier to debug.
In the next product version, can the parameter options for the topic modelling be changed to allow the output of both word relevance summary and interactive chart? It's a bit strange to run the tool twice to get this output.
I think this was brought up a few years back but why doesn't the Union config by name option have a field map? It would stop that feeling you get when you browse your workflow after a union tool and find a column which is 5% blank and 95% full sitting next to one with a slightly different name which is 95% blank and 5% full.
I would like to get a full legend overlay when hovering over the bubble (see example in power BI).
The new versions of Alteryx the red "change color" has gone to yellow which is almost impossible to see with a big and bright monitor.
PLEASE change it back to the normal red background color!
Looking for a way to make multi-selection much easier (rather than single click per item). Could be an improvement on the List Box, or a new tool that allows multi-selection with highlighting desired items. Control/Shift keys for selections similar to Windows, etc.
It would be helpful to be able to toggle the way the Mode calculation handles two or more "ties." Currently if there is a tie between records, the lower is returned. I have a use case where I would rather have the higher value return if there is a tie. I could also see there being a use for an average between the tied records. Ideally I think there would be three options for a tie: use the 1. lowest value 2. highest value 3. average of tied values. I'm not sure if first/last would also be helpful to have as options.
My use case is for product dimensions. We use the mode to normalize the dimensions (height, width, depth) of products. Because we are using the dimensions for space planning, if the lower value is used there may not be enough space for the product on the shelf. We would rather use the higher of the tied values to make sure we aren't creating a plan where the products won't fit.
Allow the direct entry of the test start date into the AB Trend tool rather than forcing the use of a calendar widget to select the date. Or at least make the calendar display the date that was set rather then the current month.
It would also be useful to edit the sample workflow for this tool , sample 21_AB_Trend_Controls_Analysis_Sample.yxmd, to add annotations to each tool to describe what the settings are in the example as well as to add more specific detail to the workflow description.
Today the Autofield tool transforms the fields into byte by default when it considers that the content is suitable while we expect text in it and that it can simply be a field not filled in in the context current but which may be later.
The idea would be to be able to choose which type by default to implement on text or empty fields and not the default byte because a byte field is not recognized on a formula using an IN for example which can produce errors in the following workflows.
Hi Team,
I have a dataset of x,y values that I am plotting with an interactive chart tool. These values will vary widely so I can't use custom display ranges and have to rely on the "Auto" function for display range.
My problem is that the two axis are Auto scaled to different scaling and it is turning all my ellipse shapes into circles. Not a huge setback as you can check the Axis labels to see the scale but for this use case the shape of the data is what I am trying to portray and this makes my reports somewhat misleading.
I'm suggesting adding an option, maybe a tick box, under the interactive chart's "Auto" config that would allow both Axis to be scaled the same amount (That of the highest value).
Cheers,
Stephen
Currently users have the option of outputting to a PNG image but currently can only use Inches to get the size set. I want to be able to output with a pixel size not in inches.
I would like to be able to connect to an AWS EMR resource.
And an AWS gov cloud endpoint.
While doing Find replace with the following settings,
The output limits to the number of characters comes with "Replace source". If the number of characters in "Replace Found Text With Value" is more than the source then it will truncate the value to source. I feel it's not correct.
Suggesting, that there should be an option to overwrite the "field size" or keep as it coming from source.
A lot of business processes require encryption and decryption, for either data transfer or authentication processes. It would be great if Alteryx could expose some of the C# encryption functions from the System.Security.Cryptography library, as either functions in the Formula tool, or as new tools.
I know that some of these algorithms require byte input, so a new tool might be the sensible option, so that user can pass various data types that are pre-coded to byte arrays before going into the algorithms.
I get the following message when running a macro with the Render tool inside
" Alteryx ppt testing1 (162) Tool #26: You have found a bug. Replicate, then let us know. We shall fix it soon."
I believe this happens when there is multiple line breaks next to each other and trying to put this into the render tool outputting to powerpoint within a table.I have the formula for updating the line breaks "Replace([Layout],"<br />","<br />")" which works when there aren't very many line breaks but now I have integrated Python to regex out HTML the Render tool has stopped working
Migrate old R based charts and create new statistical charts in the interactive chart tool to provide enhanced statistical charting and visual data exploration capabilities.
This includes:
This these URLs for more examples:
User | Likes Count |
---|---|
7 | |
4 | |
4 | |
3 | |
3 |