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
When using certain tools, particularly market place tools like the SharePoint input/ output etc. it would be helpful to have a quick way to find out which version is being used in a workflow. Something along the lines of an option when you right click the tool, that displays the current version would be ideal.
This would be helpful in several cases but primarily when handing over workflows. There are cases when I have multiple versions of the same tool installed so that I don't have any issues inheriting workflows. This does however, make things confusing when handing workflows back. Tool Version Labelling would solve this problem.
Regards - Pilsner
sometimes we deal with hundreds of columns and it's hard to scroll and locate a specific one in the Data panel.
In the Metadata panel it's easier to locate the fields by scrolling vertically, however it would be even easier if we could click on the 'Name' column header and have that temporarily sorted so as to quickly locate a given column. (This would be IDEA 1).
Additionally, but not necessarily dependent on IDEA1, if we could have the Record number of each of the fields in the metadata, also included alongside their respective names in the Data panel, that would make it for much easier location of particular fields in the Data panel, as users could look for a given field in the Metadata, find their 'order number' and then switch back to the Data panel and scroll directly to that number.
Additionally, column name search buttons could also be added to both Data/Metdata panels for a 'contains' like field name search.
Thanks!
I would love to see an option to run only one container without having to disable all others (and tools not in containers).
I've got workflows with MANY different queries/tools each in their own containers and some tools outside of containers. Occasionally I need to run or re-run just one of the containers (usually several times when the datastream contains Crosstab or Transpose tools where some fields/options will not populate until the workflow has previously run). Normally I'd either have to disable all other containers and/or select EVERYTHING that I do not wish to run an add them all to another container that I could then disable. An option to disable everything outside of a specific container would be most welcome and save a lot of time!
Vanilla Alteryx Chained Apps can only progress linearly, which means developers could not let users skip few applications ( or ) reach the last app in the chain ( or ) let the user select which specific app to trigger based on the requirement.
This can be bypassed by using a render tool with output as PCXML and HTML link of the Application you can trying to divert to, which does not affect the existing workflow in any way.
By using the below set of tools on any workflow/chained app you can either branch the flow of apps ( or ) you can skip a few apps in the chain.
Image 1 - Input Configuration with the flow that can be part of any existing application
Image 2 - Text Tool Configuration
Image 3 - Render tool Configuration
POC in action
Now If clicked on App 1, it would divert me to www.Alteryx.com
Keywords : Chained Applications, Chained Apps, Application Sequence, Skip Application Sequence, Branch Application Sequence, Application Order, Controlled Order, Trigger Next Application
Regards,
Maithreyan S
I love the ability to cache data. Sometimes, I've cached too far and I need to go back and alter a tool's configuration or make some other cache-destroying change. I then have to recache somewhere and sometimes the dataset is so huge it is a pain. I'd love to create multiple cache points as a safety or backup.
Currently, you can only type forward in the Description Window in the Meta Info tab. So once your description is in there for your workflow, you have to retype the information or type it in notepad and save it back in there. It would be nice if you could type on any previous line in that window.
It would be nice to also have some additional fields that appear to be common among the community, such as Data Sources and Purpose. That way you could use the Description window for version notes and any other notes for the user.
Hey team,
I like the profiling function in the browser. Unfortunately, there is not built-in export function. Would it be possible to implement a function to export the profiling results into excel and PDF?
Thanks,
Christoph
Hello all,
Here the issue : I have a workflow in my One Drive folder
In that workflow, I use a macro that writes a file with a relative path (..\6_Big_Data\EN\.csv ) :
Strangely, it doesn't work and the error message seems to relate to a folder that doesn't exist (but also, not the one I have set)
ErrorLink: Output Data (1): https://community.alteryx.com/t5/*/*/ta-p/724327?utm_source=designer&utm_medium=resultsgrid|Cannot access the folder C:\Users\saubert\OneDrive - Business & Decision\Documents\B&D_Market\6_Big_Data\EN\.
I really would like that to work :)
Best regards,
Simon
This is a question which is somehow in between Designer and Gallery ideas.
When saving a workflow to the Gallery, the user can select the Assets (elements which are also copied to the Gallery). The point in time during the save process is a bit questionable from my perspective.
Often, I develop workflows locally until they reach a state in which I want to move them to the Gallery so that they can be included in Schedules or be made available to other users. I would like to be able to select which macros or datafiles are copied to the Gallery as well much earlier in the development process. From my perspective, it would be great if the user could set the Assets settings in the "Workflow Dependencies" window as well. I propose 3 possible values for each element (macro or data file):
It could look like this:
When I open I'd workflow, I'd like the option click on "something" to see content previous created for the workflow. The content I'd use most frequently is: How was the INPUT data obtained? ALL of the Alteryx workflows I will be creating with my current employer will require some level of pre-build of the data sources. I would like to document the pre-build requirements (could be pages of text, so "comments" aren't optimal) and be able to ask for them as needed.
Optimally, this feature would accept .docx, .pdf and other standard formats. Another option would be to support a URL that would link me to the content. For my purposes, this would be even more advantageous as all of our knowledge content is on-line.
In short:
Add an option to cache the metadata for a particular tool so that it doesn't forget when using tool that have dynamic metadata such as batch macros or alteryx metadata engine can't resolve such as python tool.
Longer explanation:
The Problem:
One of the issues I often encounter when making dynamic workflows or ones that require calling external services is that Alteryx often forgets the metadata of what columns to expect. This causes the workflow to forget configuration of downstream tools when a workflow is first opened or when the metadata engine refreshes. There is currently the option to disable the metadata engine from automatically refreshing but this isn't a good option because you miss out on much of the value it brings.
Some of the common tools where I encounter this issue:
Solution:
Instead could we add an option to cache the metadata for a particular tool, this would save the metadata from the last time the workflow ran to within the workflows XML so that it persists when closed and reopened. Then when the metadata engine runs when it gets to this tool instead of resolving the metadata from the tool it instead uses the saved version in the XML. Obviously when it actually runs it would ignore this and any errors would still occur.
This could be an option in navigation pane of each tool. Mockup below:
This would make developing dynamic workflows far easier and resolve issues of configuration being lost when the metadata changes and alteryx forgets the options.
One of things I like to do is select a bunch of tools and to see the collective performance of particular part of a workflow. It would be super cool if these stats were aggregated.
I could imagine then you could run alternative solutions side by side and then just select the tools involved to compare.
Maybe this pointless but my guess is that memory usage could be as important as processing time and is probably a simple addition to the performance profiling feature.
Currently, Cache and Run Workflow cannot be used if there's a second branch of data which goes around the tool which you want to cache. This slows down intermediate runs especially in complex workflows with a lot of inter-dependencies.
For example:
If you want to cache at the formula "Do something", Alteryx will not allow this because a single temporary cache file at this tool will not be sufficient:
My suggestion is that Alteryx allows multiple cache files for one single cache event. In this case:
Proposed process:
This way, I could use Cache and Run Workflow much more often which would save me a lot of time.
When I run a Standard Workflow in the Designer, I can continue to work on other workflows, I can even run two workflows in parallel.
In contrast, when running an Analytical App in the Designer, the entire program is blocked and neither another workflow can be edited or run.
I propose to allow access to the Designer GUI also when running Analytical Apps.
Quite often, I would love to be able to use Browse tools already while the workflow is still running, if that specific Browse tool has completed (green box around). This would help to debug and save a lot of time.
In this case, the lower Browse tool would be enabled already now.
Currently, using AMP Engine will cause any workflow that depends on Proxies to fail. This includes any API workflow or any workflow with Download tool, etc.
They will all fail with DNS Lookup failures.
Many newer features in Alteryx Designer are now dependent on using AMP Engine, making those features (such as Control Containers) totally useless when running inside a corporate network that uses proxies to the outside world.
Please re-examine the difference between how a regular non-AMP workflow processes such traffic vs how AMP does it, because AMP is broken!
Similar to being able change the parameters of a tool using the interface tools, it could be very useful if Alteryx Designer had an option where the configuration of a tool can be modified by another tool's output (which can only consist of one row & column and may include line breaks/tab characters, only first row is used if there are multiple rows) while the workflow is running, therefore reducing the need to chain multiple apps.
This feature could be made possible as the "Control Containers" feature is now implemented, and it could work like below:
Suppose you need to write to a database and may need to specify a Pre-SQL statement or Query that needs to be dynamically changed by the result of a previous tool in the workflow.
In this case, as the configuration of a tool in the next container needs to be changed by the result of a previous formula, there would need to be an additional icon below the tools, indicating that the tool's result can be used for configuration change.
This icon which will appear below the tools will only be visible once at least one Control Container and an Action tool is added to the workflow, and will automatically be removed if all the control containers are removed from the workflow. User can change the configuration of the destination tool using an action tool, which must be connected to a tool in a container that will be run after the one it is contained in has finished running, as a tool (or several tools) that is contained in the next CC in the workflow needs to be dynamically modified before the container it is contained in is activated.
If a formula tool containing multiple formula fields is added to the action tool, the user will see all the formula outputs similar to connections (i.e. [#1], [#2]...) that can be used as a parameter.
The screenshot below demonstrates the idea, but please note that this is a change where adding an action tool may not mean that this workflow will need to become either a macro or an analytic app, so a new workflow type may or may not have to be defined, such as "Dynamic Configuration Workflow (YXDW)". Analytic Apps and Macros which utilize this feature could still be built without having to define a new workflow type.
Hi!
Under User Settings, if you could add options to change what Alteryx shows in the tool configuration window. Currently, it shows Field, Type, Size, Rename, Description. I've been using Alteryx for almost 20 years, I've never used the Description field for anything. If Alteryx provided the option to remove it from the view for users who never use it, then the Rename field would no longer get truncated, which is a field I think is more widely utilized.
There are certain constants available for use with the tools supporting formula, WorkflowFileName being one of them. This makes it possible to i.e. capture the date information in the workflow name using RegEx to dynamically filter a field by this information (especially useful in Analytic Apps).
Based on this example, I think it would be useful to make it possible for the users to use the container's name as a constant (such as CurrentContainerName), especially when it is necessary to add a hardcoded value to several tools and update the values i.e. periodically or client-based. This would also make it easier to track the hardcoded values used in the tools.
User | Likes Count |
---|---|
11 | |
8 | |
4 | |
3 | |
3 |