Alteryx Designer Desktop Ideas

It would be great if we could output the coefficients of regression equation to a table so that one can use them in rest of the module. Currently, Alteryx can output the table/coefficients in charts/reports form which is not re-usable as such in the module. 
The values of coefficients/Residuals/Errors would be very useful in building macros for techniques like Missing Value Analysis which can't be done in Alteryx as of now.

I would like to use the precreate statement as part of a app. That means if a user selects ID '12345' from an interface tool, I would like to delete recs in SQL server with that same ID through the pre create statement, then afterwards I would append new records with the same ID.
What I really miss is having the ability to send one Name & Value to an interface tool like label or readonly textbox.Then I could use Label/Textbox->Action->Output and change the precreate statement that way. 
I tried the formula way but SQL think I am running a stored procedure.
It looks like I need to use a listbox or dropdown tool and do it that way but that means I am cluttering my app with unnecessary tools. 
Could you give interface tools a 'hide' property or allow a field to be passed to the pre-Create SQL statement?
Unless there's another way to do all this? 

With a module that contains a lot of tool containers, it would be nice to have an option (similar to Disable All Tool That Write Output in the RunTime TAB) to disable all Tool Containers and then I can go pick the one or two that I would like to enable.

Can you add the Data Output along with the Report Output on the Association Analysis tool.  

We needed to manually change this on our end but it would be nice if in 9.5 this easy upgrade was done already...

I have a big need to input files created in a .sqlite format and also write out to files as .sqlite that contain spatial object fields.  Currently they are not recognized as spatial objects.  BlobConvert is not able to convert the spatial fields from the input correctly (it gets close) so the result is that we are unable to utilize any spatial fields from or to these files.

Possibility to deselect fields directly in the input (shape, csv, tab, etc).

 

I was wondering if anyone else in the community thought it would be a good idea for Alteryx to add the capability to import a Mapinfo raster file?  Currently you can work with MapInfo's vector .tab files but you cannot bring into Alteryx MapInfo raster .tab files.

Even if Alteryx is not able to do any spatial calculations on the raster it would still be useful to import a georegistered raster .tab file to allow the user to display lat/long referenced data on top of it.  Another way to look at it would be like alowing a user to create and use a custom reference map in the Map Report tool.

I need this functionality because I often need to display lat/long data on top of georegistered .tab floorplans (always created in MapInfo). Currently there seems to be no easy way of doing that.  The simple solution would just be able to import them and view .  Later if you could do spatial calculations on those files that would be an enormous bonus.  

Thanks,

Simon

I have several modules that need to run in sequence.   Can a ksh or some other program be used to string the modules together?  

So that if I have Step1.yxmd, Step2.yxmd and Step3.yxmd.  2 is dependent on 1, 3 is dependent on 2.  I want to tell it the jobs to run and then to wait until that module completes, then run the next.  


run Step1.yxmd
Wait

run Step2.yxmd
Wait

run Step3.yxmd
Wait


Or, if I have a group of modules that can run concurrently but subsequent jobs are dependent on all of them to finish, i can let all those jobs run and have the next step wait for those to complete to begin.  

run Step1A.yxmd
run Step1B.yxmd
run Step1C.yxmd
run Step1D.yxmd
Wait

run Step2.yxmd
Wait

run Step3.yxmd
Wait


I know this is very simplistic, but hoping it shows the need.  Also, we do have the scheduler set up to use, so if there is a way to set dependencies between modules within Scheduler, that might be helpful.  Just haven't found anything.  

Thanks!

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).

A client contacted us recently asking if there was a way to view the log file of a scheduled process during runtime.  The use case is so that if there is a runaway process, they will be able to identify at what point the process gets hung up.  

Currently, when a scheduled job is running (and logging is enabled), the log file is locked for use.  

Thanks!

Ability to adjust the underlying speeds on the roadways via the GUI and eliminate having to modify the xml file and registry OR adjust the existing speeds in Guzzler that correspond to the urban roadways to bette reflect traffic volume and the resulting drive time polygons that are created in dense urban areas.

The bak file that is automatically created (and re-created if deleted) really clutters up our folders.

Please allow us to either turn it off, or specify a different location to hold our back up files.

Thanks

 Add native support of Python, C#, and Java

Calgary CrossCount returns 1 row for every permutation and combination of possible crosscounts for the given crosscount fields.  This idea is to use the additional query criteria to limit the output of rows.

Example:  State Code = 'MI' and Mosaic Type = 'A01'  could be our Criteria.  and State Code, Mosaic Type and Gender would be our crosscount fields.

Calgary crosscount (and append) would output (51 * 71 * 4) 14,484 rows (all states * all mosaic types * all gender values)

The desired crosscount would output (1 * 1 * 4) 4 rows (MI * A01 * 4).

This is a simplified example just to demonstrate my confusion when Alteryx responded to me that the tool is working as designed.  In order to reduce the crosscount output, you must restate your query criteria in a filter post the calgary tool.  If the count of rows output exceeds a thresshold, you can't even use the tool as it will generate too many rows.

By defining criteria in the Calgary Input tool, only the desired output records are generated.  But by defining criteria in the Calgary crosscount tools, only the desired "combinations" have values plus it outputs all permutations and combinations of other non-qualifying records.

Please consider this request for an enhancement.

Thanks,

Mark

It would be helpful if the "Copy Ouput Fields and Add" default was unchecked.

Currently Atleryx just takes a flat file and create a Tableau Extract (.tde) file.  I would like to be able to to take two files and cube them together like Tableau allows me to use when I create my own Tableau Extract using Tableau.  Right now I have to export two different files into excel files and then use Tableau to cube them and create an extract that gives me more power and functionality than the extract that Alteryx provides.

Implement an option to toggle the automatic creation of the .bak file or allow a destination different than the yxmd file.
Once we have our files under code control (git) the bak file is not necessary and effectively doubles our storage usage.

It would be great if the mapping allowed point themes to be bi-variate, i.e. you could change the size of a point at the same time as adjusting its colour to show two variables on the map at once, relative to each other.

Chris

In the histogram tool, I would like the ability to specify the bins, not just the number of bins, but the values of the bins. That would be especially helpful when comparing different data sets when I want to see an apples to apples comparison across two different histograms.