This site uses different types of cookies, including analytics and functional cookies (its own and from other sites). To change your cookie settings or find out more, click here. If you continue browsing our website, you accept these cookies.
When reading and writing large data frames to/from a python script in Alteryx it seems that there are limitations to the SQLite component of the tool. Given that this selection is recommended only when the user is having issues in the python tool why is the option selected by default? A colleague and I spent a couple of hours trying to work through an issue with importing a data frame larger than 1000x1000 and once we found this option (SQLite override) and unchecked it the data was written back to Alteryx without any problems.
Hint provided by the tool, "This changes the intermediate data format between Alteryx and Jupyter from yxdb to SQLite. Use only if running into issues. See help for more details."
SQLite override is default selection
Error message provided by the tool
After unchecking the option the workflow ran without any errors.
Recommendation: the python tool should default to SQLite override unchecked
I would like the ability to take custom geographies and write them to a table in Exasol. We visualize our data with Tableau and rely on live connections to Exasol tables rather than Tableau extracts. One shortcoming with spatial is that we have to output our custom geographies as a .shp file then make a Tableau Extract. This would save us a few steps in sharing this data with our users.
We build some pretty robust maps with multiple connections and it would be great to copy the map tool and paste it with all of the connections when we want to tweak the map slightly but keep our original map. It is a regular occurrence for us to have a very detailed map grouping by trade area name and then may want to have an overview map with all of the same connections but slightly different layout. Tracking down the connections, reconnecting them and naming them accordingly takes a substantial amount of time even in the most organized of workflows. This function would be a huge time-saver. It would also be of value with joins and unions - anywhere you have multiple streams coming in.
My users love having the ability to pick objects from a reference file in the Map tool in the Interface palette. However, usually they need to pick objects that are interspersed amongst others. The Control + Left Click works great, until they pick an incorrect object. The only option is to clear the selection and start over.
Please add something as simple as Control + Left Click on a selected object will deselect it.
In the Report Map tool, I'm locked from changing the 'Background Color' menu, and the color appears to be set to R=253, G=254, B=255, which is basically white.
However, when we use our TomTom basemap, we see that the background is actually blue, despite what's listed in the Background Color window. (This goes beyond the 'Ocean' layer, and appears to cover all space 'under' the continents and ocean.) Since we oftren print large maps of the east coast, this tends to use a lot of blue ink. I've attached a sample image to illustrate this.
My solve to-date has been to edit the underlying TeleAtlas text file and change the default background (117 157 181) to white (255 255 255). Unfortunately, we lose these changes with each data update.
Could Alteryx unlock the Background Color menu, and have it affect the 'base' layer, underneath oceans and continents in TomTom maps? Not sure how it might affect aerial imagery.
Currently, the map input for an application defaults either to a global view of the United States or to a fixed boundary. Usng a chained application, it would be an extremely useful option to be able to specifiy spatial objects (points, lines, polygons) in the first application and then allow the second application to zoom in appropriately to those spatial objects. This could be done by either specifying a custom zoom level and using those spatial objects as a center through a reference layer, or by allowing the zoom's boundary to contain all the spatial objects (similar to the map reporting tools).
It would be very helpful to have hidden/interactive labels that can be utilized for an Report Map that only appear when the user is hovering over a specific part of the map. For example they only want to see the sales numbers for California, but do want to change the map. It probably makes the most sense to have this available for the HTML Report Maps. This would allow the report map to not look too crowded with labels, but still have the labels available if the user is interested in a particular part of the map. Is this something that can eventually be added to the report map tool?
When building an analytic app which uses a Map Input, please enable Interface tool functionality which would allow the app user to change the base map (roads, imagery, etc.) within the app map interface. Currently I believe the only way to accommodate different base maps in an app is to configure multiple Map Inputs – one for each base map. The resulting map interface duplication clutters up the app and opens the door for configuration errors.
I have a 1000 row excel workbook with multiple sections on the same sheet, each with a unique header. Each section has exactly 16 rows of data included. I want to pull the rows only from one specific header called "wages".
I tried using a multi-row formula and the below expression to pull only these 16 rows but it isnt working. Any ideas?
IF Contains([F1], "Wages", 1)
THEN [Row+1:Test]+1 & THEN [Row+2:Test]+1 & THEN [Row+3:Test]+1 & (... all the way to +16)
I have a very large geospatial point dataset (~950GB) . When I do a spatial match on this dataset to a small polygon, the entire large geospatial point dataset has to be read into the tool so that the geospatial query can be performed. I suspect that the geospatial query could be significantly speed up of the geospatial data could be indexed (referenced) to a grid (or multiple grids) so that the geoquery could identify the general area of overlap, then extract the data for just that area before performing the precise geoquery. I believe Oracle used (uses) this method of storing and referencing geospatial data.