Get Inspire insights from former attendees in our AMA discussion thread on Inspire Buzz. ACEs and other community members are on call all week to answer!

Alteryx Designer Desktop Discussions

Find answers, ask questions, and share expertise about Alteryx Designer Desktop and Intelligence Suite.

Gallery Connection Works for the Owner of Workflow; Other Users Get an "Alias" Error

ASMR
7 - Meteor

Originally posted in "Server"

 

Our client has set up an Alteryx Server in which several different users upload their own workflows and schedule as need be. Things run smoothly for the most part, but there are two specific workflows that each write data to different tables within SAP HANA (which has been set up as a Gallery connection within the server). Whenever I try to publish these workflows to the Gallery and subsequently run them, I get an "Unable to translate alias..." error for that output tool. I also can't select that output in the Manage workflow assets option when saving to the Gallery. Another user also encountered the same issue as me. 
Error message in the Gallery; same as what I see when saving the workflow within DesignerError message in the Gallery; same as what I see when saving the workflow within DesignerCan't select the highlighted tool within Manage workflow assetsCan't select the highlighted tool within Manage workflow assets

 

However, the owner of the workflow can publish these two workflows to the Gallery without any error messages. I should also note that there are other workflows on the Server that use the same Gallery connection and those run without any alias errors (and I'm not the owner of those workflows either).

 

Any ideas on what might be causing this issue, and why they are only pertinent to these two workflows? It's strange to me that a Gallery connection would work for some workflows and not for others. 

5 REPLIES 5
patrick_mcauliffe
14 - Magnetar
14 - Magnetar

When the workflows were built, was the connection already shared from the server to the user and then built into the workflow?

Or was the same Alias name used that existed on the server?

Does the system/application Windows account have the same permissions to that connection?

ASMR
7 - Meteor

I didn't create the workflow initially, but I believe your first line is the case. There are other workflows that run on the same server (which is hosted on an AWS instance) that don't encounter this issue. And this doesn't happen to the owner of this workflow, just me and (at least) one other user. 

SanjuRaghu
5 - Atom

You might be using the pre-configured connection string in the output tool. Try replacing the exiting output tool with a new one and manually enter the connection string.

ASMR
7 - Meteor

I tried that but I still get the same alias error

patrick_mcauliffe
14 - Magnetar
14 - Magnetar

Does your own account have the same level of access to HANA?

Labels