Tables, columns, and relationships describe how data is structured behind the scenes. A form is what finally makes that structure visible — the actual screen a user looks at and types into. Two tables can hold the exact same columns yet present them completely differently, depending on how their forms are laid out.

Quick facts
  • A form is the on-screen layout a user reads and edits a record through
  • Sections group related fields; tabs split a form into separate pages
  • Main form = the full editing experience for a record
  • Quick view form = a read-only mini-view of a related record, embedded inline
  • Quick create form = a popup for adding a related record without navigating away

A form is a printed intake form, laid out on purpose

Think of a doctor's office intake form. It isn't a random scatter of blank lines — it's deliberately grouped, with a "Contact Info" block near the top and a separate "Billing Info" block further down. The grouping helps you find what you need, even though every blank is ultimately just one more field on the same record.

A Dynamics 365 CE form works the same way. Columns don't just get dumped onto the screen in creation order. A customizer arranges them into:

  • Sections — a labeled grouping of related fields, like "Contact Info"
  • Tabs — separate pages within the same form, so someone can click over to "Billing Info" without scrolling past everything else

The underlying record doesn't change based on layout — only how conveniently a person can read and edit it does.

Form elementWhat it does
SectionGroups related fields under one heading, like "Contact Info"
TabA separate page within the same form, switched between without leaving the record
Example A Contact's main form might have a "Details" tab with a "Contact Information" section (Name, Email, Phone) and an "Address" section beneath it, plus a "Sales" tab holding fields only the sales team needs — all still one Contact record underneath.

Beyond the main form: quick view and quick create

The full-page form is called the main form — what opens when you click into a record. Two smaller, purpose-built form types show up in specific situations instead:

A quick view form is a read-only mini-view of a related record, embedded directly inside another form. Instead of clicking away from a Contact to check its Account, a quick view form shows a handful of that Account's key fields right there, no navigation needed.

A quick create form is the opposite shortcut: a lightweight popup for creating a new related record without leaving the page. On an Account, need a new Contact right now? Quick create pops open with just the essentials, saves it, and links it automatically.

Key takeaway: A form is the on-screen layout a user actually works with — sections and tabs organize its columns the way a paper intake form groups related blanks together. Main forms are the full editing experience; quick view forms show a related record's details read-only inline, and quick create forms let you add a related record without leaving the page.