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.
I have created a workflow which uses a Input Data connection that reads a SQL server database. The connection is created in Alteryx Designer by selecting the connection from the Gallery. When saving the workflow to the Gallery, I set the workflow to use my specific credentials so that it can be scheduled.
When running the workflow in the Gallery manually, it works fine. However, if I schedule the workflow it suddenly complains to not be able to translate the alias as per the screenshot below
I've read the troubleshooting guide but it does not seem to address this case, or am I missing something?
If I'm not mistaken, the alias are both user and machine specific. Try scheduling this on your machine (with your credentials again) and see if that does the trick. If this works, you might need to configure the alias on the worker machine, or change the connection type to an ODBC.
Not sure if the Gallery connection is shared with the Studio you are part of, or if it is shared directly with you (as a User). I've faced similar issues: I (Curator) would share the connection with the Studio I'm part of, use that connection in my Designer and publish the workflow. When I ran the workflow manually from my Private Studio, it would run fine. But when I schedule it, I would get 'Unable to translate alias' error.
I then shared the connection directly with me (User not Studio), and I was able to schedule the workflow. Not sure if this is a bug or feature, but connections shared with Studios do not seem to work when workflows are scheduled, whereas connections shared directly with individual users seem to work when workflow are scheduled.
This post saved me hours of headache and debugging. I ran into this exact same issue and changed the permission on the Data Connection from using the studio to the individual user. Thanks much for the help!
I echo @RonnieH 's comment about this being a bug. Has this been reported to the Dev team?
This is a known defect that we are planning to have resolved by early next year at the latest. The friction caused by having to share to each user individually is definitely something we want to get out of your way!