Frustrated with how to share in-db connections?

[JoeCat]

We've been struggling to get in-db connections (specifically to Postgres db) shared.   I've created a connection on the server machine, created same on my desktop, and I can successfuly run a workflow on the server (schedule run).    I make another workflow with same in-db connection Public, and other users cannot run it.  This was the root issue.

But now  as we are onboarding users to start using this in-db connection, I dont want to multiply the problem.  Do I need to be setting up OBDC connections on each of their machines.  And then when they want to publish to server, how do we ensure it all aligns.   It seems the alias matching is not enough for their identical connection work on server. 

We were able to set up the "data connections" (which appears to only be usable on the green Input Data tool set).

I've read every article and community post possible.  I really just need to understand the standard functionality, and the normal high level process by which these connections are rolled out and shared with other users and to server.  Maybe we have expectations beyond how I think this works.  Any help is appreciated.

v2023.1

[apathetichell]

Do I need to be setting up OBDC connections on each of their machines.

short is ummm. yes. yes -- you do. I'd recommend that you handle this via getting your registry entries you create for postgres db (there are about 3 .reg files)--- you can then create a script (.bat file) to use regedit to import them. You can also have this script download a specific postgres driver --- and set it up. This will create your ODBC 64 entries. This is a hard requirement to connect via ODBC on your machine. Alteryx doesn't make the rules here.  Once you have that set up --- you can use DCM or setup connections to your DB in Alteryx however you see fit -- -but the ODBC driver set up is not negotiable.