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
Not sure I'd call this a user setting, but I couldn't figure out the right heading this belongs to.
When opening files, there are often times a couple of files at that aren't run on any kind of schedule or set time frame but you come back to when you need to run them.
There should be a way to set "FAVORITES" for a handful of files that you find yourself referring to on a repeated basis, but too far back to be on the 'recents' list because you open too many other files.
I can be picky about how my workflows are laid out. Oftentimes, the connector between tools has a "mind of its own" as to what direction it goes and how it crosses other objects. I'd like to see the ability to control the connector lines with "elbows" that can be positioned in custom locations and directions, like an MS Visio diagram. Alternatively, add a simple "pin" tool could be added to the canvas and it's only function is to take in and send out a connector line by defining the input and output location. The input and output locations could be defined angularly/radial in degrees, for example. Image attached below of existing workflow with a "troublesome" connector and the concept of "elbows" and "pins" added as an alternate control mechanism. Both would be great! :)
With more and more enterprises moving to cloud infrastructures and Azure being one of the most used one, there should be support for its authentication service Azure Active Directory (AAD).
Currently if you are using cloud services like Azure SQL Servers the only way to connect is with SQL login, which in a corporate environment is insecure and administrative overhead to manage.
The only work around I found so far is creating an ODBC 17 connection that supports AAD authentication and connect to it in Alteryx.
Please see the post below covering that topic:
Ok the time has come to expand functionality in the record ID tool. I would like the ability to restart the counter based on a field (e.g zip code). You can do it quickly in Tableau (see image) so why not have this functionality readily available in Alteryx? Sure, you can already do it in Alteryx - the long way - with the generate rows tool, look at previous/active row with certain condition and do +1 or something like that.
Having a simple restart counter in Record ID tool just makes sense. It's intuitve to have it there, and it's easier to use than generate rows tool. IMHO also easy to develop by Alteryx and +1 for Alteryx in gartner magic quadrant!
Pardon the length of this post, but I have been working with Alteryx since version 2.0 (11 years) and have been accumulating a wish list ever since. Some of these suggestions have been made in the past but have yet to be embraced. This is the first post for the first 'idea' but, as I said, this is a wish list that has grown since I was first introduced to Alteryx. More posts will follow.
I will break this into sections to hopefully make the suggestions easier to categorize and digest.
Application interface - Since I was introduce to Alteryx, the application interface (what is presented to users) has remained rather stagnant and, with the rumored push to adopt HTML as a replacement for pcxml, could benefit from the following additional settings. I suggest these based on the fact that dot Net classes for interface controls are readily available in Windows which allow for manipulation of each of the controls attributes.
1. The ability to set 'style' attributes for each of the interface tools in the application interface (font-family, font-style, font-size, font-weight, color, etc. This could be presented to the developer as an additional (perhaps optional button) in the Configuration panel for each interface tool as below:
These settings would be specific to the type of interface tool and to how the individual tool would layout and/or be styled relative to the application interface window. One layout option, applicable to most interface tools, would be where the label would be relative to the object itself (top, bottom, left, right). The CSS could be stored in and interpreted from the XML of the yxwz file referencing the ToolID of the Node in a section of the XML hierarchy called <CSS> or something standard. An option to alter the default CSS could be displayed with a radio button control so that if not selected, the tool would fallback to the default system CSS of the tool. This default could also be set in System settings so that a consistent interface could be defined across the enterprise.
2. Moving to the actual window that displays when the application is opened, a lot of the same concepts could be applied to the Interface Designer pane.
Attributes that could be set could include position on screen when opened, width and height of the window, and all the attributes of a dot Net form. The same radio button strategy used for individual interface tools could be employed to use or not use system defaults.
3. In the UI, it would be nice if there was additional flexibility in how the interface tools could be laid out. Along with the relative position of labels for each control, being able to layout controls horizontally as well as vertically would allow for a more organized interface.
The Radio buttons would work as normal with the Text Box controls inside each Radio button and only displaying when the button is selected.
I realize a lot of the current development in Alteryx is focused on the new Alteryx Connect and being able to attach to more data files and services. But, if there is still also a concerted effort to move from what could be considered a legacy proprietary mark up language, pcxml, to a more robust and universally accepted mark up, html and css, then, in my humble opinion, expanding the options for developers to design more user friendly and customizable applications to a standard 'style' across the enterprise, both on the desktop and in the gallery, is a worthy endeavor.
Thanks for your attention. More to follow.
Dan
At present - to identify the dependencies of your workflow - you have to go to to "Advanced Settings" to find this critical capability.
(see @MattB 's great post here: https://community.alteryx.com/t5/Alteryx-Knowledge-Base/Workflow-Dependencies/ta-p/49696 )
Could we instead move this to the workflow properties on the left hand side - this would be a more logical place to keep this info.
CC: @rijuthav; @jithinmony; @HengHe; @RajK; @ydmuley; @revathi; @Deeksha; @MPistone; @Ari_Fuller; @Arianna_Fuller; @JoshKushner; @samN; @avinashbonu; @Sunder_Sriram; @Rahul_Thakur; @Rahul_Sing
I have need to Unique my data on all fields. However, I do not know all the fields that will be in my data because of a Dynamic Select tool (or in some cases a Cross Tab tool). The Unique tool defaults to having any new fields be unchecked in its configuration. Without finding some work around, I will be unable to schedule this workflow or turn it into an app for use on the Gallery without risking duplication caused by the Unique tool that fails to capture new/different fields that may come through the data.
To solve this problem and be consistent with other tools in Alteryx, the following features need to be added to the Unique tool:
The v10 formula configuration window had two very small advantages. First, it always had an extra 'line' for another output field (no pressing '+' required). Second, it defaulted to letting you immediately begin typing the name of the next column (no need to press 'Select Column' then 'Add New Column'). I know these are minor, but every little thing counts when you're doing heavy development.
It has been brought up that the following comments were given during the beta. While I appreciate the reasoning of requiring 'obvious intention,' my personal opinion is that it is overkill in this scenario. Even for new users, the old design was quite intuitive.
"Thanks for taking the time to provide feedback! This touches a conversation topic that has been ongoing here at Alteryx. While we want workflow development to be as fast as possible, we also are trying to address the overall usability of the tool and make sure it is very clear what we intend the user to do. We decided to have the UI ask for an explicit action (pick an existing field to edit or click to add a new field) to help make those options clear, as we have found that users don't always understand from the existing tool that this is the first decision they should make when using the tool. That being said, your feedback is definitely valuable. I will be sure to bring this up as we are making improvements to the new tool and see if there's a compromise that we can make on speed vs. obvious intention. Thanks for taking the time!"
We often build very large Alteryx projects that breakdown large data processing jobs into multiple self contained workflows.
We use CReW Runner tools to automate running the workflows in sequence but it would be nice if Alteryx supported this natively with a new panel for "Projects"
Nice features for Projects could be:
When we try to call external web site from Alteryx Designer Download tool, our company proxy server failed the authentication because Alteryx uses the basic login/password authentication. This has happened to multiple applications that need to interact with external partners. Will like to request an enhancement to enable Alteryx to authenticate using Kerberos or NTLM.
porWYSIWYG - What you see is what you get...
WYSIWYG implies a user interface that allows the user to view something very similar to the end result while the document is being created.[3] In general, WYSIWYG implies the ability to directly manipulate the layout of a document without having to type or remember names of layout commands.[4]
Looking forward to have such a Reporting layout designer, embed all pictures, tables, graphs, legend, header, footer...
Just like in Qliksense and tableau...
In Alteryx 11 the formula tool got redesigned but multi-field and multi-row tools have been left as it. It would be nice to have formula autocomplete and other new features in these tools as well.
When inputting a CSV file via the Azure Data Lake File Storage tool the default behaviour is for the first row to be interpreted as data.
When reading the same file locally using the File Input tool the default behaviour is for the first row to be interpreted as headers.
Since the majority of files will include headers on the first row, it would be helpful to have the "First row contains field names" option selected by default in the Azure Data Lake File Storage tool, and this would also bring the defaults of this tool in line with the standard File Input tool.
Illustration below showing the issue:
In alterxy BI teams, we often need to hit the same data-store - however if shared connections are not adopted in the server environment, there's currently no easy way to share the connections among the team (none that I know of)
Would be great if there were a "share" button on the data connections tab in the designer, so that we could share connections with a team, or export known good connections to a file that can be kept under config-management / version control.
Thank you
Sean
It would be really usefull when we can filter fields by name and make selection. At times I have work with 300+ fields and it's really hard to scroll down to select few fields. Tableau has this feature. Wer can have this feature in select and all embedded select tools (join, append etc)
When creating a formula with the formula tool, it would be useful to be able to quickly tab into the data type column, then press D for Double and select this quickly.
Right now, you cannot use the keyboard to quickly type-ahead in this field, so every double field requires you to select, drop down, move the mouse to the bottom of the scroll window, click scroll down, then mouse back up to D for double.
(or "S" for Spatial etc - this is standard for most drop-down boxes)
User | Likes Count |
---|---|
20 | |
9 | |
7 | |
6 | |
5 |