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 posting an alteryx job to the gallery; or packaging them for transport - any deep dependancies are lost (I think that we start to have trouble once you're 3 levels deep).
For example - you have a canvas; which uses macros; which in turn have macros; which in turn have macros.
this is not as uncommon as it may sound on the surface - due to the current lack of flow-of-control support in Alteryx; we need to wrap all of our ETL jobs in Batch Macros to force them to run in a specific order. Within these ETL jobs, it's common to decompose for lookups; master data management; etc.
Is this something that the team is currently looking into fixing - this does cause quite a bit of pain when deploying to the gallery because the jobs need to be manually stitched together and packaging does not carry the full working solution?
CC: @rijuthav; @jithinmony; @HengHe; @RajK; @ydmuley; @revathi; @Deeksha; @MPistone; @Ari_Fuller; @Arianna_Fuller; @JoshKushner; @samN; @avinashbonu; @Sunder_Sriram; @Rahul_Thakur; @Rahul_Singh
I really like the Tool Container. I also really like to have neat and tidy modules. Sometimes though, the two are in conflict because the Tool Container automatically sizes itself so I end up playing around with tool placement to get my containers the same.
Could you please add the option to make the Tool Container a sizeable object (like the Explorer Box) or give width and height value boxes in the tool properties?
Hello all,
When using in-database, all you have in select or formula are the Alteryx field types (V_String, etc..).
However, since you're mostly writing in database, in the end, there is a conversion of Alteryx field types to real SQL field types (like varchar). But how is it done ? As of today, it's a total black box. Some documentation would be appreciated.
Best regards,
Simon
We all know and love the Comment tool. It's a staple of every workflow to give users an idea of the workflow in finer details. It's a powerful tool - it helps adds context to tools and containers, and it also serves as an image placeholder for us to style our workflows as aesthetically pleasing as possible.
Now, the gensis of this idea is inspired by this post and subsequent research question here.
The Comment Tool today allows you to:
But it would provide way more functionality if it had the capabilities of another awesome Alteryx tool that is not so frequently mentioned... the Report Text Tool!
What's missing in the Comment tool that the Report Text tool has?
Now, whilst I understand that the Report Text tool is just that, a tool that needs to be connected to the data to work, so too does the Comment tool (to a lesser extent).
It would be awesome to have the ability to connect the data to the Comment tool as it was a Control Container-like connector. It can also be just like the Report Text tool with an optional input, thereby making it like a normal Comment tool.
To visualize my point:
The benefits of doing so:
I think it'll be a killer feature enhancement to the comment tool. Hoping to hear comments on this!
Kindly like, share, and subscribe I mean comment your support. Thanks all! 😁
-caltang
Quick and (hopefully) simple one here. Many times when I use the Text To Columns tool, there is still leading whitespace from comma separated lists with spaces. It would save from the minor inconvenience of putting a Data Cleansing tool after each of these tools to include an Advanced Option to trim whitespace from the results. I tried some workarounds using the empty fields and including spaces in the delimiters box, but this results in unwanted behavior.
SOOOOoooooo many times it'd be great to just dictate the character length/count (fixed width) for the parse (just like you can in excel), instead of being constrained by a delimiter or being obligated to go create (potentially complex) REGEX. Ideally you could go into the column and insert the <break> (multiple times if needed) after the given character where you'd like the parse to occur. Anything past the last <break> would all be included in the final parse section/field.
You could also do it a little less visual and just identify/type the character count you want for each column. If you really want to enhance this idea, you could also include the ability to name the fields and prescribe the data type. Those would just be gravy on the meat of the idea however, which is, provide the ability to parse by fixed length fields.
Hello all,
OLEDB is usually way faster than ODBC so that the way to connect we promote. However, the new DCM only works for ODBC connection, which is quite strange.
Best regards,
Simon
Please add XBRL - eXtensible Business Reporting Language (https://www.xbrl.org/ , Wikipedia , http://www.xbrleurope.org/ ) as output file format.
XBRL is based on XML and is used in financial word, for example all public companies in USA send their financial reports to Stock Exchange Commison in XBRL format. (http://xbrl.sec.gov/)
In Japan Central Bank and Financial Services Agency (FSA) are collecting financial data for banks and financial companies using XBRL format.
Thank you.
Regards,
Cristian
After multiple years of using Alteryx, The tabbed document feature was left out of 2022.1. This feature allows for a much cleaner canvas for exploring workflow and output data. I view this feature as a basic function of Alteryx, I was surprised to find out that the development team intentionally omitted this function. I really don't want to revert back to older versions but it may be only the way to have a more comfortable feel of Alteryx.
It would be absolutely marvellous if the ability to use a field as the replace value could be incorporated into the Regex tool. Currently the "Replacement Text" field is a hardcoded text value, and so to make that dynamic you have to wrap the tool in a batch and feed in the value as a Control Parameter. If we could just select a field to use as the replacement value, that would be spiffy.
M.
Visio is our organization's most common method of communicating business processes and workflows. Being able to export an Alteryx workflow to Visio would help us communicate the tool's functionality to process owners.
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
Hello - The Input Data tool allows you to import a list of sheet names, but it doesn't let you import a list of named ranges. I'm proposing the Input Data tool allows you to import a list of named ranges for as many Excel file formats as possible. Right now when I go to import say an xlsx or xlsm the Input Data tool allows me to select from a drop down of named ranges, so it seems the functionality is already there. I am not aware of a reasonable approach to getting a list of named ranges other than opening up the Excel file as XML, specifically xl/workbook.xml - however, I've ran into issues with this approach providing sheet names instead of named ranges (unsure why but I posted about this here https://community.alteryx.com/t5/Alteryx-Designer-Discussions/How-do-I-get-a-list-of-all-named-range...)
If we were able to import a list named ranges I think the benefits are obvious. The one that really stands out to me is that if you have a standard when creating named ranges (for example "prefix_name1, prefix_name2" etc... you could search for specific prefixes to find the named ranges available. In a large portfolio of models deploying such a standard the total universe of named ranges might not be known ahead of time except the prefix to search. I'm curious if this resonates with others.
Thank you
Add in-database tools for SAP HANA.
Please star that idea so we can prioritize this request accordingly
Alteryx is unlike many BI tools in the sense that it joins NULL. It is difficult to think of another platform that has this behaviour. Either people know about this and work around it or they don't and their joins are a ticking time bomb. Please add a check box to the Join and Join Multiple tools to allow or prevent joining NULL. This will serve to remove the need for workarounds as well as educate users about this default behaviour.
(originally raised as discussion : https://community.alteryx.com/t5/Data-Sources/Input-Data-Tool-Record-Limit-control/td-p/58718)
Hi all,
When using a record limit on a database query - the actual query being executed on the server depends very much on the connection type (Native SQL; OleDB; and ODBC). However, for all 3 of these, it seems that the record limit is being enacted on the client side, not on the server. What I mean by this is that when I take the exact queries that are being run by Alteryx on the server (by looking at a SQL Profile trace on the server), and run these in a query window, you can see that the row-limit is not occurring in SQL, but in Alteryx.
(to test this, I ran several queries with and without the record limit; profiled them using SQL profiler; and the profile trace was identical either way)
Aside from putting "Select top(100) from..." in all the queries that that we create, or using in-DB queries for every simple query - could we instead have an option to force the row limitation down to the server on a regular InputData tool, so that we can take advantage of the server's ability to optimize?
Thank you
Sean
The guide line of Shape File is below. They recommend that you use only letters and numbers.
"Spaces and certain characters are not supported in field names. Special characters include hyphens such as in x-coordinate and y-coordinate; parentheses; brackets; and symbols such as $, %, and #. Essentially, eliminate anything that is not alphanumeric or an underscore."
But many GIS tools can read and write 2 byte field name at Shape File.
(e.g. QGIS https://qgis.org/en/site/index.html)
And Esri Japan says Shape file can use 2 byte field name.
https://www.esrij.com/gis-guide/esri-dataformat/shapefile/
We want to use 2 byte field name at Shape File on Alteryx Designer.
(e.g. UTF-8 , Shift-JIS )
Thanks,
Kajitani
I'm sure there's a reason behind it, but can we please be allowed to run calculations on null values in a formula tool? right now, if we sum three values (1 + 3 + [null]) it produces [null], can the formula tool just ignore the null values? the only way around this is to fill the [null] cells with a value and that adds an additional step to what should be a fairly straight forward process. That value would have to be different for a multiplication formula vs an addition formula in order to not change the answer materially whereas ignoring the value is a more consistent solution.
In Alteryx enable connections to Oracle Databases that are configured to use External Authentication.
This should allow Alteryx workflows to connect to Oracle databases using different authentication mechanisms, e.g. Kerberos.
Please see this discussion for some analysis on what would be required in Alteryx to support Oracle Database External Authentication:
Essentially this would involve Alteryx allowing users to specify that a connection to an Oracle database will utilize external authentication.
Then when connecting to an Oracle database with external authentication, Alteryx would pass the relevant parameter to Oracle to indicate external authentication is required (and Alteryx would not pass user name and password info). Then authentication with the Oracle database would be controlled by the external authentication configuration on the computer running Alteryx.
For more information on Oracle Database External Authentication see: