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.
There are multiple reasons why a user may not be able to see a Gallery connection in Designer. Try one of these recommended actions to resolve the issue.
Confirm that the connection was shared with the user. Edit the data connection and look for the user in the Users and Studios list.
Confirm that the email address the user uses to log in to the Gallery is the same address you are using to share the connection. Ask the user to remove the Gallery from Designer and re-add it using the correct credentials.
If you are sharing the connection to a studio, confirm that the user has access to that studio.
I might be misunderstanding, but, gallery connections have a type of Gallery, not System or User.
Should they be set to System?
**********EDIT: Okay I've been having a look around. It seems that the connections can be shared with the VM correctly :) Yay! However... when I try to upload the workflows to the Gallery, I get the error that my VM can't log in; same as the one above. Weird, since that I can run the workflows using the shared connections on the VM, but can't run the workflows saved by the VM.... Any ideas?
Try entering your Domain and credentials. This could be related to workflow execution on the service layer. Basically, when a workflow or app gets run by the gallery or scheduler, it runs via AlteryxService. If you do not have credentials in that section, then the AlteryxService will use the system default to execute the workflow. The bad thing is that the system default, generally does not have access to most assets, or locations in your environment. When you actually click Run in the Designer, it is using your Windows log in credentials to make everything run correctly, when running on the Service layer and there's nothing set in Run As, it may not be able to run with access to all the things the workflow is calling for.