Today on the Salesforce Admins Podcast, we talk to Skip Sauls, Senior Director of Product Management at Salesforce.
Join us as we chat about how Data Cloud can make it easier than ever to roll out enhancements to your org.
You should subscribe for the full episode, but here are a few takeaways from our conversation with Skip Sauls.
Pulling data from external sources is always a challenge. For one thing, it usually requires a bunch of work on the back end to get things looking the way you want them to. What’s more, it opens the door to all sorts of potential problems when things don’t match up, not to mention the extra security challenges.
That’s why I was excited to sit down with Skip Sauls. He’s the PM for Data Cloud, and he’s here to tell us how his team has made working with external data sources easier than ever before.
Data Cloud allows you to combine your external data sources with what’s in Salesforce without hacking together a series of customizations. Connectors allow you to import data from external sources as direct objects, or transform it into something more useful. You can run reports with it, use it in flows, embed it in Lightning pages, and much more, without needing to write specialized code.
Skip’s goal is to minimize the customizations you need to make and seamlessly combine your external data with what’s in Salesforce. Using Data Cloud means that you’ll be able to deploy enhancements to your org without worrying that everything’s going to break, or rebuilding it from the ground up. As Skip says, “we don’t want people to feel like they have to radically change everything in their day-to-day lives just to access something new.”
Looking forward, Skip and his team are trying to further simplify how Salesforce works with external data sources. They’re rolling out tools to minimize imports, so your data lives in one place but works the same as what you have in Salesforce. They’re also working on Remote Data Cloud, which will help you consolidate data that’s spread out across multiple orgs.
If you want to learn more about Data Cloud, I have good news for you. Skip and his team are releasing dozens of new hands-on challenges to Trailhead over the next few months. There’s never been a better time to get up to speed with everything that’s possible with Data Cloud.
Mike Gerholdt:
This week on the Admins Podcast, we’re talking lakes, well, not lake lakes, but I mean we do talk about lake-making kits, and I do think that would be a hilarious swag at Dreamforce. But Skip Sauls is back because data lakes and Data Cloud are on our mind, and he’s got a bunch of new features that he’s talking about. Not to mention, he also tells us how we can get hands-on with Data Cloud, which I’m a fan of getting hands-on anything because that really helps me understand it. That’s what we’re going to talk about.
Before we get to the episode, just want to make sure you’re following the podcast on iTunes, Stitcher, Spotify, iHeartRadio. We’re on all the podcast platforms. You don’t have to follow them everywhere. Just one, your favorite one, and then the new episodes download automatically right to your phone. Every Thursday morning, you can get up head to work or walk the dog or go for a run and get your new episode just by pressing play. With that, let’s get to our conversation with Skip.
Skip, welcome back to the podcast.
Skip Sauls:
Thanks, Mike. I’m glad to be back, and as always, glad to talk to you and to the admin community.
Mike Gerholdt:
I was looking at my notes from the last time we talked, and the last real podcast that we did was about a year ago. To me, a lot of Data Cloud stuff was brand new, and also a lot of the concepts around data lakes and data silos was a new thing. It still may be new to many people in the audience, but I think we’re starting to become even more exposed to it by just the sheer volume of amount of Data Cloud information that’s coming out, and also the number of features that now Salesforce can support. Let’s start with, what’s some of the new stuff that you’ve been rolling out in Data Cloud since we last talked?
Skip Sauls:
One of the most exciting things for the admin community is how you can now leverage data from Data Cloud in your standard Salesforce org, in your lightning pages, in your reports, in your flows. That’s been a big theme for the past year, which is, we’ve got this great technology for unifying the data, manipulating it, doing all kinds of great stuff to the data, but we now need to make it available to our customers, to our respective users. A lot of that focus is what I think is very exciting because now you can actually make use of it, and you’re not trying to write specialized code or you’re not trying to export things somewhere else. You can use it in the standard Salesforce fashions. It’s inside of fields on a form, it’s in inside of a record with related lists, it’s in a report, so it’s in all the places you would expect it to be.
Mike Gerholdt:
That’s good. A lot of the times when we hear stuff like that, when we’re not bringing the in, but we’re surfacing it, I’ve heard the term like a pane of glass?
Skip Sauls:
Mm-hmm.
Mike Gerholdt:
Okay. Just want to make sure that-
Skip Sauls:
That’s a great way to visualize it. The trick for a lot of our customers, as you know, is that you bring things in and enhance their working environments. You make them more productive, giving them better results, better KPIs, whatever that might be. We don’t want people to feel like they have to radically change everything in their day-to-day lives just to access something new. Salesforce has done a pretty good job of that over the years, of bringing things in to lighten the experience, into mobile, making things that are in a low-code, no-code fashion, and really listening to what our customers want, which is, “Make my users more productive. Give them something useful here.” They’re always interested in technology, but really, the reason people want Salesforce is because it makes them more productive. It’s a useful application architecture. That’s what, to me, is very exciting. I look forward to Data Cloud just being assumed as being part of all Salesforce, not as being an add-on or something that’s on the side, so to speak, that it’s actually just it is Salesforce, for that matter.
Mike Gerholdt:
Yeah, well, it is.
Skip Sauls:
Exactly.
Mike Gerholdt:
One of the things that’s interesting is I learned more about Data Cloud, I go back to… This was a requirement that I got way, way back when I was an admin, 2008. I remember an executive saying, “Well, this is nice and all, Mike, but how come I can’t see X?” And I remember having to explain to them, “X data is on a different server that we have on location that Salesforce doesn’t have access to.” The fear, for me, was them wanting to integrate, essentially, a data silo into Salesforce. Because back then, data integrations were just crazy. But I think there’s often, this is how I look at Data Cloud is, but how hard is it to really set up?
Skip Sauls:
That’s one thing we’ve focused on is making it so that you can bring data from pretty much any source into Data Cloud. I’ll tell you more about something else that’s even more exciting down the road, but first off, talk about the notions of connectors. You have them in various flavors where you can connect to an external source and you can pull the data in. You can do it in batch, you can do it in streaming, it can be fully scheduled, and you bring that data in either as the direct objects from the remote source or you can transform them into something more useful. You may say, “I need to do something to IT to get it in the standardized formats.” Things like dates and times, all sorts of things that you may want to… Salesforce admins are familiar with this. How do you make the data get into the shape you want?
Data Cloud has a lot of really great functionality for that. We’ve leveraged tooling from the likes of MuleSoft, Tableau, CRMA, plus the traditional Salesforce loaders and that sort of thing, and unified that in Data Cloud. We made that part of it as simple as possible, and we’re adding more and more connectors to external sites. We’ll have a very rich array. In theory, an admin can say, “I need to pull data in from…” Even something relatively obscure. There’ll be a way to do that, and in the future, even custom connectors will be possible. You’ll be able to do one that isn’t sold by Salesforce or by a partner. That all is very exciting, and that fits into the traditional model where you’re importing things in, but you’re now doing it into one place i.e. in the data cloud, as opposed into multiple places, or directly into Salesforce itself, which is the part that’s nerve wracking, as I think you were saying.
You don’t want to necessarily modify all of your existing records, so with Data Cloud, you’d bring those external sources in. You can have as many as you want to. It’s highly scalable to work with almost anything. Then you’ll bring in your data from Salesforce, you’ll have that mapped in effectively, and then you can have that unified into a single object. You look at it as being the same person, account, contact, et cetera, across all the different data sources. And you’re not having to go and manually map everything in and do all sorts of things with unique IDs and keys and that sort of thing. It’s doing a lot of the heavy lifting, and it fits very much into the standard Salesforce model of making those things easy. You’re now dealing with it at an app level, not at a lower level, in most cases. You’re not having to do that every day, trying to figure out how to get the data in.
Mike Gerholdt:
One of the things that came up in the discussion that we had of getting the data out of the silo… To be clear, it’s not that we wanted it out, it was more of we just need to reference it. I think one thing you mentioned to me that was very intriguing is because back, this is ’07, we were going to copy the data and then Salesforce could see it. But with Data Cloud, we actually don’t need to worry necessarily about that, right? It’s a feature we can set up where, if we want to keep that single source of truth and reference that glass pane, we can do that. Right?
Skip Sauls:
Exactly. The terminology you might hear is bring your own lake, bring your own code, and that sort of thing. There’s a whole class of things there. I don’t know how much I can say, because there’s some pretty cool announcements coming around this, but there’s a lot of work on making it so that you can leave the data in the external store. It could be a lake, lake house, data warehouse, traditional database, S3 buckets, wherever. You can leave a lot of those things in place, and you reference them from Data Cloud as opposed to importing them. This gets into the zero copy, no ELT mantra that you’ll hear. The basic idea is that you’re not having to actually make those copies, like you were saying. You’re not going to move it back into it. It stays in place. It stays resident in the external system. But to your apps and to your users, it looks like it’s natively in Data Cloud, and therefore natively in Salesforce.
That’s pretty exciting. There’s still the case where you might want to transform something to make it fit into the shape you want, but importantly, you don’t have to do that to this data. You don’t have to do it every time you want to try to use it. That’s what we’ve seen traditionally with Salesforce is we were always importing, whether it was into Core or into Tableau or CRMA, etc. You are always importing the data, doing stuff to it, making copies of it, and that sort of thing. As powerful as those tools were, they still required that copy, which is the part you were saying we’re trying to get away from.
Mike Gerholdt:
Yeah, copy, sync, then you had to figure out last modified, who wins, conflict resolution… That was a whole day of meetings for me.
Skip Sauls:
Exactly.
Mike Gerholdt:
It was not good. As you mentioned all this, I’m thinking just offhand, because this is how my brain works. A really fun swag item for Dreamforce would be a lake-making kit, like from the Progressive commercials. That would be hilarious.
Skip Sauls:
Yeah.
Mike Gerholdt:
I’m the only one that thinks that’s funny, I think.
Skip Sauls:
Maybe you can do that for a Dreamforce or TDX next year.
Mike Gerholdt:
Yep. “Here you go, sign up to win a lake-making kit.” One of the important things I think about not having to sync data and worry about that as a potential is also, depending on the organization and how they use the data, if they’re in a contract and there’s PII involved, then they can confidently say, “This is only stored here.” As opposed to… I remember we had to go through that with a government contract and outline all of the places that this data could appear. When we were syncing data, then it became another page and a half of documentation of how people had access to Salesforce. I think that’s really cool. You mentioned ease of use, and with ease of use, to me, that is also just how do we get the word out? How do we get people hands-on with that? What are some of the things that your team’s working on around that?
Skip Sauls:
One of the things we’re really excited about is providing hands-on challenges where you get to actually use Data Cloud directly. There’s some technology behind it, but in effect, you’re getting an org that is Data Cloud-ready, and then you can go do a trail, do a hands-on challenge at TDX or Dreamforce, maybe you’re in a course somewhere. Using that org, and in the Trailhead model, you’re running a check, have you done the work and that kind of thing. That all works perfectly. Now we’ve got that working very well. You can use this in the same way you would your standard Salesforce org. You get a DE org or something, and you start working against that. That’s very exciting. And the cool part about that is that also will power all of these modules that come from Einstein, things like Prompt Builder and so forth.
Almost everything that you’ll see for these new technologies is actually powered by Data Cloud. Even though you’re not maybe explicitly using Data Cloud for the trail or the hands-on challenge, it’s under the covers, Data Cloud being used for all the data, objects, services, and so forth. The reason that’s exciting is it’s harder than it may sound, because Data Cloud instances are not as lightweight and inexpensive as say, a Salesforce DE org. There’s a cost associated to it. They’re consumption-based. So we had to do a lot of work to figure out how to get that into a manageable state so we can offer that experience to our users and not be too much of a cost burden for us. There’s still a cost there, but it’s worth it for us to invest in our users, our customers, so they can get up to speed on Data Cloud, they’re enabled on it, and they’re also enabled on, again, I mentioned Einstein and that sort of thing. That’s very exciting.
We were hearing from people, “I like Data Cloud, I want to learn more about it, but these trails don’t let me use it.” “I don’t have Data Cloud. How can I learn more directly?” As I’ve heard you and others say, a lot of people can learn the theory from a standard trail or from docs and that kind of thing. Maybe they can pass a test, but in practice, it’s that hands-on experience that really resonates. It’s like, “I actually know what I’m doing here. I know how this behaves when I click on it. I know where to go.” And that sort of thing. That’s a really cool thing, which you’re going to see a lot of.
Our plans are to have dozens of these out over the next few months, and we have a goal of getting tens of thousands of users enabled with these hands-on challenges. That tells you the scale we’re talking about. I would encourage everybody who’s listening, go try out the hands-on challenges that are on Trailhead right now. There’s at least a few of them there for Data Cloud, some for Einstein, etc. You can get nice, shiny new badges and get your real world hands-on experience, and you’ll see more and more of these in the coming months.
Mike Gerholdt:
It’s one thing to do a module where it ends in quiz questions and then you read some stuff, and then it’s another to do one and then get the error message be like, “Oh, really? I got to go back and read some of this. I really thought I knew what I was doing here.”
Skip Sauls:
Exactly, exactly.
Mike Gerholdt:
One thing we didn’t touch on, and this is maybe blinders that I have, but what about people with multiple orgs?
Skip Sauls:
A really cool feature, which is… I have to go look at my schedule and see when it’s going to be out, but it’s soon. Is the notion of a remote Data Cloud. I’m waving my hands here as I’m talking to you, but I’ll try to describe it for the listeners. What you’ll do in the future is when you have multiple orgs that you’re managing, for example. A lot of people will have more than one. You’ll designate one to be the home org. I don’t know if that’s the official terminology, but that’s what we’re calling it right now. That is where the Data Cloud instance will live. It’ll be tied to that org. You won’t have multiple Data Clouds, you’ll have one, in most cases. Then the other orgs you have will be remote orgs that are leveraging that org.
There’s some technology there. You can look up something called data spaces. You’ll be able to say this part of this data in this data space can be mapped to these remote orgs, and in your remote org, you’ll be able to access that as if it’s natively inside of your org. In all cases, Data Cloud doesn’t live inside of Salesforce Core, it’s actually running externally. It’s not as big of a hop, if you will, to have these remote orgs. It’s not like they’re really going around the globe trying to connect to each other. The home org is just where you’re going to manage the core data, the way to do everything. But you could then have orgs that are primarily for sales or for service, or maybe you’ve got some that are by industry or by region. However you decide to organize yourself, no pun intended, you can still use the same Data Cloud instance.
The cool part there is because we’re unifying all this data, you could have the same customer represented in multiple places across all these orgs, but they look like the same customer inside of Data Cloud. You can use this for how do you rationalize the data instead of trying to do it manually with all sorts of mappings and code and that sort of thing. You can say, “This is going to be Mike on all these different orgs.” And also, importantly, it’s Mike coming in from external data sources. It could be IoT, it could be social media, pretty much wherever you’d like to. But you can know this is Mike across all those, and it’s a lot more straightforward than in the past, where we had to manually do a lot of work to say, “This is actually the same user across all these things.”
Mike Gerholdt:
I like that. Yeah. Boy, 2007 Mike really needed Data Cloud, let me tell you. One of the things I was thinking about as you were talking through all this and unifying the data is really looking at Einstein and some of the stuff that’s coming down now, and admins are seeing that. We saw it at TDX with Prompt Builder and Copilot. If you’re a Salesforce admin and you’re sitting there and you listen to this Data Cloud, what are some of the questions that we’re hearing from customers that are really good questions to ask on what should I be looking for in an organization that should prompt me to start having these conversations about getting Data Cloud?
Skip Sauls:
There’s a really good blog, and I’m going to try to find this for you. I’m going to tell you there’s some great quotes in here if you’re not familiar with SalesforceBlogger.com, that’s actually run by some Salesforce employees. It’s mostly employees posting it, but it’s not our official blog. It’s like some of the other semi-official blogs that has some really great content. In there, there’s a whole section of what people will ask for. The reason I bring this up is a lot of times, you won’t hear people saying, “We need Data Cloud.” They’re going to actually say, “We need to make better sense of our sales data.” “My sales guy needs to be able to know which customers to target.” In that example, you might have your current notion of your accounts and contacts and leads and that sort of thing. Then you’ve got some external data which talks about very similar things, but it’s from a public source. It’s not Salesforce data
But it’s information about accounts and it could be customer data, it could be company data and that kind of thing. But it tells you something interesting about them and what they’re interested in, and you can actually import that data and unify it and then run some calculated insights and other about it. You might find out you’re not really targeting the right people. You might say, “We actually need to branch out and target other customers.” Or you’re enriching the same data for your current customers, it’s just data you didn’t have before. It’s like, “We didn’t know this. We didn’t know they were interested in these things, and we can have other selling opportunities.” It’s that kind of thing that I think is very important is that you’re using it as a tool to make better sense of your data, make better sense of your respective target objects, whether they be customers or things, than you could before. You can do so in a way that doesn’t require that you’re manually trying to build all this inside of Salesforce Core.
Mike Gerholdt:
For the longest time, the joke was how long is your account page or your contact page, because you are having to reduplicate all these fields just to accommodate all of this extra data.
Skip Sauls:
Exactly. We see lots of interesting naming conventions for that kind of thing
Mike Gerholdt:
Probably horrible ones, too.
Skip Sauls:
Yeah, exactly.
Mike Gerholdt:
I’m guilty of that, too. Contact, last name, four, because that’s how it’s going to work.
Skip Sauls:
If you inherit orgs from others, sometimes that’s multi-generational. You can certainly see that with like, “There’s three or four different naming conventions and duplicates of objects.” Because they oftentimes came in and said, “We can’t really change this. We can’t really make sense of it. We almost have to start over again in order to enhance something.” The idea with Data Cloud is don’t do that. Keep your existing data, move the source of truth into Data Cloud and operate it on it there, and you don’t have to go back and rewrite everything in Core or importantly, everything off Core, every single time.
Mike Gerholdt:
You bring up a point, so let me… Silly question, because I’m still learning this too, but with Data Cloud… This is going to sound weird, correct me if I’m wrong, but you can have multiple sources of truths. We would have a finance system that was a source of truth for address, but we had a certification system that was a source of truth for what certifications that organization held. We didn’t want them all in Salesforce. We wanted each… It’s a data silo, but that’s its job, and it’s secure that way. With Data Cloud, we can connect them, we can get that view in Salesforce, but we also don’t have to pull all that data in. Am I right in saying that?
Skip Sauls:
Exactly. You’re mapping the data from Salesforce into Data Cloud, and if you have the same names and same values across different objects in different fields and external sources, you can resolve those inside of Data Cloud and say which one is the one you want to use, which one is that source of truth. You can create your ideal, I think people call it the golden record, is one notion I’ve heard of. This is the agreed upon… I heard it called the single version of the truth, which sounds political, but it’s basically you as an organization say, “This is what we all agree is the correct source of truth for these things.” Instead of it being in multiple orgs or across multiple objects, you now have the single unified object and you agree that this is the address, this is the account value, this is whatever the dates might be.
That’s the beauty of it is it gives you one place to do that work, instead of trying to do it across things. It’s always been possible to do this kind of thing. You didn’t need Data Cloud to do that kind of thing, it’s just harder to do those things. People found it frustrating, and the thing we didn’t want to hear, what we heard people say, “I had to pretty much export everything outside of Salesforce and do work on it in some other cloud to get the results that I wanted.” So we’re saying, “Let’s not let require people to do that. We don’t want them to leave Salesforce. We want this inner gravity to still be on Salesforce. Let’s give them the tools they need to be inside of our platform instead of externally.”
Mike Gerholdt:
I remember having real conversations about how this X server could do a CSV and put it on… I think it was an Outlook or SharePoint, and then how do I set up, at the time, Data Loader via the CLI to do batch imports? That was a conversation that now feels so dated. Feels like watching a early ’90s sitcom where they have a bag phone in a car.
Skip Sauls:
But people still do that today. We saw that with analytics. We still see it with people exporting, and they go into Excel, and they do their work there. We have had lots of great tools for this, and Data Cloud has the best suite of these things now, and you can actually do it really well in place. There’s no reason for you to export anything, unless you want to make it available to somebody to play with in Excel, but there’s no reason you should be doing your work there. Importantly, you’ve got tools like Tableau, which are really good at this, much better than Excel would ever be. Do your work in Data Cloud, use some of these great tools we have, and not do this external manual copying, uploading type of thing. That stuff works fine in the small, but it’s terrible when you have large numbers of people working on it, and really bad when you have different people coming in at different times that may not realize what was happening.
Mike Gerholdt:
Yeah, let alone the second you pull something out of a system, now you’ve lost all control over that data.
Skip Sauls:
Exactly.
Mike Gerholdt:
In terms of security, confidentiality, especially if it’s a spreadsheet, could be emailed to somebody. That’s the part that always worried me. I always had the sales manager whose second question was, “Who can export this data?” Nobody, thankfully. That’s a checkbox I never check. Skip, thanks for coming on. I know last time, we talked about the Evel Knievel motorcycle, but that was just because I was fresh off of going through a world tour DC and some museums out there.
Skip Sauls:
Oh, yeah. I’m a big motor sports fan, just like you. A gear head, whatever you want to call it. If it has a motor, I’m interested in it. Getting a little too old for some of it, but I still enjoy it.
Mike Gerholdt:
Well, that’s the beauty is you can always watch it. There’s always somebody younger than us that’ll want to do something fun.
Skip Sauls:
Exactly.
Mike Gerholdt:
Thanks for catching us up as the new Trailhead… I’ll link to the Trailhead modules that we’ve got available on that. Then of course, knowing that there’s more coming out. To me, the most exciting part with everything is the second I can get my hands on a DE org or something, that’s when I can actually start to understand it. I remember that was so fundamental when I first started as an admin, the ability to get my hands on a DE org and try stuff out that wasn’t a production org. The same holds true for all of our products, so I’m glad that we’ve overcome that barrier.
Skip Sauls:
I encourage everybody to try that out and give us your feedback. What else do you want to know? What doesn’t work well? What did you enjoy? Reach out to us. You guys will see me, the community, on Twitter, LinkedIn, etc. I’m always looking for more feedback, and ping me if you need anything. Let me know how we can help.
Mike Gerholdt:
Yeah. I appreciate it, Skip. Thanks for coming back.
Skip Sauls:
Yep, thanks a lot.
Mike Gerholdt:
I’m glad we could have Skip back. Always appreciate him coming back and helping admins understand how we can break down all of the data silos that we have within an organization and make our lives easier. I wasn’t kidding when I asked a few of the questions about syncing data and back and forth. I’ve got to believe that’s some of your life, too, because I feel like everybody just one view of the customer. But everybody’s got to own different parts of data, and that’s fine. This really helps knock things out. I think it really makes things interesting and accessible for Salesforce Admins.
Now, if you’re listening, I want you to do me a favor. Click on the Share Episode button, and you can post it to any of your social media. You can text it to a friend, maybe there’s a friend. You guys can both do a Data Cloud Trailhead module together, and let him know that you got hands-on with Data Cloud, which was something that the last time we were on the Salesforce podcast that Skip was on, he couldn’t tell us to do.
Thanks for listening, and until next week, we’ll see you in the cloud.
Today on the Salesforce Admins Podcast, we talk to Skip Sauls, Senior Director of Product Management at Salesforce. Join us as we chat about why data is so important to reporting, what some big-data terms are, and some fun hobbies that Skip enjoys outside of building awesome products for Salesforce Admins. You should subscribe for […]
Today on the Salesforce Admins Podcast, we talk to Lizz Hellinga, Consultant and Salesforce MVP. Join us as we chat about why clean data is more important than ever if you want to leverage the potential of generative AI. You should subscribe for the full episode, but here are a few takeaways from our conversation […]
Today on the Salesforce Admins Podcast, we talk to Muralidhar Krishnaprasad, EVP of Engineering, Next Gen Customer 360 Data Services at Salesforce. Join us as we talk about Data Cloud and all of the exciting innovations coming to help admins own all the data in their org. You should subscribe for the full episode, but […]
