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.
I really love how I can drag and drop a file directly onto the canvas from Windows Explorer and Alteryx knows to create an Input Data tool. But when I tried it with a folder today, hoping to see a Directory Input tool appear, it wouldn't do it. Could we have a similar functionality for automatically creating a Directory Input tool?
Was very happy to see the Bulk Loader introduced for Snowflake during last release. This bulk loader is specifically available for Snowflake environments that are hosted on AWS, but does not provide functionality for those environments using Azure. As Snowflake continues to build momentum, I imagine this will be a common request. Is there something in the pipeline to add this functionality?
For an interim solution, we will be working toward developing some generic scripts/snowsql to mimic that bulk load, but ultimately we'd love to have this as part of the tool.
Presently when mapping an Excel file to an input tool the tool only recognizes sheets it does not recognize named tables (ranges) as possible inputs. When using PowerBI to read Excel inputs I can select either sheets or named ranges as input. Alteryx input tool should do the same.
I didn't see it as in the Idea section, but questions and workarounds have been discussed in the community a few times (11/15, 3/18, 4/18), and suggestions seem to be just to buy the $400-600 ODBC driver from CDATA (or ZappySys), or I could use a VBA script in Excel trigger a refresh, or create my own Alteryx connector macro (great series btw, though most was beyond my understanding!)
While not opposed paying, kludging, or learning to program, they're just one more thing to build/buy, install, maintain, and break at the most inconvenient time
OData (Open Data Protocol) is an ISO/IEC approved, OASIS standard that defines a set of best practices for building and consuming RESTful APIs. OData helps you focus on your business logic while building RESTful APIs without having to worry about the various approaches to define request and response headers, status codes, HTTP methods, URL conventions, media types, payload formats, query options, etc. OData also provides guidance for tracking changes, defining functions/actions for reusable procedures, and sending asynchronous/batch requests. OData RESTful APIs are easy to consume. The OData metadata, a machine-readable description of the data model of the APIs, enables the creation of powerful generic client proxies and tools.
I am using a Dynamic Input within a Batch Macro to allow the user to read (dump) data from multiple Oracle tables with varying schemas. If a table read has 0 rows output, then an error message like the following is displayed at the end of the job execution:
Because it is always possible to return 0 rows from the read, I'd like to mute the error message. If this message is present, I don't want to STOP the macro/application. I do however want to stop the application if an ERROR Message that I care about is encountered (e.g. Output file is not defined).
Right now the PublishToPowerBI connector only publishes to "My Workspace." I manage datasets that feed reports for multiple workspaces, some of which are not necessarily personal workspaces (so there is no login associated). A drop-down that lets you select which workspace, that you are a member of, would be fantastic!
The workaround right now is to ETL in Alteryx then save the dataset out to OneDrive. You can then "Publish" the Excel sheet to Power BI natively, and the data refreshes once an hour. This works for some data, but we have use cases that need refresh rates much higher than that. Plus publishing directly to Power BI would be ideal.
The SQL Editor window could have a better presentation of the SQL code; two issues observed
First, that it's simply plain text without even a fixed-width font, much less syntax highlighting
Second, if you type in some manually formatted SQL code (e.g. with line feeds and indentation), then click on the "Visual Query Builder" button, then click back to the "SQL Editor" button, all the formatting is lost as it is converted to one run-on line of code, which is very difficult to read.
I understand that going between the Visual Query Builder and the SQL Editor is bound to have some issues; nonetheless the "idea" is to allow a user friendly display in the SQL Editor window:
Use a fixed width font, (should be trivial to implement)
My "implementation ideas" are based on a couple minutes with google, so hopefully this is a very feasible request; my user base is very likely to spend more time in the SQL editor than not, so this would be a valuable UX addition. Thanks!
Right now we can create Tableau extract files (.tde), but cannot read them into Alteryx -- this limits the partnership of these two companies. Please add the functionality to import .tde files, Best, Jeremy
Is anyone else annoyed that the default Output Options for the output tool usually need to be changed? What I've found in my couple of years of using this (wonderful) tool is that for Excel and Tableau outputs especially, the default is always 'Create new [sheet OR Extract File]'.
But when you use that option for your output tool, you can't use the Alteryx flow again; you get an error (Sheet already exists you moron, or Extract already exists stupid) (c'mon, you know Alteryx is judging you and the strikethroughs are there in spirit).
The 'stupid' is silent
If you ever want to run your workflow again, you've got to change it to 'Overwrite [Sheet (Drop) OR Existing Extract File (Create if does no Exist)]'.
I'm not sure about you, but I've been (passive aggressively?) hoping that with each new release of Alteryx, I would get a means to change my defaults. I would LOVE the option to have my output tools default to the overwrite, ratherthan create, option automatically. That one step is just... annoying to do over and over again.
So, I'm not going to be a passive-aggressive twit any longer. I am formally asking for what I want like an adult.
Can I please have an option in Options>User Settings>Defaults with a drop-down for Output tool preferences: Create by default, Overwrite by default, Append by default, and whatever the other options are generally categorised according to how the Output tools are done? I really only care about the overwrite one, but you're getting my gist at this point, right?
Please support GZIP files in the input tool for both Designer and Server.
I get several large .gz files every day containing our streaming server logs. I need to parse and import these using Alteryx (we currently use Sawmill). Extracting each of these files would take a huge amount of space and time.
This was previously requested and marked as "now available", but what is available only addressed a small part of the request. First, that request was for both ZIP and GZIP. What is now available is only ZIP. Second, it requested both input and output, what is now available is input only. Third, while not explicitly stated in the request, it needs to function in Alteryx Server in order to be scheduled on a daily basis.
It would be extremely helpful if Alteryx could add quick filters to the data browsing windows that would allow you to filter the contents of the window based on each column. Essentially just replicate what you can do with quick filters in Excel.
Without this, I'm often forced to copy my data out into Excel in order to do any detailed trouble-shooting, and often there's too much data to copy, which prevents me from quickly getting to what I need.
Of course you can create a whole separate filter object, but that's combersome and requires re-running the workflow.
Essentially, I want to update a DB table with either an update or with the deletion of rows. I can't delete all of the data. My work around will be to create/insert into a table the keys that i want to delete and try to use a input/output tool with SQL that performs the delete. Any other suggestions are welcome, but a tool is best.
In earlier versions the MongoDB Output did not pass fields with null values; this was ideal for storing individual attributes, where one person may have 4 attributes and another may have only 2 attributes, because we did not waste space storing empty or null values. The newer versions pass these fields with null values; I would like the option to not pass these fields. Please see an example below. Thank you for your consideration.