- SalesforceChaCha
- Posts
- 💃 3 ways to keep data in sync 🕺
💃 3 ways to keep data in sync 🕺
Say BYE, BYE, BYE to unsynchronized data 🤣
Salesforce ChaCha
October 10, 2023 • Estimated Reading Time: 5 minutes
Good morning, Salesforce Nerds! Recently I ordered an awesome book called Developing Data Migrations and Integrations with Salesforce.
One of the topics was interesting and it got me thinking a bit. 🤔
Throughout your Salesforce career, what type of integration has been the most commonly requested by your clients? 🤓
I know my answer! ✋✋
By far it’s gotta be data sync’ing 🔄, where we take data from one system and send it to another - to keep it all synced up. 🤝
This is a popular ask. 💯
As a consultant, it helps to understand 📚️ the options available when we come across this.
At least from a high-level! ✈️
Today, let’s check out the 3 ways to keep data in sync! 😁
Also, grab that ☝️ book if you nerd out over this stuff like me!
Agenda for today includes
3 ways to keep data in sync
Daily Principle
All the Memes
3 ways to keep data in sync
Today we will discuss -
💃 Unidirectional Sync🕺
💃 Bidirectional Sync 🕺
💃 Two-way Unidirectional Sync 🕺
Unidirectional Sync
A super common scenario where data flows from a source to a target 🎯.
In these types of integrations, the source system 🟰 System of Record and therefore will own the data.
The clients goal is to bring target system up to date with the source system. 💯
Be on the lookout 👀 for convo’s like:
When our sales person enters the customer’s information we need that data in our ERP.
It would really help out the servicing department if we could send this data to Zendesk.
We could automate this process in Salesforce if we could get this data out of AWS.
Prime examples of when a one-way sync is used 💪.
Bidirectional Sync
Another typical thing will happen out in the wild 😉.
This is when we need to keep the same data in sync between two systems 😮!
These can get tricky 🪄 depending on the scale of the requirement, just a fair warning 🤷!
Ultimately, both systems are considered the source and the target 🎯 and your tasked with keeping them in sync!
You’ll know this is the path when you hear 🦻 things like:
How can we make sure the shipping address is the same in both Salesforce and the ERP?
It’s important that each system reflect the same data - then go on to list a 💩-load of fields
Try to stay away 🛑 from these if you can.
The conflicts can be a headache 🤕!
Two-way Unidirectional Sync
I know … a what?! 😕😕😕
This is where you sync data in both directions but 🌴 no worries 🌴 because there’s no overlap in fields. 😎
Basically, both systems act as the source and target 🎯, but they’re:
Sending different data points entirely to each other.
Sending the same data points, but to specifically mapped fields.
The former is typically done as some hand-off ✌️ point in the process. Like, sending an order 📦️ to an ERP, then sending confirmation # back.
The latter would be like creating a field in Salesforce to specifically hold the values from the external system, even if there’s also a Salesforce field for it already. Maybe you want a phone number from the ERP brought in and displayed in Salesforce or something. 🤷♀️
It’s basically a unidirectional sync, done two times! 🧠
Daily Principle
"First say to yourself what you would be; and then do what you have to do."
and now....Your Daily Memes
What did you think about today's newsletter? |