Quick View forms are awesome, they are peekaboo utility for your records and can be used when summary information is required. There are some restrictions in place to make these forms fast and efficient.
One of the restrictions is that all formatting options for controls are taken away. As usually the case, baby was thrown out with the bathwater – it’s now impossible to set control to display multiple lines for, you know, multi-line text field. (And before you start pointing out that there are quick forms for cases and some other entities that display description fields on multiple lines: create a new quick form and try adding the description field to it. See? Those are system forms, created by CRM gods, after all).
David “CRM Baker” Crook to the rescue with some xml-twisting tip.
- Create new or edit an existing quick form.
- Add multi-line text field to the form as you normally would.
- Complete the form, publish.
- Create new solution, add the entity but select only that quick form (to keep xml shorter and things simpler).
- Export the solution as unmanaged.
- Extract customizations.xml from the zip file.
- Using your favorite xml editor, find the row and the cell elements that contain the control.
- Add rowspan attribute to the cell element.
- Add appropriate number of <row /> elements so that total number of rows is correct.
- If your <form> element has maxwidth attribute, ditch it.
- Save the file, add it to the solution zip file replacing the existing one.
- Import solution, publish.
Your XML should look like the following:
<rows> <row> <cell id="guid" showlabel="false" locklevel="0" rowspan="4"> <labels> <label description="Description" languagecode="1033" /> </labels> <control disabled="false" id="description" classid="guid" uniqueid="guid" datafieldname="description" /> </cell> </row> <row /> <row /> <row /> </rows>
I believe that this gymnastic is unsupported but like that ever stopped us before, right? Supported, people, supported, what Tanguy said.