IC
Interchange Global Advisors
make your connection
Preview · Invite-only
← Salesforce Consulting 101 Module 03 of 08
Module 03 · the vocabulary

How Information Is Stored: Objects, Records, Fields

Three words you'll hear hourly: object, record, field. If you've used a spreadsheet, you already understand them — they're just tab, row, and column with different names.

By the end you can

Map object / record / field to tab / row / column, and tell a standard object from a custom one.

Estimated time: 15 min  ·  Prerequisite: Module 02

The spreadsheet you already know

Picture a spreadsheet with a tab called “Contacts.” The tab is the kind of thing you are tracking. Each row is one actual person. Each column — name, email, phone — is a detail about them. Salesforce works exactly the same way; it just uses different words:

  • Object = the tab (the kind of thing). “Contact” is an object. “Account” (a company) is an object.
  • Record = the row (one actual thing). “Jane Smith” is a record. “Acme Corp” is a record.
  • Field = the column (one detail). “Email” is a field.

That is the whole idea. Object, record, field = tab, row, column.

Standard versus custom

Salesforce comes with the common objects already built — Account, Contact, Opportunity (a deal), Case (a support request). Those are standard objects. But every business has things unique to it: a construction firm tracks “Projects,” a clinic tracks “Patients.” When the built-in objects do not fit, a consultant builds custom objects and custom fields. A huge share of Salesforce project work is exactly this — shaping objects and fields to match how the client actually works.

Why this is the foundation of everything

Reports, automation, screens, permissions — all of it sits on top of objects, records, and fields. If you understand these three words, every other Salesforce concept has somewhere to land. Get them solid before anything else.

Key terms from this module
Object
A kind of thing you track — like a spreadsheet tab. (Account, Contact, Case.)
Record
One actual entry — like a spreadsheet row. (“Acme Corp.”)
Field
One detail on a record — like a spreadsheet column. (“Email.”)
Standard object
An object Salesforce ships with built-in.
Custom object
An object a consultant builds to fit a specific business.
On an engagement

When a client describes their business — “we manage shipments for dealers” — train your ear to hear the objects: Shipment, Dealer. That instinct is the first half of a consultant's job.

The one thing to remember

Object / record / field = tab / row / column. Standard objects come built-in; custom ones are shaped to the client.

How this was written. This module was authored from established Salesforce-ecosystem knowledge — not assembled from a live web search. Nothing was fetched or “pinged” at build time, so there is no retrieval log to show. The references below are authoritative places to verify each point and read further; the flags note anything that shifts over time and should be re-checked before this goes in front of a client.
Reference & further reading
Verify before client use