Day 5: Forms, Views, and Model-Driven Apps

Jitendra Sharma

5 min read

·

Jul 31, 2026

--

Listen

Share

A Roadmap from Fresher Developer to Solution Architect
Series: Learn Microsoft Dynamics 365 CRM Step-by-Step
Day 5 of 90

Image

Welcome Back!

In Day 4, we learned how Dataverse stores business data using:

✅ Tables

✅ Columns

✅ Relationships

Today, we’ll bring that data to life.

After all, users don’t interact directly with Dataverse tables. They interact with:

• Forms
• Views
• Model-Driven Apps

As a Dynamics 365 professional, understanding these components is essential because they define the user experience.

Great developers build functionality.
Great architects design experiences.

The Big Picture

Let’s understand how everything fits together:

Dataverse
     ↓
Forms
     ↓
Views
     ↓
Model Driven Apps
     ↓
Business Users

Dataverse stores the data.

Forms display and edit data.

Views organize data.

Model-Driven Apps bring everything together.

Dataverse Tables
        ↓
Forms
        ↓
Views
        ↓
Model-Driven Apps
        ↓
End Users

Diagram
Data → UI → Business App

What is a Form?

A Form is the screen users use to create, edit, and review records.

For example:

Account Record
 ↓
Account Form

A user opens a customer record and sees:

• Account Name
• Phone Number
• Address
• Email
• Owner
• Status

All displayed through a form.

Why Forms Matter

Imagine a customer service representative opening a Case.

If information is difficult to locate:

❌ Productivity drops

❌ User frustration increases

❌ Errors become common

A well-designed form helps users complete tasks efficiently.

Types of Forms

1. Main Form

The most commonly used form.

Used for:

• Viewing records
• Editing records
• Creating records

Contains multiple tabs and sections.

2. Quick Create Form

Used for fast record creation.

Example:

Instead of opening a large customer form: + New Contact

A small popup appears containing:

• Name
• Email
• Phone

Quick and efficient.

3. Quick View Form

Displays information from related tables.

Example:

You open a Contact record and immediately see:

• Parent Account
• Company Name
• Industry
• Phone Number

without opening the Account record.

Form Components

A typical form contains:

Tabs
 ↓
Sections
 ↓
Fields

Example:

General Tab
     ↓
Customer Information Section
     ↓
Name
Email
Phone

Form Design Best Practices

Good Form Design

✅ Most important information at the top

✅ Logical grouping of fields

✅ Clear labels

✅ Minimal scrolling

✅ Consistent layout

Poor Form Design

❌ Too many fields

❌ No organization

❌ Duplicate information

❌ Important data buried at the bottom

Architect Tip

Ask:

What information does the user need first?

Not:

What fields exist in the table?

The form should support the business process.

What is a View?

A View displays multiple records in a list format.

Example:

Active Contacts

Name
Email
Phone
Owner

Active Cases

Case Number
Title
Priority
Status

Views help users find and manage data quickly.

Common Types of Views

Public View

Available to many users.

Examples:

Active Accounts
Open Opportunities
Active Cases

Personal View

Created by individual users.

Examples:

My Accounts
My High Priority Cases
My Open Opportunities

Why Views Matter

Imagine having 100,000 customer records.

Users cannot search manually.

Views provide:

✅ Filtering

✅ Sorting

✅ Grouping

✅ Faster navigation

Example View

Active Cases

Case Number
Title
Priority
Status
Created On
Owner

Users instantly know:

• Open work
• Priority items
• Assigned records

What is a Model-Driven App?

A Model-Driven App is a business application built on Dataverse.

Unlike traditional applications where developers design every screen manually, Model-Driven Apps generate user experiences from your data model.

Understanding Model-Driven Apps

Think of it like this:

Dataverse
 ↓
Tables
 ↓
Forms
 ↓
Views
 ↓
Model-Driven App

Microsoft automatically provides navigation, search, security, and record management capabilities.

Example Healthcare Application

Suppose a hospital wants:

Patients
Appointments
Doctors
Cases

A Model-Driven App can bring all of these together.

Navigation:

Patients
Appointments
Doctors
Support Cases
Reports

Users can manage everything from one application.

Benefits of Model-Driven Apps

Faster Development

Less custom coding.

Built-in Security

Leverages Dataverse security.

Mobile Support

Works across devices.

Consistent User Experience

Microsoft-standard UI.

Scalability

Suitable for enterprise applications.

Real-World Business Scenario

Let’s build a simple Insurance Management System.

Dataverse Tables

Customer
Policy
Claim
Agent

Forms

Customer Form
Policy Form
Claim Form

Views

Active Policies
Open Claims
Assigned Customers

App

Insurance Management App

Everything works together seamlessly.

Developer vs Architect Mindset

Developer Thinking

How do I create a form?

Senior Developer Thinking

How do I optimize the user experience?

Architect Thinking

How should users interact with the system to maximize productivity and minimize training effort?

This mindset separates solution architects from technical implementers.

Common Beginner Mistakes

Mistake #1

Adding every field to the form.

Result:

Huge Form
Poor User Experience

Mistake #2

Ignoring user personas.

Different users need different information.

Examples:

Sales Team
Customer Service Team
Managers

Mistake #3

Creating too many views.

Users become confused.

Keep navigation simple.

Example Architecture Exercise

Hospital Scenario:

Tables

Patient
Doctor
Appointment

Forms

Patient Form
Doctor Form
Appointment Form

Views

Today's Appointments
Upcoming Visits
Open Cases

Model-Driven App

Patient Care Management

This is exactly how real Dynamics projects begin.

Day 5 Assignment

Task 1

Design a CRM solution for one of the following:

• Hospital
• Insurance Company
• Retail Store
• Bank

Task 2

3 Tables
3 Forms
3 Views
1 Model-Driven App

Task 3

Think Like an Architect

Answer:

What information should appear at the top of a customer form and why?

Focus on user productivity.

Key Takeaways

✅ Forms allow users to create and edit records.

✅ Views help users find and manage records efficiently.

✅ Model-Driven Apps bring forms, views, and tables together.

✅ Good UX design increases productivity and adoption.

✅ Architects design applications around user needs, not around tables.

✅ Simplicity is often better than complexity.

What’s Coming Tomorrow?

Day 6: Business Rules and Business Process Flows

We will learn:

• What Business Rules are
• Form Validation
• Field Visibility
• Field Requirement Logic
• Business Process Flows
• Stage-Based User Guidance
• Architect Best Practices

Tomorrow we begin automating business logic without writing code.

Final Thoughts

Forms, Views, and Model-Driven Apps are where business users spend most of their time.

You can build the most technically advanced solution in the world, but if users struggle to use it, the project will fail.

A successful Solution Architect doesn’t just design systems.

A successful Solution Architect designs experiences.

See you in Day 6! 🚀

Author: Jitendra Sharma
Series: Dynamics 365 CRM — Fresher to Solution Architect Journey
Day: 5 of 90 Days Learning Challenge

#Dynamics365 #ModelDrivenApps #Dataverse #PowerPlatform #CRM #Microsoft #SolutionArchitecture #UXDesign #SoftwareDevelopment #CareerGrowth