In this chapter, we covered a lot of the theory behind MDM, having a single source of truth for data records, and some methods for its implementation, along with considerations for doing so. While Salesforce is often implemented to act as the de facto source of truth, it is important to understand why that often drives these decisions and the benefits it gives, hence spending time on the theory of MDM. With that theory understood, it should become clear how Salesforce fits into an organization’s MDM strategy.
We’ve looked at why data quality is important in the context of MDM, and why it is important to preserve data attributes across the systems in the enterprise that constitutes the single source of truth, or golden record.
We turned our attention to MDM implementation in Salesforce, touching on the use of middleware, and highlighting the data migration exercise that will invariably accompany a Salesforce go-live.
We have covered what a golden record is and looked at the various things to consider when determining where a golden record’s data fields reside, and what data fields from source systems constitute the golden record. The architecture related to associating different systems in the IT enterprise with the golden record can have an impact on how data operations work and business rules run, so we covered the theory behind that also. We also then looked at how to preserve data quality and ensure traceability and business rule context for operations and procedures, highlighting that the system in which a process runs may change due to the introduction of a new data master in the IT estate.
In Chapter 4, Salesforce Data Management, we’ll dive into how Salesforce license types affect the data model and the sharing options available to work with. We’ll also look at how to govern the data on the platform, as it is crucial to designing scalable, performant solutions that combine data from one or more Salesforce instances.
Acedexam Training Policies
Learning resources
Other resources
Our Training Providers
