Microsoft Dynamics® CRM Training
Customizing the Header
An error occurred while loading the video. Please try again.
In Microsoft Dynamics CRM, the December 2012 Service Update brought support for new forms for five entities: Account, Case, Contact, Lead, and Opportunity. When I switch between the new forms and classic forms, I am not switching forms, but merely changing the interface of the same form. The new interface will be referred to as the "flow" form. I will call the older interface the "classic" form.
The classic form has a header that contains read-only fields. In the new flow forms, the header appears in the upper right-hand corner, and each field is larger, and represented as an orange tile. Beyond the cosmetic changes, and perhaps the most important improvement, is that these fields are no longer read-only.
In this tutorial, we are going to learn the rules of formatting the header, for both the flow forms and classic forms.
One of the first things many users notice about the flow form is the absence of the ribbon. Yes, there is a command bar, but how do you replace the many buttons of the ribbon? One button that is omitted from the command bar is the “Assign” button; however, since the header fields are no longer read-only, I can simply reassign a record by changing the Owner field. Note that the Owner field in the header is a required field, as noted by the red asterisk.
Now, watch what happens to the header when I switch to classic mode. The fields are once again read-only. Therefore, I need the Assign button in the ribbon. Without it, I have to maximize the Header section in the body of the form.
When required fields appear in the Header, the Owner field in this example, but are not present in the body of the form, Dynamics CRM automatically creates the Header section. This allows users to edit what would otherwise be a non-editable field. This rule applies to all required fields, even though I can reassign the Owner by using the Assign function in the ribbon. If I want to get rid of this section, I have to add the Owner field to the body of the form.
Now, I want to add and remove some fields to the header to tailor it to my business. When I open the Form Editor, you will notice that it resembles the classic form; however, I can still edit the flow form. I just need to make sure that the correct form is selected. See the form selector in the navigation pane? The old form is named “Information”, and the new flow form takes the name of whatever entity is being worked with; “Lead” in this example. I open the Form Editor, and then click Header in the ribbon.
Now that I have selected the header, I can add and remove fields just as I would the body of the form. The Header can be one to four columns wide and can also support as many rows as I want. I can even remove this Owner field if I add it to the body. I'll leave the field as is, and instead add another row of four fields, so I end up with a header with two rows of four fields; eight fields all together. I save, publish, and open the record once again.
When the flow form opens, notice that only four of the eight fields are displayed. The flow form can only display the top row of fields. When I switch to classic though, I can see all eight fields.
The header of the flow form saves space over the classic version by removing redundant features, but cannot display as much information. However, it is more user-friendly, and features editable data regarding the open record.
For more tips, tricks, and tutorials, please refer to the Success Portal or our xRM.com blog.