How to combine disparate data streams into a single view of Salesforce data. This quick tutorial will show you how, using real-world examples.
In this brief and engaging tutorial video, Xplenty Solutions Engineer Teri Morgan provides clear, concise instructions that will keep multiple Salesforce Organizations in sync.
Morgan clearly outlines each step necessary to combine data sets from multiple Salesforce instances. Creating packages, running them, and scheduling package updates are each clearly explained using real-word use cases.
Any company with multiple Salesforce instances will find this an invaluable resource for combining disparate data streams into a single view of their Salesforce. Salesforce users responsible for reporting and data management will find this quick, simple tutorial a handy resource as they create and schedule package updates.
[00:00:00] Hi there. My name is Teri Morgan, and I'm a solutions engineer with Xplenty. Lots of businesses store valuable information in Salesforce; likely your company is one of them. Often they need to move that data around within Salesforce. Perhaps you need to move data from one object to another. Maybe your company has more than one Salesforce instance and you need to move data back and forth between them.
[00:00:40] I have even worked with large corporations where the parent company has one Salesforce and in its portfolio, each company has their own Salesforce. The parent company wants its Salesforce to be the one source of truth, where they can run company-wide reporting.
[00:00:54] Consequently, they need each of the portfolio company’s data synced in their Salesforce.
[00:00:59] How would we do this? Let me walk you through a quick demonstration.
[00:01:11] Okay, we would start by building a package. This package is going to be named Salesforce Accounts because we're going to be bringing in the account objects.
[00:01:23] First we need to add those Salesforce source components; one for each portfolio company.
[00:01:37] This one is going to be company one.
[00:01:48] We'll select all the fields and save the component. Now our parent company would like to add a company ID for each of these companies so that they can keep each of the [00:02:00] data sets straight. In Xplenty, one of the best features is our transformation layer using the code free transformation components.
[00:02:13] Customers can do everything they want from standard SQL unions, joins; clones to parsing, hashing, or encrypting data, even on a field level. We're gonna use the select component to add that company ID. We'll start by bringing in all of our fields.
[00:02:42] Then we want to add that extra field. So for company number one, it's ID will be one zero zero one
[00:02:56] and we will save that. Now we need to duplicate [00:03:00] these one for each of the portfolio companies.
[00:03:13] Then we're going to go in and change the source of that data so that it's specific to this portfolio company. This one is two. Okay. Here we go. Now we've still got our account object. Still got all those fields. Perfect.
[00:03:45] This ID is going to be one zero zero two.
[00:03:58] This is company three [00:04:00] it's source of data. Come from it's Salesforce. Still the account object. Still those fields. Save it.
[00:04:20] Its ID will be one zero zero three. Okay. And finally
[00:04:33] company four. Select its data source, still the account object, still all those fields.
[00:04:54] Its ID, you guessed it, one zero zero four.
[00:05:00] Now we need to combine these data sets. We're going to use this easy no-code union component and combine the data from company one and company two. Auto fill all of those fields and save. Now we're going to do the same thing for companies three and four.
[00:05:37] And finally, we’ll union those two data streams together.
[00:05:50] At this point, we're ready to send all of that data into the parent's Salesforce instance.
[00:06:02] [00:06:00] We're going to choose its Salesforce. Our target object is the account, and we're going to upsert.
[00:06:16] Bring in all of those fields, meaning this component, and we're going to save it. So at this point now we have a data pipeline built that will bring in all of the account objects from each of those portfolio companies and update the parent object with it. Go ahead and save that. We're going to come back here to our package editor.
[00:06:43] So we've built that here. Now we can come in and choose to duplicate that same package because maybe we want to bring in not only the account object, but maybe we want to bring in leads and opportunities. Okay. [00:07:00] So we're going to rename these.
[00:07:08] This will be our leads package.
[00:07:21] This one will be opportunities.
[00:07:27] Now at this point, you would need to go back into those packages and change the objects from accounts to opportunities and leads. But for the sake of time, we're going to pretend that we've already done that. Now we would like to create a new package. This is going to be our Salesforce update package.
[00:07:46] Actually, let's name it Salesforce Workflow, because that's what it's going to be. It's going to be a workflow instead of a data flow. In Xplenty, a workflow, this feature allows us to add [00:08:00] logic between multiple packages so that we can set up a series of packages to run successfully based on completion, based on failure.
[00:08:09] We're going to do that now; we are going to run our first package. Let me select which package that is. Let's say we want the accounts. There's going to be our accounts package. We are going to update the accounts first. And then when that runs successfully, now we would like to update the leads next.
[00:08:45] Once the leads update has completed, we're going to update opportunities.
[00:09:01] [00:09:00] So now we have each of these individual packages that will run in succession. Let's save this workflow. Now we're ready to schedule it so that it can just run automatically. We'll create a new schedule for it. Let's say that we want this package, this workflow to run every two hours. That'll give us enough frequency so that our parent Salesforce can remain updated with all of the portfolio company’s Salesforce. We'll add the workflow to this schedule.
[00:09:45] Save that. And we're just going to turn that schedule on once we've created that that will automatically start running and update every two hours. [00:10:00] This is a pretty common use case that I come across. Most recently, I had a client that was in this same boat. For the sake of his privacy,
[00:10:07] I'll call him “Andy.” Andy was really struggling with the amount of manual effort that he was spending in Salesforce. He was frustrated because he felt that his role wasn't adding value to the organization. It got to a point where even his boss was questioning the amount of impact Andy was bringing to the company.
[00:10:24] He was terrified that he might lose his job at the next round of layoffs. Fortunately, Andy solved his problem by automating the manual work he was doing in Salesforce by using an ETL platform. By doing so, he was able to save 15 hours of manual effort per week, which enabled him to devote more time to restructuring the reporting process
[00:10:47] his company used. This created a dramatic increase in his output, which he was able to concentrate on greater timeliness and accuracy in the reporting process. There was so much [00:11:00] improvement that after completing this project, Andy is now being considered for promotion. I wish him the best of luck. He has my full support moving forward, because I know this is a key element to their business.
[00:11:12] If you think there's an opportunity for Xplenty to help you solve a similar problem, I'm more than happy to discuss it with you. Please reach out to me at X-Force@xplenty.com. Thank you.