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.
What is the user attempting to do: Migrate workflows with gallery data connections from Server A (existing Alteryx server) to Server B (new Alteryx server) using a script or migration workflow.
For this to work the same gallery data connections must be created on both Server A and Server B. The XML for each Workflow being migrated contains a data connection ID provided by MongoDB. This needs to be updated in each workflow with the data connection ID of the matching connection on the target server (Server B). The customer is using a workflow which unpackages each workflow, changes the data connection ID to the residing server and repackages the workflow again. This still fails during runtime with the following error:
"Unable to translate alias"
Why does this fail? The __TemporaryAlias.xml file is not created during runtime for workflows directly downloaded and uploaded to the gallery (in other words without designer intervention). The __TemporaryAlias.xml contains data connection information used to translate the alias against the gallery data connection on the target server (Server B). For more information on Gallery data connections please click here
Important: There are many scenario's where "Unable to translate alias" errors can occur. This article is specific to migrating workflows with gallery data connections.
If for any reason the __TemporaryAlias.xml file is not available, Alteryx will try to use the GalleryAlias.xml file on the target server to validate the connection. The GalleryAlias.xml file resides in the windows user profile which must have an active connection to this resource (data connection). The following instructions should be completed on Server B (target server) to overcome the "Unable to Translate Alias" error.
1. Create a windows service account and assign in Alteryx System Settings (If a Run As account already exists please move to step two). Assign the service account with the appropriate Run as permissions. The customer may need to liaise with their IT Administrator for this task. *Please note: The Alteryx service will restart once saved.
2. Create an account in Gallery and share gallery data connections with this service account. If you are using Window Authentication, simply log into the gallery as the service account to create the user.
5.Once complete the customer should then modify data connection id's in the workflows XML to match the new server (Server B).You can manually modify this in the XML however customers in the past have used migration workflows or scripts to automate this process. Please see sample snippet of the workflow XML showing the connection id. This may appear multiple times so be sure to change all references.
You can use MongoDB input tool to find the all data connection ID. You will need this information when replacing the values above. Please query the "AlteryxGallery" Database and "DataConnections" collections.Be sure to check "include Mongo_Id field" to display connection in the results pane. See configuration below:
6. Once completed the error message will not appear when the workflow is migrated and run on Server B
*Please note that if your customer has a multi-node environment, these steps should be repeated on all worker nodes.