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
Given Crew Macro Pack increases Alteryx's capability so much, and is used so pervasively, is there a reason to not include Crew Macro Pack in Alteryx Designer or Alteryx Server by default?
Can anyone give a reason why Alteryx wouldn't bundle Crew Macro Pack?
If not, can we get Crew Macro Pack bundled into Alteryx and have official support for it?
I propose another wildcard, %ErrorLog%, that would simply output the error codes and narratives instead of having to use the %OutputLog% to see these. I'd rather not have a 4 MB text email depicting every line of code and action in the module when all I really need to see are the errors.
In the community and in mixed teams - it's very common for people to be caught on the error that "This document was created in a more recent version". Although there are several workarounds (e.g. this one from @WayneWooldridge here https://community.alteryx.com/t5/Alteryx-Knowledge-Base/Adjusting-Alteryx-Files-for-Different-Versio...), this seems like it may be an easy problem to solve more permanently.
Could we add an option to Alteryx to save the file with the lowest compatible version number?
So - for example - if i'm only using components that shipped with version 10, then please mark the file as version 10. If I've used a tool that shipped in 11.0.6 then that needs to be the version number.
This way - files will be back-compatible as far as is possible by default unless using newer components.
Many thanks
Sean
Roughly, in all versions of Alteryx Designer, you can use the Annotations tab and rename a tool. This is awesome for execution in designer, because you can then easily search for certain tool names, better document your workflow, and see the custom tool name in the Workflow Results.
However, when log files are generated, either via email, the AlteryxGallery settings, or an AlteryxEngineCMD command, each tool is recorded using only its default name of "ToolId Toolnumber", which is not particularly descriptive and makes these log files harder to parse in the case of an error.
Having the custom names show in these log files would go a long way towards improving log readability for enterprise systems, and would be an amazing feature add/fix. For users who prefer that the default format be shown, this could be considered as a request to ADD renames in addition to the existing format. EG "Input Data 1" that I have renamed to "Load business Excel File" could be shown in the log as:
00:00:0.003 - ToolId 1 - Load business Excel File: 1 record was read from File Finished in 00:00:0.004
Whenever I add an interface tool, it adds a constant just like the 4 engine constants and any user constants. It would be useful if tools like the formula and filter automatically added question constants to the list for you to use. This would be identical to how user constants behave currently. Here is the before and after for visual effect:
BEFORE:
AFTER:
This functionality would allow the user to select (through a highlight box, or ctrl+click), only the tools in a workflow they would want to run, and the tools that are not selected would be skipped. The idea is similar to the new "add selected tools to a new tool container", but it would run them instead.
I know the conventional wisdom it to either put everything you don't want run into a tool container and disable it, or to just copy/paste the tools you want run into a blank workflow. However, for very large workflows, it is very time consuming to disable a dozen or more containers, only to re-enable them shortly afterwards, especially if those containers have to be created to isolate the tools that need to be run. Overall, this would be a quality of life improvement that could save the user some time, especially with large or cumbersome workflows.
One of the most common causes for Admin trauma for our central Alteryx Gallery team - is dealing with drivers that may not be on the server; or a particular worker; or on a designer.
What we're looking for, is for the Alteryx team to maintain a packaged set of drivers as a single installer - which we can download at the same location as the Alteryx designer / server versions.
This would allow us to have 1 version of all drivers across ALL designer clients; as well as on our workers and servers.
CC: @rijuthav @jithinmony @HengHe @RajK @ydmuley @revathi @Deeksha @MPistone @Ari_Fuller @Arianna_Fuller @JoshKushner @samnelson @avinashbonu @Sunder_Sriram @Rahul_Thakur @Rahul_Singh
Instead of adding a tool container to the canvas, then moving my input tool into that - it would be nice if I could just click a box for 'Disable' in the input tool properties. This would speed up things if I'm trying to test inputs one at a time; or need to disable just one specific output while I test another data stream in my workflow.
Would really love there to be a way to store environment related config variables without requiring the use of an external config 'file' that you need to bring in in every workflow.
Functionality should be similar to how the Alias manager works (although allowing aliasing of more than just DB connections)
The sort of things that would typically be included as such a variable would be:
If this could be set for different subscriptions or collections it would be fantastic. If not, at the server level would suffice.
The are a lot of SQL engines on top of Hadoop like:
My suggestion for Alteryx product managers is to build a tactical approach for these engines in 2016.
Regards,
Cristian.
Create a tool that allows user to create calculated fields for Tableau to output along with a .tde so they are available when openning the tde.
There are several situations where precalculated materialized data will visualize inaccurately in Tableau and calcualted fields need to be used.
When you click on 'Open results in a new window' or in when viewing results in the 'Results - Browse' sometimes it would be nice to have a freeze pane feature so you can pin column(s) to the left and scroll to the right.
I have several modules that need to run in sequence. Can a ksh or some other program be used to string the modules together?
So that if I have Step1.yxmd, Step2.yxmd and Step3.yxmd. 2 is dependent on 1, 3 is dependent on 2. I want to tell it the jobs to run and then to wait until that module completes, then run the next.
run Step1.yxmd
Wait
run Step2.yxmd
Wait
run Step3.yxmd
Wait
Or, if I have a group of modules that can run concurrently but subsequent jobs are dependent on all of them to finish, i can let all those jobs run and have the next step wait for those to complete to begin.
run Step1A.yxmd
run Step1B.yxmd
run Step1C.yxmd
run Step1D.yxmd
Wait
run Step2.yxmd
Wait
run Step3.yxmd
Wait
I know this is very simplistic, but hoping it shows the need. Also, we do have the scheduler set up to use, so if there is a way to set dependencies between modules within Scheduler, that might be helpful. Just haven't found anything.
Thanks!
Add an option to cancel an occurrence currently queued to run without it removing, or completing, the original schedule. Not sure if this is by design or a bug but when you cancel a workflow that's in queue, it sets the scheduled workflow to "Completed" even though you just wanted to stop that occurrence and still keep the workflow schedule “Active”.
Also, adding an option to PAUSE a scheduled module. This is useful when you need to temporarily suspend a workflow from running, but save the hassle of re-configuring the schedule when you want to turn it back on.