Many people maintain valuable information in Excel files, and many organizations, like ours, also use SharePoint to store and share structured and unstructured information. We see most user-generated and maintained data in Excel files in SharePoint document libraries, and one of the great benefits of Alteryx is the ability to join that Excel data with other data sources. Unfortunately, the v11.0 Scheduler cannot resolve the UNC-style ( \\server@SSL\DavWWWRoot\site-name\document-library\filename ) addresses, so workflows that access this valuable SharePoint Excel data must be run manually. The SharePoint List Input tool can read the list-style metadata for Document Library files, but does not access the file content.
The Scheduler should be enhanced so that scheduled workflows can read Excel data stored in SharePoint Document Libraries.
Today, if I want to save a job onto the Alteryx Gallery, I need full permissions to do so and it is a manual process. For some organizations, this level of access is deemed excessive, which can make properly leveraging the Alteryx Gallery difficult. Having the ability to write a "deployment" script that could publish a workflow to the Gallery, and potentially add a new workflow to a Collection would be incredibly helpful in these cases.
As a server administrator, I would like to have more control over collections. I have a user who is in charge of a collection out of office, and we have some users who need to get to be added to the collection to run workflows. As admin of the server, I would like to be able to add users to this collection, modify permissions, modify workflows, etc. This would be necessary both for when users are temporarily out of the office as well as if someone were to leave the company.
I have been trying to scan all of the workflows that are stored in the gallery and wrote this community post about it. Some Alteryx employees reached out to me directly to see if they could help solve my problem. We ended up with a somewhat wonky roundabout solution (that I haven't implemented yet) by downloading yxzp files through the Gallery API, unzipping them, then scanning the workflows as xml. I think the process could be greatly simplified if Alteryx had a set of Introspective tools.
The introspective tools would use similar, if not the same, processes that Alteryx already has in place to pull data from the gallery/server itself. The set of tools would be most useful for Server admins or people that are trying to build meta-workflows for Alteryx to make things easier for their users. Similar to the solution to my problem above, most of this functionality can be worked around by querying the Mongo and/or scanning engine logs. The Introspective tools would simplify this process greatly, especially when it comes to joining records from the Mongo and collecting workflow-internal data.
Since the tools will have direct access to the gallery/server it would make sense that they would only be available to machines with server licensing or could be made available if the user has a high enough permission level in the gallery they are trying to obtain data from.
In regulated environments, like banks, there is a requirement to fully segment Alteryx Jobs so that people on either side of a Regulatory Wall cannot access each other's canvasses or results.
As an example:
- Public vs. private side in Broker/Dealer banks
- Compliance or HR or Finance need to be segmented from all other areas in most banks
What is needed here is for any canvasses belonging to each of these walled-off areas to be controlled so that they cannot be shared across the wall, and results cannot be viewed across these areas. This also means that the Gallery Environment needs to be capable of being segmented fully within 1 installed environment.
So, .YXI files are great, they allow a much simpler installation process of macros from the Gallery to your local machine and server.
However one problem; they are not supported to be hosted on the Alteryx Gallery. This means that in order to share .yxi files they have to be hosted on some other drive and then you have to have a workflow in the alteryx gallery which provides users with the download link.
This makes that clean process a bit less clean, and it also causes problems with big customers who cannot whitelist these share drives for which the .yxi files are hosted. I myself have had about 20 emails from one global consulting firm in the US requesting access to a macro, I can't link them to the content as they are blocked, and therefor I have to email them individually.
It's a tad tedious and ruins the 'install experience'.
If you don't know what I'm talking about you can follow my colleagues (Peter Gamble-Beresfords) blog here:
What I'm asking for is simple, support for .yxi files in the Alteryx gallery, in the same way you do with macros.
This issue relates to an inability to input data from a database where access to only certain columns is permitted. This is due to PII data being present in the data.
I am trying to pull data from one table at a time using the standard ‘Input Data’ tool.
As I do not have table level access I am explicitly specifying the column names and not using a wildcard. Please see the example below, query highlighted in yellow and the returned error in red. You will see the error message returned from Alteryx suggests a * wildcard has been used despite specifying the exact fields to pull.
Several of the Ford GDIA team and Ford HPC team have reviewed this with me and cannot assist. The HPC team believe it is a bug in Alteryx which has been reported by other users internally, that is ‘Select *’ commands being sent from Alteryx despite specific columns being outlined in the query to the data lake. As we only have access to specific fields within Ranger (due to PII data) the select * fails and returns an error.
I can confirm my ODBC connections are all set correctly as I can pull from certain tables where I have full table level access but not others. Access rights are all in place as I can use the same query on Ambari without issue.
Thank you for any assistance you can provide,
Select STATION_ID, STATION_DESC from dsc60082_qlscm_tz_db.qlsc_station limit 10
Info: Input Data (3): ODBC Driver version: 03.80
Error: Input Data (3): Error SQLPrepare: [Hortonworks][Hardy] (97) Error occurred while trying to get table schema from server. Error: [Hortonworks][Hardy] (80) Syntax or semantic analysis error thrown in server while executing query. Error message from server: Error while compiling statement: FAILED: HiveAccessControlException Permission denied: user [mhiggi37] does not have [SELECT] privilege on [dsc60082_qlscm_tz_db/qlsc_station/*]
I believe it would require turning off the queries we currently run to retrieve metadata and retrieving metadata only for the columns selected in the query.
Please submit to our Idea Center for consideration. Thanks!
Angela Ogle | Customer Support Engineer
On the workflow results window, I'd like to see a column for "Start Time". If I have a workflow that is running, I'd like to know what time it started running so I have an idea on when it might finish.
When restoring an Alteryx Gallery instance to a second box for test & dev it's highly likely that you don't want all your workflows scheduled from your production instance to run in your secondary instance.
However there doesn't currently seem to be a kill switch that you can implement up front to stop your scheduled workflows from running. The only way to disable scheduled workflows in your test gallery is to manually delete them all, which is annoying when you have hundreds.
It would be great to have a config flag to disable scheduled workflows before the service is started.
When a workflow is run manually in the gallery the user is able to enter input parameters. However when using the schedule functionality this option is not available and a separate workflow needs to be developed to dynamically derive input parameters. Effectively two separate versions of the workflow need to be created and maintained.
If this functionality could be built into a future version of Alteryx this would be of significant benefit.
Currently the Gallery's Admin API is a bit light on functionality. It only works with data connections & workflows and not regular server admin functions. Endpoints I'd love to see, but not limited to, are:
Run this workflow at 12:00 PM.
Do you mean 12:00 in Geneva or 12:00 in Michigan?
Michigan of course! I'm not in Geneva.
When the server isn't in the same timezone, confusion exists on what time is being discussed. It would be nice to automate the conversion of times to local.
Would like to see a Notification hierarchy implemented to Gallery. Currently, the settings that control notifications are at the Gallery-level....where only the admin can control, for example, notifying users if a new workflow was added to a collection they belong too. Could this setting be inherited, but then, for example, a Collection owner can implement their own notification settings that overrides the Gallery default? Using the same example as before, perhaps the Collection owner could disable notifying their Users if a new workflow is loaded to the collection.
One of the issues that we have with Alteryx jobs in prod (and also Tableau, coincidentally) is that often a canvas is built to serve a need at the time, but after a while it's no-longer needed but it continues to run and consume server resources.
Can we add the option to our server environment to request recertification that a particular job is still needed every X months.
This will achieve 2 useful purposes:
- if the job is no-longer needed then the user hits "No thank you" and it's then taken off the scheduler which reduces server loads
- Alternatively - the user may realize that this should have been handed over to a new team or owner, and they can then make this change based on the recertification prompt.
I'm pretty certain that this would help to manage the inevitable build-up that happens on server environments where jobs build up until the server starts thrashing and the admin team then need to go out to all the users to do this recert process manually.
Currently, we use Task Manager to control Alteryx Service (or command line). An administrative function within Alteryx should support graceful stopping and starting of the service as user jobs are interrupted (or can be) by our activities. While I currently post messages to users alerting them to admin activities, I am asked why Tableau can restart jobs (admin) and we can't. Other admins have asked what is "hanging" alteryx service up for a STOP command. I have explained that all jobs must be stopped in order for a quick restart of the service.
We're using a single server today (this client) and plan to add workers to the configuration. It would be helpful to know where work is running and be able to use admin functions across the servers.
we are in a dynamic team where people move from 1 project to the other that implies moving series of workflows from private studio to collections prior to sharing. I have not found other ways but to do that 1 by 1 with very limited ways to filter the flows.
Could there be, from the collection, a way to
- increase number of possibilities to filters to find the proper flows (or maybe just simply allow folders in the Private studio)
- be able to multi select the one to add / delete from / to the collection
Currently there are certain locations on server that are paginating content results:
Each of these pages require users to either know exactly what they want to find by using keyword filtering or know exactly what page they want to go to and use the bottom arrows/page numbers to navigate to that page. Ditching pagination for something more intuitive helps users that may not be as acclimated with the depth of content when there are a lot of results, and also saves users multiple click interactions to find what they want.
There are tons of solutions for this, but infinite scroll is the most user-friendly & least taxing server & client side.
https://infinite-scroll.com/ has code & examples, and jquery seems to be the most widely used implementation.
Currently Alteryx 11.x+ does not support Gallery data connections for In-DB connections, it would be nice to have these In-DB connections on Gallery thus providing ability to easily collaborate with others when using these In-DB connections. Right now we are saving to .indbc file and sharing that file.
Currently, this is completely manual with whoever is assuming the schedule creating it under their profile and then the old schedule being deleted.
This can happen often in organization where a user leaves the company or assumes a new role requiring some else to maintain those schedules. It would be convenient if there was an option to reassign the owner of a schedule to simply this process.