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
Idea: Allow the user to set the data type including character field width in the Text Input tool.
The Text Input tool currently auto-senses the correct type and width of the field in a Text Input tool. However, this sometimes restricts the usage of the data downline.
Examples:
1 - I often run into the situation where I've copied some data from a browse tool and then pasted that as an input to a new workflow. Then I'll turn that workflow into a macro. But then I run into an issue where the data that comes into the macro is larger than the original width in the Text Input tool. This causes problems.
2 - The tool senses that a field containing zip codes should be numeric and then converts the data. This corrupts the data and makes me insert a Select/Formula tool combo to pad the zeros to the left.
Hello,
According to wikipedia :
A partition is a division of a logical database or its constituent elements into distinct independent parts. Database partitioning is normally done for manageability, performance or availability reasons, or for load balancing. It is popular in distributed database management systems, where each partition may be spread over multiple nodes, with users at the node performing local transactions on the partition. This increases performance for sites that have regular transactions involving certain views of data, whilst maintaining availability and security.
Well, basically, you split your table in several parts, according to a field. it's very useful in term of performance when your workflows are in delta or when all your queries are based on a date. (e.g. : my table helps me to follow my sales month by month, I partition my table by month).
So the idea is to support that in Alteryx, it will add a good value, especially in In-DB workflows.
Best regards,
Simon
95% of the times I see myself using the Directory Tool, it is only to access the FullPath content, so I immediatly add a Select tool to deselect the other attributes the tool returns.
Is there any chance to add a checkbox to only retrieve FullPath?
I couldn't find a previous idea on this, but let me know if it already exists.
Hello all, just another little QoL suggestion!
There have been a few occasions recently where I've been adding some Report Text to a Rendered output and have needed to reference the current date. However, when building a quick formula to do this, I've first needed to add a dummy field within a Text Input tool so that the Formula tool doesn't error due to no incoming connection.
I know I can create a branch off from the main dataset and just use that, but for something simple like this, I find it cleaner to isolate and generate it in this way and so it'd be great if - for situations like this - the Formula tool's input anchor was optional (obviously only when using it to create new fields).
There are likely many other examples where you may want to build a simple workflow (or branch of one), starting with a quick field generated within the Formula tool itself. However, just thought I'd raise this with a scenario I've encountered a couple of times recently.
Cheers!
Please add official support for newer versions of Microsoft SQL Server and the related drivers.
According to the data sources article for Microsoft SQL Server (https://help.alteryx.com/current/DataSources/SQLServer.htm), and validation via a support ticket, only the following products have been tested and validated with Alteryx Designer/Server:
Microsoft SQL Server
Validated On: 2008, 2012, 2014, and 2016.
This is one of the most popular data sources, and the lack of support for newer versions (especially a 2+ year old product like Sql Server 2017) is hard to fathom.
ODBC Driver for SQL Server/SQL Server Native Client
Validated on ODBC Driver: 11, 13, 13.1
Validated on SQL Server Native Client: 10,11
Please add ablity to globally, within a module, forget all missing fields.
Who needs a 1073741823 sized string anyways? No one, or close enough to no one. But, if you are creating some fancy new properties in the formula tool and just cranking along and then you see that your **bleep** data stream is 9G for nine rows of data you find yourself wondering what the hell is going on. And then, you walk your way way down the workflow for a while finding slots where the default 1073741823 value got set, changing them to non-insane sized strings, and the your data flow is more like 64kb and your workflow runs in 3 seconds instead of 30 seconds.
Please set the default value for formula tools to a non-insane value that won't be changed by default by 99.99999% of use cases. Thank you.
We all love seeing this. And, it's fairly easy to fix, just go find the macro and insert a new copy. But, then you have to remember the configuration and hope that it was simple.
With the tool that's there, the XML still contains the configuration, all that's missing is the tool path. It would be great to be able to right click and repair the path from the context of the missing macro.
Hello!
I'm submiting this idea to put other products into alteryx students program, I think that we (students) should have access to study these products (not only the Intelligence Suite, but Server as well).
Hello all,
I really love the DCM feature present in the last two releases. However, I have noticed the Generic ODBC Connection is missing :
Classic Connection Manager :
Data Connection Manager :
Best regards,
Simon
It looks like as of 2022.3, workflow tabs get shortened to a specific width. This is fine however now the asterisk that lets me know if my workflow has changed doesn't display in the tab anymore. I would have to look at the top of the screen to see this. I know this isn't a huge deal, but it would be nice to still be able to see the asterisk in the tab so that I can still know which workflows have been saved even if I am currently looking at a different open workflow. One solution may be to move the asterisk to the front of the workflow name.
Also, would users want a setting to allow them to keep full workflow names versus shortening them?
Thanks!
The bak file that is automatically created (and re-created if deleted) really clutters up our folders.
Please allow us to either turn it off, or specify a different location to hold our back up files.
Thanks
At the moment containers either expand and overlap other tools, or you have to leave space for them (defeating the original purpose of using them). Is there a way we can have the containers expansion shift the workflow so the others tools shift down / right to account for this expanision?
Hello,
More and more databases have complex data types such as array, struct or map. This would be nice if we could use it on Alteryx as input, as internal and as output, with calculations available on it.
https://cwiki.apache.org/confluence/display/hive/languagemanual+types#LanguageManualTypes-ComplexTyp...
Best regards,
Simon
After I type something into the filter box, I should be able hit enter and then it just applies my change (ie enter hits the apply button). It used to be this way, but it's not working as of 2021.2. This feels like a very tiny move in the wrong direction. Currently enter does nothing. It looks like if I hit tab twice and then enter, it finds the apply button. I shouldn't have to hit tab twice.
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.
A common problem with the R tool is that it outputs "False Errors" like the following: "The R.exe exit code (4294967295) indicted an error"
I call this a false error because data passes out of the R script the same as if there were no error. As such, this error can generally be ignored. In my use case, however, my R tool is embedded within an iterative macro, and the error causes the iterator to stop running.
I was able to create a workaround by moving the R tool to a separate workflow and calling it from the CReW runner macro within my iterator, effectively suppressing the error message, but this solution is a bit clumsy, requires unnecessary read/writes, and uses nonstandard macros.
I propose the solution suggested by @mbarone (https://community.alteryx.com/t5/Alteryx-Designer-Discussions/Boosted-Model-Error/td-p/5509) to only generate an error when the R return code is 1, indicating a true error, and to either ignore these false errors or pass them as warnings. This will allow R scripts and R-based tools to be embedded within iterative macros without breaking.
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!
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.
At present, Alteryx allows for users to run 2 versions of Alteryx at once - one installed using the "Admin Installer" and one via the "non-admin installer"
However, in corporate environments, only the Admin Installer can be used (all installers are repackaged for corporate environment / endpoint management)
This leads to a situation were we cannot run two or more different versions of Alteryx on one machine (like you can with Visual Studio or other platforms). This also prevents us from participating in the BETA program because the BETA version would overwrite the users's current version. Finally - this also makes version upgrades more risky since we cannot run the new version in parallel for a period to evaluate and identify any issues.
Request: Please can you change the installer for Alteryx to default to parallel install per version - so that a user can run 2019.1; 2019.2; and 2019.2 BETA on one machine in a way that is fully isolated (i.e. no shared components - have to be able to uninstall one instance cleanly and leave the others in a fully functional state).
Many thanks
Sean
User | Likes Count |
---|---|
29 | |
13 | |
7 | |
7 | |
6 |