Workflow Ran on Multiple Desktops

[tdavis1234]

I'm connecting to input data though an ODBC connection. Screenshot shows a username/password, but I also tried this with a "No Authentication" connection and have the same issue.

Here's my ODBC Connection. Again, I have tried with the Authentication Method of "Not Authentication" as well:

However, when my colleague opens up the same workflow, this is what he sees. 

Why would it show that his connection is invalid? I've confirmed that he has same ODBC connection access, it's just that it doesn't seem to connect when he opens up the workflow that I created on my desktop. 

[Gaurav_Dhama_]

How is she/he opening the workflow? Is she/he opening it from gallery or from the shared workflow via chat or email?

[apathetichell]

I'm not an expert on DCM --- but I am 95% sure that the DCM connection must be shared with your coworker --- if this was on server --- you can manage this from server. If this is local --- your coworker must set up their DCM connection and must use the same naming convention you used.

In the old days of ODBC and manage In-DB --- you would have to have an ODBC connection/driver and you'd have to connect this to Alteryx via manage in-db. All your coworkers --- would need the same naming conventions for connecting to use any workflow with an IN-DB tool. 

[tdavis1234]

They're opening it from the file saved on a shared drive. 

[Gaurav_Dhama_]

Ok, so they need to build the connection with server else designer wouldn’t know what that string means.

So you can go to manage connections and synchronise.

Preferably, upload this workflow and let people open it from there into their designer. That will take care of most of it.

[dreldrel]

Agree with Gaurav's idea, also you can sync your connection to the server, then share connection with your users

[KGT]

OK, I'm guessing that you don't have a server, so the centralised sharing of connections won't work and you need to handle the sharing of connections yourself. @apathetichell provided the right thing to look at above. 

The error your co-worker is seeing is because they don't have the DCM connection set up. They need to set that up on their machine as you'll have trouble sharing that without a centralised location.