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.
Do you use Alteryx in a language other than English? If so, we want to hear from you! Please help us improve the international experience of our products by participating in this 5 minute survey.
We are updating the requirements for Community registration. As of 7/21/21 all users will be required to register a phone number with their My Alteryx accounts. If you have already registered, you will be prompted on your next login to add your phone number.
I have a workflow that contains a macro and this macro uses alias to connect to db (SQL Server). Works fine on desktop and when I try publishing it to gallery, it gives an error saying "Unable to translate alias". The alias are set up correctly in gallery and shared as well, there are no issue in publishing a regular workflow that use alias.
Are there any additional steps to be taken to make a Macro work with alias?
Ok, so we opened a support ticket with Alteryx and they were very prompt in admitting that this is a known issue and also provided an elegant solution to work around the issue. Hope this is going to help everyone that gets the "Unable to translate alias" error while connecting to Gallery Data Connections from Macros.
Within the main workflow, add Input Data tools for all Gallery Data Connections referenced within the Macros. You can group all those extra Input Data tools into a container and disable the container so it won't affect your workflow. Then save the workflow back to the Gallery and run it.
Doing this will force the Gallery Data Connections used within Macros to be packed along with the workflow when saving the workflow to the Gallery allowing the Gallery to know which Data Connections you need to use.
Give it a try. It worked for us.
Kudos to Alteryx Support for providing the solution in such short time! This needs to be fixed though 🙂
I was annoyed by this issue in the last couple of days. I build a solution which will dynamically switch connections based on different scenario. I originally use a config table to dynamically change the alias and It worked perfectly from my computer but has the alias translation issue in Gallery.
Now I got an 'ugly' solution but this will keep my macro structure unchanged.
The core concept is given that gallery is not able to recognize connection alias in macro or nested macros. We could just use the native connection string. Below are my steps:
1. A config table which maintains all the connection strings, password (encrypted), and file format.
2. Use a macro to update the input/output connection detail.
See attached pics.
Really hope there is a bug-fix release for this one.
Did you had to add just empty Input tools to your workflow? I have one that uses ODBC and another, bulkload, that also uses ODBC. Does this mean that I have to add both tolls, empty, on the workflow or do I have to enter some information there as well?
Are there any plans to work on this but? We tried the workaround and have had no success. So we appear to be left with configuring System DSNs, something I've just spent a couple of months work to ensure we don't use any more.