Currently, the scheduling via designer controller is independent of the gallery. So, even after a canvas is deleted, the scheduler still continues to execute the cached version of the canvas, as long as the scheduler exists.
Note, this issue does not occur when the canvas is directly scheduled in the gallery, and only occurs when you schedule via the Designer on the controller directly.
Steps to replicate issue:
1) Publish a canvas into gallery
2)Schedule the canvas to run daily via the Designer --> Options --> View Schedules --> Select Controller --> Create new workflow and schedule
3) Delete the canvas from gallery
4) You will notice that the canvas is still getting run on the defined schedule, even though you have deleted the canvas
Observed in Alteryx 11.5.1
Golden copy of a canvas should be the version existing in the gallery. Once the gallery instance of the canvas is deleted/replaced with a new version,
All related artifacts to the old version should be marked as "Deleted"
All existing schedules should be stopped from being executed
We should continue to retain all meta data attributes and execution history related to the old version (should not be wiped out) but clearly marked as archived/deleted
All the items in the 'View' menu have useful shortcuts. For instance, I'm always using Ctrl+Alt+D for the interface designer.
It would be nice to be able to quickly check workflow dependencies; at the moment there are far too many clicks to get there given the amount they are accessed (by myself and my colleagues at least...)
Quite often the window is only required briefly to check whether absolute/relative paths are used and to see inputs/outputs. It would really improve speed and ease of use if the window could be brought up with a couple of key strokes.
I'm not sure if this will ever be possible, but I know that it would greatly benefit me and I'm sure thousands of other users. In my work place I am constantly working in a conference room and at my desk. At my desk I am wired into an Ethernet connection while in the conference room I am wireless. When I start my workflows after working with my team in the conference room, I can't go back to my desk until the workflow is finished running because I am changing internet connections and I lose connection to the databases. With the pause button it would become possible to run a workflow and then change my internet without losing connection to the databases.
Another use for this would be while testing a workflow with a new tool. There are times I run a workflow that can take a few hours, but then I realize there is a mistake somewhere in my workflow, where the data hasn't reached yet. I think it would be very helpful to be able to pause the workflow and add the new tool in, while seeing results from tools it has already passed through.
But yet again this is just an idea that relates to me, I wonder what the rest of the community thinks.
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'm only just starting to explore the python and html sdks, but I think this functionality would be really useful for Alteryx tools.
I foresee cases where a custom tool is developed and we want to install it for 20+ users. Rather than having each user manually open and install the file, and troubleshooting for each of them (which could also become challenging if we want to deploy an enhancement to a tool in the future), I'd like a method (preferably via command line) to automatically install a tool for a user without any interaction/input.
This would allow for targeted tool deployment as well as large-scale tool maintenance as custom Python tools mature in the enterprise space.
In order to debug a call to a REST API - it is often necessary to take the web call, and pop this into a web browser. Can you add a second output to a RestAPI tool (a derivative of the Download tool) that has a second output that provides the full web call that was made, including the full parameterised URL. This would make it MUCH easier to debug rest API calls.
With the amount of users that use the publish to tableau server macros to automate workflows into Tableau, I think its about time we had a native tool that publishes to Tableau instead of the rather painful exercise of figuring out which version of the macro we are using and what version of Tableau Server we are publishing to. The current process is not efficient and frustrating when the server changes on both the Tableau and Alteryx side.
Now that Alteryx releases updates to Designer every quarter I'll likely be updating my copy of Designer frequently. Meanwhile, my IT team doesn't want to have to update Server every quarter to stay compatible. Problem there is, when I create workflows in the latest version of Designer they can't run on the older version of Server, nor on the Gallery.
Some features that would allow me to work around this:
If I could elect what version I want to use when uploading to the gallery.
If instead of having to upload workflows from within Designer (which thereby opens the workflow in whatever version I have installed on my machine) I could upload workflows from the Gallery website by navigating to a folder on my directory and selecting a given workflow. That way I could open the workflow in Notepad beforehand and alter the version number to match Server.
I'm guessing this is a niche problem that few others will encounter:
Not everyone is as big a nerd as me and will insist on updating Designer each quarter
Other companies may have IT teams that update Server each quarter
You can install an admin and non-admin version of Alteryx on your machine (I plan on doing this once IT responds to my internal service request).
You could use the admin version for the latest and greatest version of Alteryx
You could use the non-admin version to match whatever version of Server IT has installed and use that to upload (first opening the workflow in notepad to manually overwrite the version number to match server)
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.
In a database, a view is the result set of a stored query on the data, which the database users can query just as they would in a persistent database collection object. This pre-established query command is kept in the database dictionary. Unlike ordinary base tables in a relational database, a view does not form part of the physical schema: as a result set, it is a virtual table computed or collated dynamically from data in the database when access to that view is requested. Changes applied to the data in a relevant underlying table are reflected in the data shown in subsequent invocations of the view. In some NoSQL databases, views are the only way to query data.
Views can provide advantages over tables:
Views can represent a subset of the data contained in a table. Consequently, a view can limit the degree of exposure of the underlying tables to the outer world: a given user may have permission to query the view, while denied access to the rest of the base table.
Views can join and simplify multiple tables into a single virtual table.
Views can act as aggregated tables, where the database engine aggregates data (sum, average, etc.) and presents the calculated results as part of the data.
Views can hide the complexity of data. For example, a view could appear as Sales2000 or Sales2001, transparently partitioning the actual underlying table.
Views take very little space to store; the database contains only the definition of a view, not a copy of all the data that it presents.
Depending on the SQL engine used, views can provide extra security.
I would like to suggest creating a fix to allow In-DB Connect tool's custom SQL to read Common Table Expressions. As of 2018.2, the SQL fails due to the fact that In-DB tools wrap everything in a select * statement. Since CTE's need to start with With, this causes the SQL to error out. This would be a huge help instead of having to write nested sub selects in a long, complex SQL code!
Under the new licensing system (licenses.alteryx.com), I don't have the ability to truly release a license seat without user interaction. Currently, I have to revoke the license and then have that user start up alteryx on their machine to complete the process. Until the user starts up alteryx, I cannot reallocate that license.
I would like the ability to obsolete a license where as soon as I click the button in the licensing portal, I can immediately reallocate that license to somebody else. This functionality existed in the previous licensing system and is not available in the new licensing system.
This appears to be a bug with either the Layout Tool or the Render Tool. When I setup two Tables using the Horizontal Layout Tool and export to Excel using the Render tool, the font size of the bottom-right cell of the first table is too large. No amount of changing the font properties within the Alteryx Reporting tools appears to fix this.