Skip to main content
Back to course
Log in
Get started
Someone wanted to learn this too, so Grasp built them a personal learning path.
Create your own
Switching Companies
·
Module 1
Salesforce Platform Foundations Refresher
1
Distinguishing Salesforce Metadata, Configuration, and Business Data in Deployments
Distinguish Salesforce metadata, configuration, and business data in a deployment scenario.
Distinguish Salesforce metadata, configuration, and business data in a deployment scenario.
2
Designing a Salesforce Data Model with Object Relationships
Design a Salesforce data model using standard objects, custom objects, lookup relationships, and master-detail relationships.
Design a Salesforce data model using standard objects, custom objects, lookup relationships, and master-detail relationships.
3
Choosing the Right Salesforce Declarative Mechanism
Select an appropriate declarative mechanism—formula, validation rule, roll-up summary, or Flow—for a stated requirement.
Select an appropriate declarative mechanism—formula, validation rule, roll-up summary, or Flow—for a stated requirement.
4
Tracing Record Updates Through Salesforce Order of Execution
Trace a record update through the relevant stages of Salesforce order of execution.
Trace a record update through the relevant stages of Salesforce order of execution.
5
Determining Object and Field Access Permissions
Determine a user's object and field access from profiles, permission sets, and permission-set groups.
Determine a user's object and field access from profiles, permission sets, and permission-set groups.
6
Determining Record Access in Salesforce
Determine a user's record access from organization-wide defaults, role hierarchy, sharing rules, teams, and manual sharing.
Determine a user's record access from organization-wide defaults, role hierarchy, sharing rules, teams, and manual sharing.
7
Identifying Governor Limits from Debug Logs
Identify the governor limit responsible for a failed transaction by interpreting a debug log.
Identify the governor limit responsible for a failed transaction by interpreting a debug log.
Next module isn't ready yet,
Back to course
Previous module
Next module