Shreenika IT Services
Forms and Types
Introduction:
In Model-Driven Apps (built on Microsoft Dataverse), a form is the main interface where users
view, create, and update records for a table (entity).
When you open a record like an Account, Contact, or Case, what you see on the screen —
fields, sections, tabs, and related data — is controlled by a form.
Forms ensure that:
• Data is displayed in a structured way.
• Business rules guide the user’s input.
• Different layouts can be shown for different user roles or purposes.
Types of Forms in Model-Driven Apps
1. Main Form
The Main Form is the primary form for viewing and editing records.
It can contain multiple tabs, sections, subgrids, and business rules.
For example, in a Customer Management App, the Account main form might have:
• A General tab with fields like Account Name, Phone, and Website.
• A Details tab with Address and Industry.
• A Contacts tab showing related contacts in a subgrid.
Example 1:
In a Customer Service App, the Case Main Form contains:
• Tab 1: Case Title, Customer, Status.
• Tab 2: Description, Resolution, Related Activities.
Example 2:
In a Sales Management App, the Opportunity Main Form includes:
• General Tab: Opportunity Name, Estimated Revenue, Close Date.
• Details Tab: Sales Stage, Competitors, Products
Quick Create Form
The Quick Create Form is a simplified form designed for creating a new record without leaving
the current page.
For instance, while working on an Opportunity, a user can click + Add Contact and see a small
Quick Create Contact form with just Name, Email, and Phone.
This helps save time and keeps the user’s workflow uninterrupted.
Example 1:
In a Sales App, while working on an Account record, the user clicks + Add Contact and a small
Quick Create Contact form opens with fields for Name, Email, and Phone Number.
Example 2:
In a Project Tracking App, while creating a Project Task, the user can quickly create a related
“Resource” record without leaving the task form using a Quick Create Resource form with
Name and Role.
Quick View Form
The Quick View Form displays read-only data from a related table directly inside another form.
For example, on a Case Form, you could show related Customer Account details — such as
Account Name, Primary Contact, and Contact Phone — without letting the user edit those
details from the Case form.
Example 1:
In an Incident Management App, the Incident form shows related Customer Account info —
like Account Name and Primary Contact — via a Quick View Form, without allowing edits.
Example 2:
In a Contract Management App, the Contract form displays related Vendor information such
as Vendor Name, Address, and Contact Number through a Quick View Form
Card Form
The Card Form is a compact form used to display summary information, often in dashboards or
embedded views.
For example, a dashboard could show “Top Accounts” where each account is displayed as a
small card with just Account Name, Annual Revenue, and Owner.
This helps give quick insights without opening full forms.
Example 1:
In a Dashboard, a Card Form shows summary info for Top 5 Accounts with Account Name,
Annual Revenue, and Owner.
Example 2:
In a Service Dashboard, a Card Form displays Active Cases with Case ID, Priority, and Status,
allowing users to quickly assess workload.
Questions on Forms and Types
1. What is a form in a Model-Driven App?
2. Why are forms important in Model-Driven Apps?
3. Which platform do Model-Driven Apps use to store and manage data for forms?
4. What is the purpose of a Main Form in a Model-Driven App?
5. How is a Quick Create Form different from a Main Form?
6. When would you use a Quick View Form?
7. What is the use of a Card Form in dashboards?
8. How does a Main Form – Dialog improve user experience?
9. Give an example of a Quick Create Form in a sales scenario.
10. How can a Quick View Form be used in a Case management app?
11. Describe a scenario where a Card Form is more useful than a Main Form.
12. Provide a use case for Main Form – Dialog in an Order management app.
13. Why should you use role-based forms in Model-Driven Apps?
14. How can business rules enhance form usability?
15. Why should Card Forms be kept minimal?
