We have discussed on several occasions and in different forums, about the importance of having or providing Alteryx with order of execution control, conditional executions, design patterns and even orchestration.
I presented this idea some time ago, but someone asked me if it was posted, and since it was not, I’m putting it here so you can give some feedback on it.
The basic concept behind this idea is to allow us (users) to have:
This approach involves some functionalities that are already within the product (like exploiting Filtering logic, loading & saving, caching, blocking among others), exposed within a Tool Container with enhanced attributes, like this example:
The approach is to extend Tool Container’s attributes.
This proposition uses actual functionalities we already have in Designer.
So, basically, the Tool Container gets ‘superpowers’, with the addition of some capabilities like: Accepting input data, saving the contents within the container (to create a design pattern, or very commonly used sequence of tools chained together), output data, run the contents of the tools included in the container, etc.), plus a configuration screen like:
This should end a brief introduction to the idea, but taking it a little further, it will allow even to have something like an Orchestration layout, where the users can drag and drop containers or patterns and orchestrate them in a solution, like we can do with the Visual Layout Tool or the Interactive Chart tool:
I'm looking forward to hear what you think.
This has probably been mentioned before, but in case it hasn't....
Right now, if the dynamic input tool skips a file (which it often does!) it just appears as a warning and continues processing. Whilst this is still useful to continue processing, could it be built as an option in the tool to select a 'error if files are skipped'?
Right now it is either easy to miss this is happening, or in production / on server you may want this process to be stopped.
I surprisingly couldn't find this anywhere else as I know it's been discussed in person on many occasions.
Basically the Formula tool needs to be smarter in many ways, but this particular post focuses on the Data Type component.
The formula tool, should not always default to V_String as the data type when entering data or a formula into the formula tool, it should look at the data type and estimate the most likely option.
I know there are times where the logical type might not be consistent in all fields, but the Data Preview and the Function of the formula should be used to determine the most likely option.
E.G. If I type a number or a date directly into the formula tool, then Alteryx should be smart enough to change the data type from the standard V_String to Int, Double or date.
This is an extension to the ideas posted here:
I often need to create a record ID that automatically increments but grouped by a specific field. I currently do it using the Multi-Row Formula tool doing [Field-1:ID]+1 because there is no group by option in the Record ID tool.
Also, sometimes I need to start at 0 but the Multi-Row Formula tool doesn't allow this so I have to use a Formula tool right after to subtract 1.
So adding a group by option to the Record ID tool would allow the user not to use the multi-row formula to do this and to start at any value wanted.
Love the new updates to the Browse tool in 2019.2! However, if you choose the option Open results in new window, which I do often so I can see my whole dataset, the search/filter/sort functionality goes away. Would be great if that new functionality also worked in the new window. Thanks!
Can't wait for the new base maps!
In-app screens, lot of space is wasted because components/tools can just be stacked one below the other.
It would great if we could also insert them horizontally.
Tags : screen, app, macro, layout, tools, UI
When you use Create Points tool - you then almost always need to use a Select tool to rename that point.
Can we please add a single text field to the Create Points tool - which would then allow us to create and name a point in one step?
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.
We want to use 2 byte field name at Shape File on Alteryx Designer.
(e.g. UTF-8 , Shift-JIS )
Tableau v2018.3 introduced multiple table extracts. These are particularly useful for fact table to fact table joins and fact table to entitlement table joins for row-level security where the number of rows created by the join and/or size of join results would be prohibitively large. Also they are useful for fact table to spatial joins where we might have multiple spatial objects (for example custom province/district/health facility catchment) for each row of fact table data.
So in Alteryx I'd like to be able to specify 2+ tables & their join keys and then write out a .hyper multiple tables extract.
We now have the ability to output to an ESRI File Geodatabase, which is great, but it only allows you to output it to the WGS84 coordinate system. I would like to have the same functionality to export it to other projections or coordinate systems similar to the ESRI Shapefile or ESRI Personal Geodatabase output tools (we specifically need NAD83 but I'm sure others would like other options as well).
When calculating distance from a single point (or a list of points) to many other points, it can require a lot of processing time to append the single point into the same table as the multiple points (especially with very large datasets). Seems it would be more efficient to allow the single point as in input to the distance tool and bypass the timely append step.
In Designer user settings, you have the option to set a default dataset for the reference base map. This is a fantastic feature when working with spatial objects. My suggestion is that this feature should persist when viewing .yxdb files outside of Designer workflows.
When I'm browsing a folder of .yxdb files that contain spatial objects, clicking on those files opens a viewing/browse window outside of Designer. Unfortunately, the base reference map setting does not currently transfer and must be reelected each time a file is opened. I would like suggest that this setting persist in this situation.
As mention on this post here I would love the ability to change the map provider to any other map service (Mapbox, google, some other paid option). This could be achieved by adding a "Map Severs" option in the default configuration and where you put in the map server details.
Hey Alteryx Community,
I think Alteryx uses the Tableau SDK to create tableau data extracts, TDE's. Since Tableau 10.3, there is functionality to connect to spatial files in Tableau (.shp). These shapefiles can be converted to an tableau data extract within Tableau. The tableau SDK has this functionality as well, but Alteryx does not support it yet. The suggestion is to add this functionality. See https://onlinehelp.tableau.com/current/api/sdk/en-us/SDK/tableau_sdk_samples.htm for the SDK link.
Spatial TDE's are way smaller (3gb .shp went to 140mb TDE) and way faster.
I am bringing this over from this post.
It would be really cool to have a workflow that you could configure to your server that we could schedule to pull down the new Cass updates and install them. Since they have to be reinstalled every two months, it would help to manage that.
I think that the data updates are set up with an FTP site, Cass could be done essentially the same way. Download it there and then use the command module to run the install? I may be over simplifying the process but it seems like this is something that Alteryx could tackle.
First: Including mapbox in 2019.4 is GREAT!
That said, one of the great features of mapbox is the ability to customize your own map layers.
It would be great if this was an option to use a custom map as the alteryx reference map similar to what is available within tableau. We in our organization have several custom map styles built with mapbox and I'd love to use them as a reference in the report map tool, or any other scenario where maps become useful.
In order to fully take advantage of Alteryx spatial features it would be great to have the ability of using Openstreetmap extract files natively.
While there are some sources available in SHP format they tend to be heavily cut down in detail, while the native OSM and PBF have the full feature set.
As it's an open format licensing shouldn't be an issue and it may pave the way to new features.
What do you think?
We use Alteryx to extract the reports from 3D CAD system.
XYZ coordinate system is used in 3D CAD system but spatial function in Alteryx is applicable only for lat/long system.
Polygon generated by Alteryx can’t be imported into Tableau with proper scale and other useful spatial function can’t be used, neither.
It would be nice to have options to use XY coordinate system in addition to lat/long.
If XYZ, 3 dimensional coordinate system can be handled to calculate distance and overlap, that would be great.
Currently, the distance tool provides an option to calculate mileage distance (as the crow flies) between a point and the edge of a polygon, but you can only calculate drivetime to the centroid.
I'd like to see an option to calculate drivetime based on the nearest edge rather than centroid, Thanks.
We primarily work on tracking people through a store or any physical space and extract shopping trip information such as areas visited, dwell time, etc. This shopper track information consists of a series of X,Y coordinates which are also used to plot heat maps based on density of points in a given area.
I have been using a workaround due to the lack of cartesian coordinate support in spatial tools - involving converting cartesian values to Lat., Long. by dividing X,Y values by 10,000. This approach works fine for finding spatial matches between points and polygons. However, when using something like a heat map tool which requires Grid Size and Max Distance in Miles/Kilometers, since there is no support for smaller units of distance, you will not be able to generate a heatmap data file.
In addition to adding support for Cartesian coordinates, it would also be helpful to provide an option to load in a Floorplan/Image as Base Map when browsing Spatial tool results.
There are times where I create several points in a row. I then have to either add a Select tool after each to rename, or remember which is which and rename in a Select Tool after all. It would make things more efficient if I could name the output field of the Create Points Tool directly in the tool configuration.
In GIS, spatial data is regularly stored/transmitted as text. With this comes metadata, including the projection used.
Example Issue: When extracting data from ESRI's ArcGIS REST Directories, the projection can be extracted from the information, but must be manually defined in the Make Points Tool. If you are trying to compile data from several different sources, all using different projections, you cannot automate the process.
Suggested Solution: Add WKT to macro interface configuration options so that an Action Interface Tool can update the Create Points Tool.
JSON extract.png - This is a screenshot of the spatial reference metadata in a JSON formatted query from an ArcGIS REST Directory.
action tool.png - Current configuration options for Create Points Tool in the Action Interface Tool.
In working through challenge 77 it became apparent that here are a few useful formulae that would help with work like this:
Input: Point; Bearing; Distance; Units
Output: New point
Degrees to DMS:
Input: Degrees as floating point
Output: string with Degrees; minutes & Seconds
DMS to Degrees:
Inverse of the above