Jan 17 (edited) • 🗣️GENERAL DISCUSSION
Data Model Class Summary Today 16/01/2026 (Team Gamma)
Created an App: Showroom
- Assigned to System Administrator profile so admins can access it immediately.
Objects Created:
- Vehicle (Parent) Fields: Model, Price, Imported Date
- Test Drive (Child) Fields: Customer Name, Slot Relationship: Master-Detail to Vehicle (field name: Vehicle) Confirmed working and visible in Schema Builder.
Validation / Testing:
- Created records to confirm the Vehicle → Test Drive (Master-Detail) relationship works as expected.
- Verified the structure visually in Schema Builder.
Issue Encountered & Fix Applied:
- Issue: Newly created fields were not showing on the objects/pages.
- Root Cause: Field-Level Security (FLS) was not set to Visible for the relevant profiles.
- Fix: Updated FLS visibility for the created fields, after which fields displayed correctly.
Screenshots captured and available Below
>>>Must Know Definitions>>>
Object:
A container (table) that stores a specific type of data in Salesforce.
Example: Account stores company details.
Field:
A data attribute (column) on an object that stores a specific piece of information.
Example: Account Industry, Contact Email.
Record:
A single saved entry (row) in an object.
Example: Account record: “Acme Ltd”.
User:
A person (or integration) with a login and a license who can access Salesforce based on assigned security.
Example: Divine Lantum as a Salesforce user.
Profile:
A user’s baseline access that defines what they can do: object permissions, field permissions, system permissions, plus default app/tab access. (Every user has exactly one profile.)
Example: “Sales User” profile: Read/Create on Leads.
Role:
A user’s position in the role hierarchy that mainly controls record visibility (who can see whose records).
Example: Sales Manager can see Sales Rep records under them when sharing allows hierarchy access.
Permission Set:
An add-on set of permissions that extends a user’s access beyond their profile (never reduces access).
Example: Permission Set “Export Reports” gives Export Reports permission.
Permission Set Group:
A bundle of permission sets assigned together to simplify access management (can include “muting” to turn off specific permissions inside the group).
Example: “Service Console Pack” = Console permissions + Case access + Knowledge access.
Relationships:
1-to-Many Relationship (general)
One record relates to multiple records.
Example: One Account has many Contacts.
Lookup Relationship: (1-to-many, loose)
A relationship where the child record can exist without the parent; security and ownership are independent.
Example: Contact → Account (Lookup) (a Contact can exist without an Account).
Master-Detail Relationship: (1-to-many, tight)
A relationship where the child record must have a parent; the child inherits owner and sharing from the parent; roll-up summaries are supported.
Example: Invoice Line → Invoice (Master-Detail) (line can’t exist without invoice).
Many-to-Many Relationship:
A relationship where many records on Object A relate to many records on Object B, using a junction object (typically 2 master-detail relationships).
Example: Student ↔ Course via Enrollment (junction object).
Work assignment and collaboration (Additional)
Queue:
A shared ownership container that holds records (and some work items) so a team can pick them up. Only supported objects can be queued.
Example: “Support Queue” owns new Cases until an agent takes one.
Public Group:
A named collection of users (and optionally roles, roles & subordinates, other public groups) used to simplify sharing and access—mainly in Sharing Rules, manual sharing, folder/report/dashboard sharing, and email sharing lists.
Very short example: Public Group “EMEA Sales Team” is added to an Account Sharing Rule to grant them Read/Write access to EMEA Accounts.
5
3 comments
Data Model Class Summary Today 16/01/2026 (Team Gamma)
skool.com/pathway-to-salesforce
A community to help you transition into tech, master Salesforce skills, and unlock career opportunities with hands-on learning and real-world support.
Leaderboard (30-day)
1
+317
2
+142
3
+80
4
+75
5
+65
Powered by