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
Hey all,
The join tool currently does not allow case-insensitive joins, but the find/replace tool does. Additionally- even if both sides are identical, the join tool will not join "Sean's house" to "Sean's house" because of the non-letter character in the middle. Finally - if one side is a string(2), and the other is a vString(200) - even if you have a single identical character on both sides you get uncertain outcomes unless you force the type
Please could you consider amending the join tool to include 3 new options or capabilities:
- Case insensitive join
- Allow full Unicode character set in join
- Full match across text types (irrespective of string size) - this would allow a string(2) value to match to a string(100) value as long as the string(100) value only has the same 2 characters in it as the string(2) value
That would remove a load of work from every text-join that's being done on every canvas we do.
Thank you
Sean
We need color coding in the SQL Editor Window for input tools. We are always having to pull our code out of there and copy it into a Teradata window so it is easier to ready/trouble shoot. This would save us some time and some hassle and would improve the Alteryx user experience. ( I think you've used a couple of my ideas already. This one is a good one too. )
The Output tool currently creates a zero-row file if you filter all the rows out (an empty file)
However - there's a very common need to say "don't generate a file at all if there are zero rows" - for example if you are generating a "Daily Details" file and there are no daily details today, you want to suppress this file. This frequently trips up newer users since the only way to suppress a zero-row output file today is to it with macros.
Could you add a flag to the output tool to "Suppress empty files" so that if there are no rows to be written, Alteryx does NOT create an empty file? This way the user can be in control of what to do with empty record sets?
Our company has a need to link a new data source in Athena. We have been able to establish a connection using the input functionality however the connection is so slow it is unusable. We need to have Alteryx build an In Database option for Athena to allow us to link our data lake to Alteryx.
Hello!
I appreciate this is a very underused element of Alteryx Functionality, however, I have noticed a few issues with the description of fields.
Firstly, if you set a description on a field within a select tool:
And then attempt to clear the description later in the workflow (in another select tool), you cannot. When you delete the description, it will clear back to the original value (in this case, 'test'):
This can be easily recreated, and can be more applicable to yxdb outputs that contain the description of fields. In that scenario, you cannot go back to the previous select tool and remove the description. The closest you can come to easily clearing the description is replacing it with a space ' '.
As a secondary issue, as current the score tool removes field descriptions and overrides the source. For example if I open the Score tool example workflow, and add a select tool/description:
You can see the meta data going into the score tool:
But unfortunately the output of the tool looks like:
Showing that it has completely removes the descriptions, and also replaced all of the 'source' information. My suggestion for this would be that it would not replace the source information or descriptions.
Thirdly - and quite a niche issue, but an int64 field specifically will break when the description differs between the data and the model.
Again, easy to recreate within the Ccore tool example workflow. Apply a Select tool to both streams, setting 'First_Years' to an int64. Within the bottom stream (the model creation), set a description, in this case, 'test':
Make sure to leave the top streams description blank.
Run the workflow, observe the error:
Error: Score (106): Score: The variable testFirst_Years is missing from the input data stream.
Interestingly, it seems to be using the description as part of the name within the Score tool, which is causing issue when the descriptions differ. My suggestion for this would be that it would not utilise descriptions at all.
Kind Regards,
Owen
Hey all,
At present, if you have an existing canvas and you want to move to a DCM Connection - you are asked something like "this will reset all of your connection details - are you sure". If you have complex queries; or pre+post SQL - then you first have to copy all of this out into Notepad before you can convert to DCM and then reconfigure it all again.
However, if you are not using DCM you can change data sources when you go into Workflow Dependancies without losing your queries etc.
Could we revisit the user experience of changing to or from a DCM connection to eliminate this "start from scratch" phenomenon - if you are converging from an existing SQL ODBC or ODB or SSVB connection to a SQL connection via DCM then it should allow you to make this conversion without losing your current configuration; and the same for any other database type.
cc: @mbarone
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
When writing a good amount of code, it is easy to get lost in a sea of parentheses. Just when you think you're all done, you get an error that can force you to scour through your code to find the missing, extra, or misplaced parenthesis.
A common feature today is to highlight a parenthesis when its partner is clicked on. This instantly lets you know if you have the wrong number of them and where.
I didn't think this was that important early on in Alteryx, at least for me. Formulas were meant to be short and easily readable at a glance. Now as I dig deeper, there's R, Python, SQL and other text-heavy inputs.
I don't need a full-fledged text editor in Alteryx, but I would love some quality of life features like parentheses matching.
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.
It would be ever so helpful and save a couple extra steps if a count distinct option could be added to the crosstab tool. Seems like a slam dunk since plain ole 'count' is already a choice.
Hello all,
DuckDB is a new project of embeddable database by the team behind MonetDB. From what I understand, it's like a SQLite database but for analytics (columnar-vectorized query execution engine on a single file). And of course it's open-source and free.
More info on their website : https://duckdb.org/
Best regards,
Simon
Dear Developers,
it would be great, if SSO would be possible for Salesforce connector.
Our company is not so much in favor distributing log-in details for a service account.
If there is already a solution in place, than perfect, but if not, I guess this functionality would be a lever to use Alteryx in our company.
Best Regards,
Johanna
when you bring in a comment box or tool container to your canvas it should come in with your preferred defaults for fill colors, font color & size, etc. I have specific color schemes to identify what my comments are for and one scheme that I use most often has font size, position & color, and background color that I have to set every time i bring in a new comment box.
I LOVE working in Alteryx it because unlike excel you set a "macro" to perform repeating operations once and then ignore them to do your real work. This concept should extend to the little things within Alteryx, i.e. settings for preferred defaults for comment boxes & tool containers.
It would be absolutely marvellous if the ability to use a field as the replace value could be incorporated into the Regex tool. Currently the "Replacement Text" field is a hardcoded text value, and so to make that dynamic you have to wrap the tool in a batch and feed in the value as a Control Parameter. If we could just select a field to use as the replacement value, that would be spiffy.
M.
Hello,
This is one thing that my OCD cannot cope with.
Some tools, like the Union tool, allow you to 'Ignore warnings', like when fields are missing.
Some other tools however don't give the option. Date time tool for instance. Sometimes I feel like yelling at Alteryx that "I know that field already exists! I want to change it!". Or the join tool, when you join on a double.
I know that these warnings don't really affect anything, and they may be useful to highlight something that may be best to be changed, but pleeeeaaassee give us a tick box or something like the union tool where we can ignore warnings. It makes my workflow messy.
(I'm on designer v 2021.1 btw, so if this has already been done, then please ignore my rant. 😁 )
Thanks
Edit: What I'm talking about
I would love to be able to see the actual curl statement that is executed as part of the download tool. Maybe something like a debug switch can be added which would produce 1 extra output field which is the curl statement itself? This would greatly enhance the ability to debug when things aren't working as expected from the download tool.
Would love to have the ability to connect S3 to alteryx using the AWS IAM role instead of needing an AWS access key/secret key.
IT will not hand out the Access/secret key so it would be great to connect to S3 without needing a password.
Currently - if someone has accidentally kept an excel file open on their desktop, Alteryx will fail to load this flow.
However, it would make more sense to open this file without read-lock as a dirty-read (equivalent of "Read Uncommtted").
This may require some interaction with Microsoft but would be worth pursuing because it prevents / eliminates an entire category of needless canvas errors.
User | Likes Count |
---|---|
16 | |
9 | |
7 | |
5 | |
4 |