CRM 2013 New Features: Quick View Forms

This is perhaps my favorite new feature in CRM 2013.  It is common for customers to want to see Contact details such as Phone Number and Email Address on ‘transactional’ forms such as the Case and Opportunity forms.  Previously we had three options to address this:

  1. Do nothing, train that users should click on the Contact to pop the Contact form to view those details
  2. Create custom fields on the Case / Opportunity form and duplicate / synchronize the data from the Contact record
  3. Embed an HTML web resource on the form that dynamically retrieves and displays this data  

Quick Views now provides a no code equivalent to #3 which looks like this:


I’ll demonstrate some creative uses of this new feature in a second but first here are the basics…

The Quick View form is configured using the CRM form editor just like you would a normal form:


You are however constrained when it comes to the form layout, you get one Tab that can contain only single-column Sections – i.e. you are configuring a single column form:


You can insert multiple Sections though and each Section can have a Label and can contain Fields, Spacers or Sub-Grids:


Now onto some design scenarios you might not have considered yet…

You can chose to render Sub-Grids as Charts and add some visual interest to your forms.  In the below screenshot whilst the user is looking at an Opportunity they get a handy visual indicator of the Account’s open Opportunities and active Cases:


You can use a Quick View Form to add contextual help to a CRM form.  This is my bright idea of the year, I think this is very cool and I look forward to utilizing this on a project. Imagine you have multiple types of Opportunities and each Type has different considerations that we want to communicate to the user.  We could create an Opportunity Type entity and place a corresponding lookup field on the Opportunity form.   On that Opportunity Type entity we can populate some guidance into some custom fields and then use a Quick View Form to display those fields on the Opportunity form once the Opportunity Type is  selected.  That gets us a user experience like this:


The experience is immediate, the Quick View Form renders / changes on change of the lookup field. 

I have placed the Quick View Form on the right side of the form, you could also place it beneath the lookup field:


One concern I have is the Quick View Form seamlessly integrates into the CRM form so there is the potential for the user to be confused and think these are editable fields.  Placing the form on the right helps address this.

Anyone else have any creative ideas on how we can leverage this new feature?


11 thoughts on “CRM 2013 New Features: Quick View Forms

  1. Jukka Niiranen

    Great article once again, Gareth! I’ve also been experimenting with the very same approach, leveraging the Quick View forms to show instructions that are relevant to the current process stage where the record is. So, instead of just showing the info field based on the opportunity type, you would get a stage specific set of instructions that update as you progress the opportunity forward in the sales process.

    This would require you to model the processes and process stages as custom entities that hold the instruction fields and then update the corresponding lookup fields on the opportunity field with real-time workflows as the user clicks on the Business Process Flow control to move from one stage to another. I’m looking forward to trying this approach in one upcoming project and also sharing the experiences from that, but based on my initial tests this seems to work quite nicely.

    As great as the new Business Process Flow control is as a process visualization component, the very limited space that this control gives for field labels and values doesn’t really meet the needs for instructing the end user on what he or she should be performing. It’s fine for data collection, but a more extensive process guidance still has to be provided through other means. Since I’d rather see it all embedded inside CRM and not some external document or intranet site, the Quick View form capabilities seem like a great fit for this type of a need on presenting information from another entity in the context of the actual transactional record like opportunity, case, project and so on.

  2. Kiran

    Wonderful Information !!
    I have one question here. Is there any way to drill down, to see the actual records which formed the chart in the Quick View Form. I know that in Dashboard we can drill down to see the actual list of records. But when i put charts in the Quick View form, i am not able to drill down to see actual records.

    Could you please let me know how to achieve that functionality if there is any.


  3. Pradeep

    when i populate the look up from javascript in onload even the quick view form is not visible for that record, any specific reasons?

    1. Jukka Niiranen

      Since notes are not presented in standard CRM fields or views but rather in a specific form control, I can imagine this being much more complicated to implement. Quick View Forms also don’t support adding custom web resources or iFrames. I suspect one issue would be that these form components are designed to be dependent on the parent record on which form they are rendered in. Once you’d embed them on a form of the child entity, they’d need to reference the parent entity instead of the currently viewed record. Ensuring all the scripts would work in such a scenario might introduce a level of complexity onto the basic usage of these components that would make it not feasible to support it.

  4. MarkX

    Is there a way to access/retrieve the attributes/fields values included in a Quick View Form from within the scripts in the parent form it is hosted?
    I’m assuming that Xrm.Page object has been added a support to access elements in quick view form control, is in it? where could I find information about this?

    1. Mehul Mehta

      Hi Mark,
      yes you can access fields displayed in quick forms from the parent form; i have done it and it works fine. There is an example in SDK to do that; please have a look else let me know and i can post code snippet for you.

  5. Mehul Mehta

    Hi all, we have one typical issue by using quick view form using quick view control. From SDK it says information displayed in quick view form are read only which i can see working for the fields but when it is a subgrid(especially N:N related records) it shows ‘delete’ icon when you mouse hover the record. This is potentially problem for us as user can now accidentally remove the record. Any suggestion how to restrick delete option for subgrid in quick view form.


  6. dhkumara

    Hi Gareth and others,

    Thanks gareth for this post and explanation!
    I have one quick question. Can we have control loading of Quick view subrgid records.
    Let’s say i have 1 webresource which creates tab (tab1 has 2 subrgrids and tab also 3 and tab 3 also has 2 subgrids) so total 6 subgrids on a form. and if i click finAccount(tab1) html WR then it should only 2 subrgids and leave another for subrgids and same way if i click any HTML form tabs only related placed subgrid should be loaded. Is this possible then how?



Leave a Reply

Fill in your details below or click an icon to log in: Logo

You are commenting using your account. Log Out /  Change )

Google photo

You are commenting using your Google account. Log Out /  Change )

Twitter picture

You are commenting using your Twitter account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )

Connecting to %s