Translation Layer for an Inter-app pipeline.
Hey Qrew! Question for your expertise. I have a request from my userbase to create a number of pipelines to help transmit a request from one app to another. The gist is, when a request in system A...
Forum Discussion
100% correct, I have been kicking myself all day. But these systems were made for folks who were fairly fierce in their defense of wanting to be independent. Moving forward, I will 100% be standardizing.
I wish they were the same, but naming conventions and fields per site/site contact vary between app A and B/C. So extra layer of confusion there.
I might have to just standardize across all the apps, at least as far as naming and nomenclature go.
MarkShnier__You
Qrew Legend
Qrew LegendWell, I suggest that you get someone higher up in the organization like head IT or some department decree that we are going to have centralized tables for common information like contacts and sites and customers. Things like that. Then you tell everybody not to worry that everything will be transitioned on a calm orderly basis.
Then I suggest you create a table in a dedicated app, perhaps called shared tables app, and have that be the source of truth. You can start that off by copying one of the tables in one of the apps that has the best data.
Then you create connected Sync tables in the various apps to replicate that every hour.
Than any of the applications you make the relationships to these new connected sync tables
Then you can write a pipeline to walk through the existing sites and contacts in these various apps and try to match up those names the best it can with names taken from a new relationship to the connected sync table. Then you have humans deal with the ones that the pipeline could not match up.