Summary – Understanding Salesforce sharing and security – Salesforce Data Architect Theory – Salesforce Certified Data Architect Study Guide

Summary

We’ve started our learning journey and begun with concepts around data modelling and design. We’ve covered sharing and security, delving into the various mechanisms available in Salesforce to control access to data. We’ve paid particular attention to how the OWDs and role hierarchy can have a profound impact on the data that your users can access. We’ve seen how OWDs affect data model design for solutions on the Salesforce platform, and why it is important to get these right based on a solid understanding of the impact of a particular OWD setting when building Salesforce solutions that address customer requirements.

We’ve also covered the different object types available on the platform, highlighting the differences between standard, custom, external, and big objects and the various use cases for each. Again, the use of certain object types (and in particular big objects and external objects) can affect the user experience with regard to data access.

We’ve covered relationships and their effect on Salesforce functionality and data access, and we’ve seen the different methods of objects and their data together on the Salesforce platform, highlighting how we relate data held in external data sources with that held within Salesforce.

We’ve also looked at performance around data with regard to data skew and the methods available to mitigate the impacts of a user owning more than 10,000 records or an account being the parent account for more than 10,000 child records.

With a solid grounding in the concepts highlighted in this chapter, you now understand why it is important to plan for the future from the outset of the design on your Salesforce data model to mitigate the risks associated with data skew and other factors that affect performance.

Lastly, we brought together the concepts when modeling data solutions and introduced a standard for data model diagrams.

In Chapter 3, Master Data Management, we’ll dive into what Master Data Management (MDM) is and learn how to effectively design and implement an MDM strategy on the Salesforce platform. We’ll look at the concept of a golden record, preserve data traceability across multiple data sources, and learn how this affects the context in which business rules run.

Practice questions

1. The Public Read/Write/Transfer OWD is applicable to which objects?

• Performance issues related to an account record that has more than 10,000 child records is known as what?

• What OWD is available for the campaign object that isn’t available to others?

• What type of Salesforce object is used to access data held in an external system in real time?

• True or false: Big objects will store multiple commits of the same representation of a row of data.

• What OWD causes the object to inherit the same data access permissions as the object it is associated with?

• How is a many-to-many relationship created?

• What type of relationship is only available on the user object?

• What happens to the child records when a master record in a master-detail relationship gets deleted?

1. True or false: sharing the child object is affected when using a lookup relationship.

Answers

1. Lead and case.

• Account skew.

• Public Full Access.

• External object.

• False – Big objects only store a single row for multiple commits of the same representation of data.

• Controlled by Parent.

• Two master-detail relationships, one on each object, relating them to each other.

• Hierarchical relationship.

• Child records are also deleted.

1. False.

Further reading

• Data Access in Salesforce: https://developer.salesforce.com/docs/atlas. en-us.dat.meta/dat/dat_components.htm

• Salesforce Standard Objects: https://developer.salesforce.com/docs/atlas. en-us.api.meta/api/sforce_api_objects_list.htm

• Salesforce Data Model Diagrams: https://architect.salesforce.com/ diagrams#template-gallery

• Salesforce Object Relationships Overview: https://help.salesforce.com/ articleView?id=overview_of_custom_object_relationships.htm&type=0

• Restriction Rules: https://help.salesforce.com/s/articleView?id=release-notes.rn_forcecom_sharing_restriction_rules.htm&type=5&release=234