With a grasp of Master Data Management (MDM) concepts under our belt, we can now look at Salesforce Data Management. In this chapter, we’ll look at how the Salesforce data model and Salesforce licensing work together. The license types chosen for a solution have an impact on the objects available. This can extend to record sharing facilities available in the case of Experience Cloud license types.
We’ll look at what data persistence looks like on the Salesforce Platform and how that works when governing solutions on the Salesforce Platform.
Next, we’ll expand on our golden record theory from Chapter 3, Master Data Management, to explain what a Single Customer View (SCV) looks like on the Salesforce Platform, and how data from multiple Salesforce clouds and multiple Salesforce instances can be pieced together.
Therefore, in this chapter, we’ll cover the following topics:
In this section, we’re going to cover how the different Salesforce licensing options affect the objects and standard functionality available to users. Given the vast array of functionality available in Salesforce products, it is important to ascertain what the required objects and functionality will be (from both an internal and external access perspective) so that the correct licenses can be purchased. As expected, certain licenses are more expensive than others—for example, Service Cloud licenses are more expensive than Sales Cloud. In the case of Experience Cloud, this type of license not only affects the objects available for users but can affect sharing rules and role hierarchy too. We’ll get to those implications further along in this section.
Because of the cruciality of getting licensing correct, an important artifact produced during the Certified Technical Architect (CTA) review board is Actors and Licenses. This is essentially a listing of different user types and the licenses those different user types (also known as personas) need to interact correctly with the proposed solution. As a Salesforce architect, you should therefore consider this exercise as a pillar to your solution. If it is wrong, it can have profound impacts on the way users work.
Important note
Experience Cloud = Community Cloud: Salesforce has rebranded Community Cloud to become Experience Cloud. This is intentional and represents a shift from Communities being alens into your Salesforce data for external users. The technology that powers Community Cloud/ Experience Cloud has evolved so much that entire digital experiences and commerce storefronts can be powered from it, hence the rebranding. For the avoidance of doubt, Community Cloud, Communities, and Experience Cloud are one and the same. The Salesforce documentation isn’t fully updated at the time of writing, so be mindful that you may still see references to Community Cloud and Communities from time to time.
Let’s now delve deeper into the different types of licensing on the Salesforce Platform.
Acedexam Training Policies
Learning resources
Other resources
Our Training Providers
