Automated Solution to Fix Migrated Gallery Connections "Unable to Translate Alias"

[RPThree]

Hi All

We have been trying to perform a server migration from one environment to the others but have come across an issue with the new server not being able to recognise them due to ids being different in mongo DBs even though we have just done the server restore method as advised by Alteryx.

We were told to follow this guide by alteryx 

"Unable to Translate Alias" When Migrating Workflo... - Alteryx Community

There are over 900 odd workflows that we would have to go through manually though so is there anyone who has created an automated way for us if we create a list of old and new ids to easily find an replace in the xml of the workflows as we would need to run it on 4 nodes too.

[fmvizcaino]

Hey @RPThree ,

Keep in mind that replacing the ID is not enough. You will still need to check if the workaround adheres to your server, meaning that you will need to generate the gallery.xml manually in all of your worker nodes, and this would only apply if you are not using Gallery credentials but using a run as or service account.

I`m attaching here a simple example showing how to change the data connection ID in bulk.

Best regards,

Fernando Vizcaino