Standard objects model common CRM entities such as Accounts, Contacts, Leads and Opportunities. Their purposes differ; an Opportunity tracks a potential sale rather than a person.
Before you begin
Use an authorized development or training organization with fictional records. Record the object names, permissions and configuration used so that someone else can reproduce the exercise.
Work through the idea
First describe the business requirement and the records involved. Keep the exercise separate from a live organization's data and change process. Platform behavior can depend on permissions and configuration; verify those conditions rather than assuming an administrator's result applies to every user.
- Identify each record's business meaning
- Inspect relationships and required fields
- Separate standard and custom fields
Practice task
Model a fictional company with two contacts and one sales opportunity. Explain where each fact belongs.
Check your result
The company is not duplicated as a Contact and the sales stage belongs to the Opportunity.
A mistake to avoid
Do not assume that similarly named fields on different objects have the same business meaning.
Keep a review note
Save the inputs or scenario, your reasoning and the result you checked. Explain one assumption and one case that needs more work. Revise the exercise after feedback and distinguish what you demonstrated from what remains untested.
Official reference for further study
Explore the related learning path · Choose another worksheet