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
Alteryx offers the ability to add new formulae (e.g. the Abacus addin) and new tools (e.g. the marketplace; custom macros etc) - which is a very valuable and valued way to extend the capability of the platform.
However - if you add a new function or tool that has the same name as an existing function / tool - this can lead to a confusing user experience (a namespace conflict)
Would it be possible to add capability to Alteryx to help work around this - two potential vectors are listed below:
- Check for name conflicts when loading tools or when loading Alteryx - and warn the user. e.g. "The Coalesce function in package CORE Alteryx conflicts with the same function name in XXX package - this may cause mysterious behaviours"
- Potentially allow prefixes to address a function if there are same names - e.g. CoreAlteryx.Coalesce or Abacus.Coalesce - and if there is a function used in a function tool in a way that is ambiguous (e.g. "Coalesce") then give the user a simple dialog that allows them to pick which one they meant, and then Alteryx can self-cleanup.
Currently : the "Label" element in the Interface Designer Layout View is a single line text input.
Why could it be impoved : the "Label" element is often used to add a block of text in an analytical application interface. And adding a block of text in a single line text input is **staying polite** quite the struggle.
Solution : make this single line text input a text box just like the formula editor.
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! :)
In a similar vein to the forthcoming enhancement of being able to disable a specific output tool, my idea is to have the inverse where you can globally disable all outputs and then enable specific ones only. This should help reduce the number of clicks required/avoid workarounds using containers to obtain this functionality and allow users to be very specific in which outputs run and don't run as required.
Hello all,
As you may know, Alteryx use the Active Query Builder component. However this component itself evolves with cool new features :
https://www.activequerybuilder.com/blog/2018-04-28-much-faster-visual-sql-query-building-in-the-new-...
You can also try the online demo
https://www.activequerybuilder.com/
Best regards,
Simon
It would be great if we could add example workflows to our macros, accessible in the same way as from the original tools (example hyperlink shown after single-clicking on a tool in the tool palette or when searching in the search bar).
There is a post on how to do it for custom tools How to add an example link in the custom tool (alteryx.com). The way described there has limitations and does not seem to work on macros: I was able to get the link to show up, but nothing happens when I click.
My suggestion, make it easy to add an example workflow to a macro, like it is to change the logo or add a help link.
As per a recent discussion (https://community.alteryx.com/t5/Alteryx-Designer-Discussions/Geopackages-Can-Alteryx-Open-GeoPackag...), please add the GeoPackage datatype to the Input tool.
For reference, the open-source project ogr2ogr has this functionality. (https://gdal.org/programs/ogr2ogr.html)
Thanks!
The Sharepoint file tools are certainly a step in the right direction, but it would be great to enhance the files types that it is possible to write to sharepoint from Alteryx.
The format missing that I think is probably most in demand is pdf. If we're using the Alteryx reporting suite to create PDF reports, it would be awesome to have an easy way to output these to Sharepoint.
https://help.alteryx.com/20213/designer/sharepoint-files-output-tool
https://community.alteryx.com/t5/Public-Community-Gallery/Sharepoint-Files-Tool/ta-p/877903
Hi
The action of the 'tab' key in configuration window recently appears to have changed from indenting to a navigation function.
The user should be able to select which action the tab key performs.
Alternatively, tab should indent and shift-tab (or alternative) navigate. I'm not the only one who would appreciate the choice.
PuffinPanic
Checkbox ability to ‘not’ output the original column on a text to columns tool
The "Manage Data Connections" tool is fantastic to save credentials alongside the connection without having to worry when you save the workflow that you've embedded a password.
Imagine if - there were a similar utility to handle credentials/environment variables.
Example Entry Tableau:
Alias | Tableau Prod |
Description | Tableau Production Server |
UserID | JPhillips |
Password | ********* |
+ |
Then when configuring a tool you could put in something like [Tableau Prod].[Password] and it would read in the value.
Or maybe for Sharepoint:
Alias | TeamSP |
Description | Team sharepoint location |
UserID | JPhillips |
Password | ********* |
URL | http://sharepoint.com/myteam |
+ |
Or perhaps for a team file location:
Alias | TeamFiles |
Description | Root directory for team files |
Path | \\server.net\myteam\filesgohere |
+ |
Any of these values could be referenced in tool configurations, formulas, macro inputs by specifying the Alias and field.
Alteryx gods,
It would make me even happier than I am now if it were possible to tailor the completion messaging in the Interface Designer when an analytic app completes.
Currently, we use rendering etc, but sometimes we simply want to be able to create a bespoke completion message.
My example is as follows:
In the app you have the option to download files, or have them emailed to you. If you choose download, the final display is the render tool with the documents listed, however, if you choose email I want nothing to show but the final window with the message "Please check your email" or something. There may be more than one option, and so being able to dynamically change these messages would be very useful.
Help me Alteryx gods, you're my only hope.
*beep boop boop*
Hello all,
In help, we can read that :
https://help.alteryx.com/current/designer/write-data-db-tool
Update/Delete is currently only supported for SQL Server ODBC connections.
I don't know about you but SQL Server is well used in transactional workload but in analytics... well... I have only used once in several dozens of context !
Maybe it would be cool to make it work on many more database?
Best regards,
Simon
How about a “Temporarily Disable Tool” feature where the tool is disabled? Just the same as the "Disable All Tools that Write Output" but would only apply to the specific tool you select. But, Instead of having to delete or cut the tool and connect around (as this can be tedious)! The feature could be applied to various preparation tools (and potentially more) to help save time.
For example, there are occasions when I might have a filter applied and would want to temporarily disable the tool only to see all results. This has been the case when I have wanted to include hospital wards (by temporarily disabling the tool) I was filtering out to review in the summarized totals.
The specific tool could have the same hashed marking as the "Disable All Tools that Write Output". The "Temporarily Disable Tool" feature could be listed when the specific tool is right clicked on. - The workflow could also prompt to show that the user has a tool "disabled" to highlight to the user.
Edit: Spelling
Hi!
Just thought up a simple improvement to the US Geocoder macro that could potentially speed up the results. I'm doing an analysis on some technician data where they visit the same locations over & over again. I'm doing a full year analysis (200k + records) & the geocoder takes a bit to churn thru that much data. In the case of my data though, it's the same addresses over & over again & the geocoder will go thru each one individually.
What I did in my process & could be added to the macro is to put a unique tool into the process based off address, city, state, zip, then Geocode the reduced list, then simply join back to the original data stream using a join based off the address, city, state, zip fields (or use record id tool to created a unique process id to join off).
In my case, the 200k records were reduced to 25k, which Alteryx completed in under a minute, then joined back so my output was still the 200k records (all geocoded now).
Not everyone will have this many duplicates, but I'd bet most data has a few, & every little bit of time savings helps when management is waiting on the results haha!
Hello,
Enhancement of 'IN' functionality (ie. in Filter tool), so using range instead of citing particular values for example:
instead [ID] IN (1,2,3,52,53,54,100,101,102) something like that [ID] IN (1-3,52-54,100-102).
I think I'm liking the new UI, but I think it's necessary to bring back save, undo and re-do buttons....
1. Frequent saving of workflows is crucial and not everyone uses keyboard shortcuts
2. The ability to undo (lots) of changes is a key part of iterating and rapidly building workflows in Alteryx and again not everyone uses keyboard shortcuts to do this.
Looks like there's potentially space to add this to the right of 'help' (I suspect this might be technically quiet difficult) or to the left of 'run', 'schedule' and 'active documents' as seen in the image below.
Out of interest, where has the 'documents' terminology come from?
It would be great if you could include a new Parse tool to process Data Sets description (Meta data) formatted using the DCAT (W3C) standard in the next version of Alteryx.
DCAT is a standard for the description of data sets. It provides a comprehensive set of metadata that can be used to describe the content, structure, and lineage of a data set.
We believe that supporting DCAT in Alteryx would be a valuable addition to the product. It would allow us to:
We understand that implementing support for this standards requires some development effort (eventually done in stages, building from a minimal viable support to a full-blown support). However, we believe that the benefits to the Alteryx Community worldwide and Alteryx as a top-quality data preparation tool outweigh the cost.
I also expect the effort to be manageable (perhaps a macro will do as a start) when you see the standard RDF syntax being used, which is similar to JSON.
DCAT, which stands for Data Catalog Vocabulary, is a W3C Recommendation for describing data catalogs in RDF. It provides a set of classes and properties for describing datasets, their distributions, and their relationships to other datasets and data catalogs. This allows data catalogs to be discovered and searched more easily, and it also makes it possible to integrate data catalogs with other Semantic Web applications.
DCAT is designed to be flexible and extensible, so they can be used to describe a wide variety. They are both also designed to be interoperable, so they can be used together to create rich and interconnected descriptions of data and knowledge.
Here are some of the benefits of using DCAT:
Here are some examples of how DCAT is being used:
As the Semantic Web continues to grow, DCAT is likely to become even more widely used.
DCAT
RDF
in our organization people are moving away from network drives to BOX for file repository and they needs to use to connect to BOX using Alteryx as an Input and Output platform where they should be able to access files to read and write.
Currently few of the users are able to use the BOX as a repository using BOX Sync tool (Map BOX as a network drive) but that is not at all useful when they try to save into a gallery and run or schedule on the gallery. A connector for BOX will be of great help.
I have developed many workflows, macros, and apps, and I have always had to find a workaround for displaying information on the user config page or user interface.
For example, I want to input 'Default text' into the Text Box interface tool, but the problem is that it does not accept any external connection.
It would be great if this tool had a Q input anchor that could accept data from a connected tool (in both single or multi-line mode) or from external input (such as a file for DropDown list or List Box tools).
User | Likes Count |
---|---|
27 | |
13 | |
7 | |
7 | |
6 |