Forms

Forms are one of the most important parts of a model‑driven app. They define how users view and edit data, guide people through business processes, and shape the overall usability of the system. Good form design helps users complete tasks efficiently and keeps the user experience consistent across DfE solutions.

Use multiple forms for different roles

Different teams and user roles may require tailored layouts. Dynamics 365 supports multiple form types (main forms, quick create forms, quick view forms, card forms) to suit different scenarios.

Best practice:

  • Create separate forms for different user groups when their needs vary significantly
  • Keep forms focused and avoid overloading one form with content for all teams
  • Use role‑based forms to simplify the interface for each user group

For example:

  • A “Case Manager” form may show detailed case data
  • A “Contact Centre Agent” form may focus on key triage data and hide admin details

Security roles to control form access

Security roles can restrict which forms users see. This helps ensure users only access information relevant to their job.

Best practice:

  • Assign forms to specific roles to deliver tailored layouts
  • Avoid exposing advanced or administrative options to all users
  • Test with real user accounts to confirm the right forms appear by default

This means that forms can be configured and limited by security role to ensure a relevant experience.

Keep layouts clean, simple and task‑focused

It's recommended to organise columns using tabs and sections to make information easy to find.

Best practice:

  • Place the most important columns (fields) at the top-left of the form
  • Ensure required columns for new records appear early in the form
  • Use tabs to separate major functional areas (e.g. “Details”, “History”, “Documents”)
  • Avoid long, scrolling forms - break content into logical sections
  • Avoid white-space or blank areas on the form
  • Maintain consistency with other forms in your CRM

A well‑structured form helps users complete tasks faster.

Subgrids for related information

Subgrids allow users to view related records directly from the form (for example, viewing all cases linked to a contact).

Best practice:

  • Use subgrids where users frequently need to see related lists
  • Avoid overcrowding forms - each subgrid should have a clear purpose
  • Use filters to show the most relevant subsets of related data
  • Place subgrids inside separate tabs if they take up considerable space
  • Avoid putting more than 5-6 subgrids on one tab due to performance and form load time

This approach emphasises using components like subgrids and Quick View forms to display related content effectively.

Quick View forms for read‑only related data

Quick View forms show information from a related table without requiring users to open the related record.

Benefits:

  • Reduces clicks
  • Helps users understand context quickly
  • Keeps references visible without duplicating data

Provide meaningful form names

Good naming helps administrators and developers identify the purpose of each form.

Examples:

  • Case - Agent View
  • Case - Manager View
  • Application - External Advisor Form
  • Application - Admin Form

Consistent tab and section naming

Use clear names (e.g. Address, History, Funding) instead of Tab_2 or Section_3. This enhances maintainability and keeps the user experience consistent.

Keep business rules and client logic efficient

Forms can contain:

  • Business rules
  • JavaScript
  • PCF controls
  • Web resources

Keep logic lightweight to avoid slow form performance. Use the simplest method that meets the requirement (e.g. use Business Rules before JavaScript).

Further reading

Create and design model-driven app forms (opens in a new tab) is Microsoft’s primary guidance page for developers working with forms.