Sync data between Solutions (Applications) | Voters

Sync data between Solutions (Applications)

in progress

Tony

Ability to sync data between two applications that are in different solutions.

Requirements:

When data in app 1 is updated, update data in App 2.
When data in app 2 is updated, update data in app 1.
Ability to select and map the fields to be updated.

Created by Jon Darbyshire

May 16, 2022

Grant Beckmann

This feature seems like it's been in development for a long time. Was it abandoned? Would love to see it come to life.

Alex Stoica

Any updates about this feature?

David Monahu

Would this feature allow an automation to retrieve data from a field in a different solution or table? Currently I have a "client services" solution where tasks have a "client field" that is a linked record from the client info table.

Say I want to create an automation to create a new task each month and assign it to a specific client - automations don't work as they can't seem to retrieve those values from the linked record field which is annoying... if this solves that - amazing!

Mariah Pelley-Smith

Yes please, this would decrease the need for have 1000 linked records and lookups!

The show home company

Can't wait for this :D

Joe Downey

Any updates? This has been in progress since July 2022. An update would be appreciated.

Barbora Vackova

Any release date update on this? desperately waiting :)

Alex Stoica

Would be fantastic!

Emmanuel Aydin

Any update on this? This ability would very much be appreciated.

Patrick

Emmanuel Aydin: Yes it is possible with a couple automation set up:
1: create a linked record field
2: Create record ID fields in both apps (it is a featured field)
3: Have matching field types for information you would like to send
4: When a record is created in app A send it to App B 
(Also have what I call an Auto stop field with a default: so for example if the record is created in app A The default is Client Created: So when you create that automation it only sends the records with the default that is client created) - Also be sure to send the title field into the linked record field created between the 2 apps
5: When a record is created in app B send it to app a and mark that auto stop field the non default option so that when a record is created in app b it doesn't send it back to app A... That same auto stop field will need to be in place in app B so the reverse duplication doesn't happen
Now you have a 2 way connection that states when a record is created in app a within app a and not an automated record from app B-> send to app B and the same which is when a record is created in app b that is not auto created from app a -> send to app a
6: now you will create an automation in both application that states when a record is updated-> update a record in the connected app. You will use the find record option to do this and you will use the record ID from app A to the lookup field record ID of app a in app b. you will then do the reverse. 
You now have created a 2 way creation and 2 way updating between 2 different applications that can be in 2 different solutions.
You can set conditions and variations of fields that you want filled in as well if needed. 
Word of advice: create a naming structure in your automation log- since it is alphabetical now you can do this like 
1 Master automations
2 Internal aurtomations
3 client automations
etc....
Because the automations can add up and if you automations triggers others you start having a ton of variables and you have to test for user created scenarios that makes sense to them, but contradicts the intended use of the way it was built

Benjamin Bachman

Is there any update on the timeline for this? It seems like this feature request has been around awhile.

→