Alteryx Server Ideas

Hello all,

According to https://openlineage.io/ 

An open framework for data lineage collection and analysis

Data lineage is the foundation for a new generation of powerful, context-aware data tools and best practices. OpenLineage enables consistent collection of lineage metadata, creating a deeper understanding of how data is produced and used.

 
This is typically the open standards needed for lineage analysis and I think it will become more and more a differenciator with your competitors. As of today, DBT or Apache Airflow already supports it (as producer), Egeria or Marquez already support it (as consumer) and guys from Datahub are working on it  (as consumers)https://feature-requests.datahubproject.io/p/openlineage
So I think Alteryx should implement this standard API as a producer, it's the next big thing in Data Governance and you don't want to stay behind !

Best regards,

Simon

Hello,

Tableau has a nice Postman Collection available... it's really easy to use since you can download or forkt it on Postman and all you have to do is to write the variable values.

I would like the same thing but for Alteryx.

Best regards,

Simon

The AlteryxService internal authenticated API that the nodes use to communicate with each other for status is not accessible to customers because it is using an undocumented authentication method. The data this appears to provide would be useful to server administrators to determine the true health of the individual nodes and for reporting purposes.

API that allows to specify the workflow version to download.

I have tried so many python packages to Refresh excel Pivot table automatically through Alteryx and save the refreshed data, most of the packages are working perfectly on designer but none of them are working on server.

If we find out anyway that will refresh pivot tables of Excel through Alteryx then it will be great for us. 

Currently, the API V3 endpoints does not have anything for Data Connection Manager (DCM). Create an endpoint to allow users to add/delete/update and list data sources, credentials, and users of DCM data sources. Also include an "admin" endpoint that can list all of the above for the entire server.

The admin screen of Alteryx gallery does not have an admin function for DCM sources, its users, and credentials. This can cause visibility issues during audits of the gallery. An API endpoint can alleviate this issue until it is added to the UI.

Enhance the v3 APi for workflows - /v3/workflows/{workflowid} - to get information for first n versions and/or last n versions of the workflow.

The problem

The current API will return information about all versions of a workflow. If a workflow has several hundred versions, you'll get all version information, much of which is useless and can take a long time to process.

The (potential) solution

Allow the API to take parameters like first n versions and last n versions. This will allow the API to return only the respective version information that would be of interest to the user.

The red box in the image is the enhancement in swagger:

Hello Alteryx Developers,

It would be great if you develop a way to connect the Alteryx Designer to AWS Redshift by SSO. When i try to set this type of connection at the Simba ODBC Driver it opens the connection several times with AWS at the browser and that ruin the customer experience.

Best Regards

Danilo Benjamin

Today the v3 api requires curator access.  V3 has Getters that should work for users with API permission.  The Getter should return the objects that user has access to.   Example:   GetCredentials for a normal user with API access should return credentials that the user has access to.  Today they get a 401 auth error.

We don't want to make these users curators just to let them access the V3 api.

I have inherited admin duties, and have been running to many problems. Some of which will escalate when the subscriptions go away. 

The pages desperately need to be updated for a more streamlined admin experience.

Couple examples I came up with below. 

Naming Convention

• Allow workflow renaming without the replace function.
• Force a unique plan name across all private studios. instead of being unique on just ID.

API Access

• Allow any user who can access the module from Collections to be able to trigger it from the API using their own API key.
• Store results of "API" triggered workflows on the page.
• Groups:

• Identify Users without a group
• Identify users in more than one group
• Add multiple users at one time (Muticheck box) with filters.

User Page

• Add/remove Users to Groups
• View, add, and remove Collections from Their User Page

Collection Page

• Add Collection from the Admin collection Page

Designer "save" window.

• Give the ability on Save As & Save for the user to automatically share the plan with their collection(s).
• Default all "Workflow" assets to be unchecked by default, rather than relying on users to click "workflow options"," manage workflow assets", and then uncheck everything.

Workflow Page

• Change Owner (Can be limited to admin only)
• Add directly to collection from this page.
• Do not reset the "private data exemption" to default every time an updated version is updated.
• Allow admin users to see logs of all users who run the plan (Also add this to the admin page while you are at it)

Would like to see more flexible options for workflow run-as credential settings, both for when publishing the workflow and kicking off the job. 

Here is a thread where we discuss the limitations we are seeing when trying to publish the workflow to Gallery via an API. We would also like to see more flexibility when our users want to kick off their workflows via an API where they could pass in different run-as credentials they would like the job to run as.

Currently we can only configure questions and flow priority when using the POST API to queue workflows.

Would be good to be able be able send some of the Runtime configurations as well.

This would allow for much more flexibility.

Example

{

"questions":

[

{"name":"Test_dt","value":"1/1/2020"}
,{"name":"Test_Num","value":"53"}
,{"name":"Test_txt","value":"schedule test"}
]

, "priority": ""

"disable browse":"True"         // When running flows in production this would reduce resource usage as data will no longer be cached. Having it as a parameters would mean that we can ensure that it is disabled

,"disable output":"False"       

}

Current Fields

Possible other fields

The full question tree is not visible within the JSON object returned when requesting the 'Questions' in the .yxwz file on the Alteryx Server. There are nested questions that are visible but there is no indication that they are nested, missing label groups, tabs and no indication whether a question should be shown or hidden. This is limiting.

A full question tree in the JSON would allow for dynamic interpretation of the 'Questions' in the .yxwz file as structured through the Interface Designer.

Regards,

Ben

Currently, in order to run an app via the API, you have to have uploaded the app to your private studio. Frankly, I don't find this function useful because you have to download then re-upload an app in order to gain access to the API. The API would be more useful if when an app is shared with you (or a collection is shared with you), then it would also allow for that app to be run via API by the user it was shared with. Right now, the only person who can run the app via API is the user who originally uploaded said app. 

Hello,
One of the frustrations we have faced in using Alteryx Gallery is the question "How do we set up many users with their respective collections easily?".

If we take for an example, the scenario where a company has 300 potential users of the gallery, who are all going to login and generate a report based on their department.
In order for them not to be able to generate the reports on other departments, the report generation workflows are put into collections. The current solution to this (atleast on SAML Authentication), is for a user to sign up, and then a Curator to assign them to their given collection. This is fine for small scale solutions, but the purpose of server is allowing for large scale deployment and automation of tasks, and this is far from ideal for a larger company.

If the server is setup on Windows Authentication, the users are able to be categorised within the Windows Active Directory, and then these groups (which may pre-exist) are able to be added to the gallery straight from the AD (see here), however this is not a feature within SAML Authentication.

From my knowledge, SAML Authentication should easily allow for this functionality, and it works very similar to Windows Active Directory. I mentioned this on a call with a Customer Support Engineer, and he explained that this wasn't part of his known roadmap for the Alteryx Gallery. 

I do believe this to be an extension of a current post on the Alteryx forum, however, this details opening the API to allow for this on an API level, however I would also suggest for this to be integrated within Alteryx Gallery, as not all users are experienced with using, or building tools around, the API.
 
Cheers,
TheOC

Hi, 

I think it would be extremely useful to be able to trigger an Alteryx workflow using Power Automate. 

The main benefit I see at the moment is automatically triggering an Alteryx workflow when the input data has been refreshed.

This would also enable a Power App to be added directly to Power Bi which can simply be clicked to re-run an Alteryx workflow then refresh the Power Bi dataset. 

My team utilizes the Gallery API extensively and have found that we have processes that the API has listed as actively running, but cannot be found via the Controller's GUI.  As a gallery artisan, I can call flows via API, but cannot cancel these executions unless I reach out to the administrator group to kill them manually. 

It would be extremely helpful to add an endpoint with the ability to submit a specific job GUID and have the server/controller kill the execution of that flow and clear up the server capacity.  This could then be scheduled on a regular basis as a maintenance  task to keep the server clean.

Thanks

The publishing endpoint, a POST to api/admin/v1/workflows/, is useless whenever workflows, apps, or macros contain Gallery Data Connections.  The workflow will get published but valid Gallery Data Connections are ignored and the apps will not run.

Please add the same dependency checks against Gallery Data Connections as is performed when a workflow or app is manually published from Designer.

This might be considered a subset of the Idea Server API to extract / submit workflows.

Thank you for your consideration.
Sincerely,

David

There is a strong need for more APIs to be introduced in Alteryx Server so that our Admin teams can provide automated solutions to our users. My understanding is that a lot of these will be introduced into Alteryx Analytics Hub however, it is also needed in Alteryx Server.

I would propose that the internal APIs for Collections and Scheduler be exposed to the Admin Key/Secrets so that we can use these APIs to move our Users workflows directly to their collection or automatically schedule for them, if needed. It seems that all this would take would be to release the Authorization from internal to the Admin on the API.

APIs I am requesting be released:

• PUT .../gallery/api/collections/{collectionID}/apps/{appID}/
• POST .../gallery/api/scheduler/