
When working with Microsoft Dynamics 365 CRM, efficiency and user experience matter. One feature that often goes unnoticed - but can make a significant difference - is the Quick View Form. If you’ve ever wanted to display related record information directly within the current form without forcing users to open another window, Quick View Forms are exactly what you need.
In this blog, I’ll walk you through what Quick View Forms are, why and when you should use them, how to set them up, and how to enhance them using JavaScript where possible.
What Is a Quick View Form?
A Quick View Form in Dynamics 365 CRM allows you to show fields from a related entity on the main form of another entity. The data shown is read-only and is retrieved through a lookup relationship. These forms are embedded into other forms and act as lightweight summaries of related records.
For example, if you’re looking at a Contact record and want to display details from the associated Account, a Quick View Form lets you pull in that information - such as Account Name, Phone Number, and Industry - directly onto the Contact form. This saves time and improves visibility, especially for users who frequently work across multiple entities.
Why and When to Use Quick View Forms
Quick View Forms are most useful when you want to improve the user experience without overcomplicating the form. They allow you to bring important related data into view so that users don’t have to navigate to other records.
Here are some common reasons to use them:
- To reduce unnecessary navigation between records
- To provide more context when viewing or editing a record
- To enhance data visibility without cluttering the form
- To summarize related information within dashboards or forms
How to Create and Use Quick View Forms
Creating and using Quick View Forms in Dynamics 365 CRM is straightforward. Here’s a step-by-step example based on a real use case.
Workaround Example
Let’s say you have a City entity with three fields: City Name, State Name, and Country Name. In the Account form, I’ll create a lookup field for the City table. I’ve added a new tab named “QV Test” to demonstrate this use case.
When a city is selected, the corresponding State and Country names should automatically appear. This is exactly where a Quick View Form helps.
Step 1: Create the Quick View Form
- Navigate to Advanced Settings → Solutions → Your preferred solution
- Select the entity from which you want to display information (e.g., City)
-
Go to the Forms section
and click
New Quick View Form
- Name the form something like “City Quick View”
-
Design your form by adding only the necessary fields - keep it simple and
focused (in this case, State and Country)
- Save and Publish the form
Step 2: Add the Quick View Form to the Target Entity
- Open the main form of the target entity (e.g., Account)
-
Add the City lookup field
to the QV Test tab
- In the form designer, insert a Quick View Form control
-
Select the lookup field that links to the related City record
-
Choose the
related entity and the
Quick View Form you created
- Position the form in the layout where it makes the most sense for users
- Save and Publish the form
Once published, users will see the Quick View Form populated with data from the related record—as long as the lookup field has a value.
Demonstration

-
Navigate to the
Account form and switch
to the QV Test tab.

-
Once a city is selected from the lookup field, the Quick View Form will
automatically display the corresponding
State and
Country fields.

Customizing the Quick View Form with JavaScript
While Quick View Forms are read-only and somewhat limited in customization, JavaScript can help you enhance them - particularly when you want to control visibility or implement conditional logic.
I have used the below code to hide the Quick View Form and its fields conditionally.
Example: Hide or Show Fields Dynamically
You can access the Quick View Form control and control its visibility based on conditions:
Code Breakdown
- Get the City lookup field value using: formContext.getAttribute("tamil_city").getValue()[0].id.slice(1, -1);
- Retrieve related record details using Web API: Xrm.WebApi.retrieveRecord("tamil_city", cityValue, "?$select=tamil_name,tamil_state,tamil_country");
- Get the Quick View Form control: formContext.ui.quickForms.get("tamil_cityQVF");
- Use visibility logic based on field values: cityQvfControl.getControl("tamil_state").setVisible(false);
- Hide individual fields or the entire Quick View Form if necessary: cityQvfControl.setVisible(false);
Final Steps
- Go to the Account form → Events → On Load

- Add the JavaScript web resource to the Event Handler
- Save and Publish the form
Demonstration
If the State field is empty in the selected City record, the State field will be hidden from the Quick View Form.
For example, I added a city named “New Delhi” which is a Union Territory and does not fall under any state. So the State field is left empty - and therefore hidden.
If both the State and Country fields are empty in the City record, the entire Quick View Form will be hidden. I created a test record named “Bir Tawil” a disputed territory claimed by no state or country (fun geography fact), and the form disappears entirely in this case.
Conclusion
Quick View Forms are a smart way to create clean, efficient, and user-friendly forms in Dynamics 365 CRM. They let you bring relevant related data into the context of the current record, reducing navigation time and improving usability.
While you can’t edit data inside a Quick View Form, you can still control how and when it appears using JavaScript. With thoughtful use, Quick View Forms can significantly enhance both your form design and the user experience.
References
- Create and edit Quick View Forms – Power Apps (Microsoft Docs)
- Quick View Forms for On-Premise – Microsoft Docs
- Client API - isLoaded Method
- Client API - getControl Method
- Client API - setVisible Method
Have a great day!