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
Currently, you have two choices for Auto Configure while working on workflows:
Pros and Cons of both:
I would love to have something in between all, kind of an intelligent Auto Configure with following features:
This idea will add quite some complexity into the logic of Auto Configure but should have quite some potential to speed up editing workflows because network access and number of re-evaluated tools in each editing step will be reduced.
I would like to propose a more interactive results window. The reason is that if you click on any of the tool hyperlinks next to the messages while the output is compiling, you get trapped inside that tool's output for the entire time that the workflow runs. You do not get to see any additional workflow result/detail as it compiles until after the entire workflow is run. It would be great if a user could escape back to the main workflow's results.
For instance if I am running a fairly long or complex workflow that does not all fit on one screen...I may want to zoom in on a tool if it has a warning or error before the workflow finishes. By clicking on the hyperlink "Union(5)" the palette will zoom to Union (5) so I can see which tool is a problem.
I can see any messages attached to Union(5), however I am stuck with this view the rest of the time the workflow runs. Clicking on the canvas (or really any other action I try to take) does not take me back to the overall workflow result window.
Granted if I have an error I may want to stop the workflow altogether, but sometimes warnings may prompt further investigation once the workflow is run and I may want to get an immediate read on where in the workflow the problem is while it is still running...which inputs might I have to check etc.
When viewing results of a workflow that has Errors, could we add External error resolution data if the user clicks on the error message? Like browse everywhere it could lookup the error in help and in community posts.
cheers,
mark
One of the most frequent issues I have with my workflow is when the Join Tool reorders columns for no reason. There is an option in the configuration to have the columns revert to the incoming order. It would be nice if the workflow automatically had this set as a default, or provide a toggle option in the settings for this to happen. In many of my flows I've had to create macros to keep the integrity of the column order or remember to go into the settings of this tool and re order the columns before a workflow run.
I find it annoying that the count records and heat map macros have file inputs which point to a W drive. This will show up in workflow dependencies and can cause false alarm warnings. Since these are packaged with Designer, simply change the macros to text inputs instead of file input.
Thanks!
Whenever I start something in Alteryx Designer which takes some time (e.g. opening a workflow), and I want to do something in another application in the meantime (e.g., Explorer), Alteryx Designer repeatedly catches the Windows focus back and brings Alteryx Designer to the front, interrupting my work in the other application. And Alteryx does this really multiple time during an action (often multi times per second), not even only when finished, causing me to have to press Alt-Tab multiple times to get the other window in the front again).
First, this is annoying: If I purposely select a different tool to be in the front I want to work in that tool and not be disturbed by a different tool that catches the focus back.
Second: This cannot be good for performance. Sending the "I want the focus" signals to Windows also takes time.
Suggestion:
Switch off all requests for getting the focus in entire Alteryx Designer. Instead, the Alteryx entry in the task bar might blink once or twice in green when the background action is completed.
If there are people who like this catching focus thing, then please introduce a setting so that it's possible to switch it off.
Hello!
I like to annotate my workflows when finished, and it can be a bit of a pain to add more and more comment tools by searching for them, or going through the current right-click menu:
What would be nice is the option to right click anywhere on the canvas, and have the option of 'add comment', similar to how we have the option for 'add container' when selecting tools on the canvas.
Cheers!
When you enter a search term in the results window, it would be great if it highlighted that term in the data results window. Otherwise, it still takes work to find where your search term is located in each row.
When I proceed with this command in a python tool:
from ayx import Package
Package.installPackages(package='pandas',install_type='install --upgrade')
in Alteryx it only updates to 0.25, but the Latest version is 1.1.2.
When I would like to upgrade from the Python side i get the following:
ERROR: ayx 1.0.54 has requirement pandas<0.25.0,>=0.24.2, but you'll have pandas 1.1.2 which is incompatible.
Can you please make sure we can upgrade to the latest version of pandas without any compatibility issue?
This is important because of json_normalize. Really useful tool, available from pandas 1.0.3!
One of the common issues when you build macros is the error "the schema of macro output XXX has changed between iterations"
So the next step that we commonly follow is to put a select tool into the flow just before the macro output - and convert all the fields to a specific type; untick the "unknown" field; and then sometimes have to go into the XML to add the "Forced = true" flag into the XML so that it doesn't change over time:
Please could you add an option under the "Options" tab to force / lock down the type of every field with one click? That would eliminate dozens of clicks on every creation of a macro.
Thank you
Sean
Hi currently if you use the cross tab tool and the names of the new fields should have special characters they end up being replaced in the new headers with underscores "_", and then need to be updated in someway. It would be great if this was all done in the tool. In other words the new headers have the special characters as desired
When building a workflow with testing tools, you tend to want to be able to put these in container and then minimise this to improve readability of the workflow.
For example instead of this:
You might want to minimise the error checks like this:
However when running apart from reading through the results window, there is no immediate indicator that there is a tool inside the container that has errored:
So the feature enhancement request is to add in an exclamation marker to show the user that a tool inside has an error and you can then easily open it up and investigate further.
Containers are a great feature. They allow us to create larger workflows in smaller canvases, and manage the flow and appearance of our work. However the design whether intentional or flawed that allows the container window to interact with the layers behind it is annoying. Connection wires should not redirect within a container because of things on the canvas behind the container. Likewise if I have a container open, I should not be able to grab a tool or container behind the open container through the container canvas. Please fix this flaw.
Hi:
I believe the ability for Alteryx Designer to read from/write to parquet files will enhance its capability to serve the DSML community better. Potentially someone can design this connector as part of the App community but given the importance parquet file formats have gained as a columnar storage format (as opposed to something like Avro - which is a row storage format), Alteryx supplying native connectors to such files would be awesome.
Thank you,
Shiva Badruswamy
Principal Architect - DSML
Stratascale
When using the Sharepoint Output tool - we have seen a few situations (which are widely reported in the designer discussions thread) where the write to sharepoint fails, but no error is raised.
This often happens because of mismatch in data types, but we've also seen this for other reasons (e.g. we had this once due to column ordering). In the worst case - this can end up with the sharepoint list being emptied out if the write fails on the first item, again with no error indicator.
The Sharepoint Input and Output are very widely used as a way of giving users a very simple UI to input data that can flow into an Alteryx Canvas - so this is a very commonly used pattern in our environment.
Could we request that the Sharepoint output tool be changed to include explicit errors and warnings on write, so that the user has a guarantee that either the write took place or there was an error to reflect the issue?
Thank you.
Currently if I drag a tool onto the canvas and it has multiple input anchors, Alteryx will try to connect to the first input anchor from the output of the nearest tool I am hovering near.
However the improvement I would like to see is where there are specific tools which are required to go into each input that it 'intelligently' connects to the correct input, for example on the gif below I have a PDF input and PDF template tool (pre-computer vision), and when I bring the image to text tool in, it will try and connect the output of the template tool into the D input anchor, when the correct input is the T anchor. What this leads to is me having to delete a connection and then re-wiring which slows down the development time.
As of version 2023.1 once a workflow is locked, it cannot be unlocked. If Alteryx can unlock it, can it be made into a user option?
My idea has two parts. See the images for examples.
1. Add an option on the lock screen so the user can get an unlock passkey.
Passkey is either generated by Alteryx or set by user
2. Change the behavior when trying to open a locked file by giving the user an option to enter the unlock passkey.
Same behavior if there is no passkey
Dialog box with passkey input and cancel button if a passkey exists
This would be useful as a way to revise or edit a workflow or update the expiration date on the existing workflow without having to reload or resave a new file.
Currently in 2020.2 (but I assume all versions), when you have a workflow running and click on the Tool Name/ID (1 - in the picture below) in the results window it is then not possible to click on the canvas OR get back to the messages for the full workflow as it is then locked to that tool.
The idea is that it should be possible to get back to all of the workflow messages if you click on a tool name in the results window whilst the workflow is running.
However, a neat little tip that I found is if you click on the input, output or browse hyperlink (2 in the picture below), it will open a pop-out browse rather than show the data in the results window, meaning you can still see all of the messages)
This leads me to think that it could and should be possible to see browse anywhere data whilst the workflow is running if this is fixed. Here's a separate idea for that.
CI / CD is critical to any production level process, especially when multiple authors are contributing new features to the same workflow. Currently, multi-author editing of workflows is extremely difficult, and something that would be aided greatly by using git to control different branches of ongoing work. Luckily, that's something we can already do today! However, the ability to test before merging a pull request is critical to modern CI / CD pipelines. For this, it we need to be able to run a headless workflow from a CI / CD environment. Also, having the ability to pass in parameters to the workflow would allow for robust integration testing - something that isn't straightforward today without running on production environments.
Hi there,
When you connect to a DB using a connection string or an alias - this shows up in the Workflow Dependancies in a way that is very useful to allow you to identify impacts if a DB is moved or migrated.
However - in 2023.1, if you use DCM then the database dependancies just show up as .\ which makes dependancy management much more difficult.
Please could you add the capability to view the DCM dependancies correctly in the dependancy window?
BTW - this workflow Dependancy Window would be a great place to build a simple process to move existing DB connections to a DCM connection!
CC: @wesley-siu @_PavelP
User | Likes Count |
---|---|
19 | |
3 | |
3 | |
3 | |
2 |