This task requires the System Administrator or System Customizer security role A defined set of privileges. The security role assigned to a user determines which tasks the user can perform and which parts of the user interface the user can view. All users must be assigned at least one security role in order to access the system. or equivalent permissions. Customization tasks can be performed only while you are online. More information: Customization Permissions
The main form is comprised of one or more tabs. Each tab can have one or more sections. Each section contains one or more fields or IFRAMES Windowless inline floating frames that are typically used for including Web pages in forms. Examples of Web pages that can be included are a page from a Microsoft SharePoint site, a section of HTML such as a button, or a custom application..
In the Navigation Pane, click Settings, click Customization, and then click Customize Entities.
Open the entity and then click Forms and Views.
In the list of forms and views, select Form, then on the Actions toolbar click More Actions, and then click Edit. Make any of the following changes to the form:
To add a section, in the Common Tasks area, click Add a Section.
- OR -
Select a tab, and select the section in the tab you want to edit, and then in the Common Tasks area, click Change Properties.
On the Add a Section or Section Properties dialog box, on the Display tab, add or change the following:
In the Name box, enter a unique name for the section.
Select the Show the name of this section on the form check box to make the section name visible. Do not select it if you want the section name to be invisible. For example, if you want to use the section to group several fields together.
If you select the Show the name of this section on the form check box, you can select the Show divider line below the name of the section check box to put a divider line underneath the name of the section.
From the Width of Field's Label Area area you can specify the width of the label area of the fields. This will affect any fields you add to this setion. Set the width between 50 and 250 pixels.
From the Location list, select the tab where you want the section to be located.
On the Formatting tab:
From the Section Layout list, select the type of section layout you want. Your selection will determine the column layout, and will also control the options available on the Formatting tab for each field in the section.
The selected section layout cannot be changed after you create a section. If you decide to try a different formatting option, remove the fields from the current formatted section so that they will be available to add to another formatted section.
Variable Field Width: Fields are set up in two columns. IFRAMEs, nvarchar/textarea and ntext fields expand to the width of the form, and you can set the number of rows displayed. For other fields, you can specify whether the field is one or two columns wide.
Fixed Field Width: You can choose the column layout: either two, three, or four columns with five possible layouts. Each field can only be as wide as the column it is in. IFRAMEs, nvarchar or text area and ntext fields are displayed within one column and you can set the number of rows displayed, but cannot set them to display across columns.
To add a new field, in the Common Tasks area, click Add Fields. In the Add Fields dialog box, select the fields you want to add to the form, and optionally, from the Tab and Section lists, select the tab and section in which you want to place the selected field or fields, and then click OK.
To edit a field, select the field you want to edit, and then in the Common Tasks area, click Change Properties.
In the Field Properties dialog box, edit a field as follows:
On the Display tab you can edit the following:
Change the label used for this field. This will not change the attribute display name The label that is used by default when an attribute is displayed on a form, in a list, or in a report. The Display Name for each attribute can be changed in the Customization area by a user with an appropriate security role., just the text in this form.
If necessary, select the Display label on the form check box to make the label visible on the form. Clear the check box if you want to have a field with no label, for example, if the field is the only one in a section with a clearly descriptive name.
Select Disabled on the form to make the field read-only for example, if the field displays a value calculated by a client-side script.
In the Location area, select the tab and section to which you want to move the field.
In the Locking area, specify whether you wish to lock the field to the form by selecting Lock the field on the form. This will prevent anyone from removing this field using the Remove command from the Common Tasks area. This will also protect the tab and section that contain this field from being removed.
On the Formatting tab, the formatting options displayed depend on the section formatting options. If the section formatting is defined as Variable Field Width, you can choose a layout of one or two columns and set the field to automatically expand to use available space. If the form formatting is defined as Fixed Field Width, you do not have the option of modifying the number of columns, but for ntext fields, you can define the number of rows for the field. For bit fields, you can set the formatting to Two radio buttons, Checkbox, or List.
On the Schema tab, the fields are read-only by default, and cannot be changed in the form for the entity.
On the Events tab, you can create a script that is executed when data in the field is changed:
In the Event List box, select onChange, and then click Edit.
on the Details tab, select the Event is enabled check box to enable the event, and in the text box, enter the body of the script that you want to use when the selected event is run.
On the Dependencies tab, in the Available fields list, select any fields you have referenced in scripts, and then click the Add Selected Records button to move the selected fields to the Dependent fields list.
- OR -
From the Dependent fields list, select the fields you want to remove as dependent fields, then click the Remove Selected Records button to move the selected fields to the Available fields list.
Caution: Because applications can interact with each other through an IFRAME, by default, in the Security section, the Restrict cross-frame scripting check box is selected. Remove this restriction only if you are sure the site you are using as the target of the IFRAME can be trusted.
To add an IFRAME, in the Common Tasks area, click Add an IFRAME.
- OR -
Select a tab and then the IFRAME in the tab you want to edit, and then in the Common Tasks area, click Change Properties.
On the Add an IFRAME or IFRAME Properties dialog box, on the General tab, enter the information you want. In particular, note the following:
In the Name box, enter a unique name for the IFRAME. The name can only contain alphanumeric characters and underscore.
In the URL box, enter a full URL for the IFRAME, and optionally select the Pass record object-type code and unique identifier as parameters check box. More information: Passing IFRAME parameters (Microsoft Dynamics CRM SDK)
The Restrict cross-frame scripting check box is selected by default for security purposes. Exercise great caution in allowing cross-frame scripting.
On the Formatting tab, the formatting options displayed depend on the section formatting options. If the section formatting is defined as Variable Field Width, you can choose a layout of one or two columns and set the field to automatically expand to use available space. In either case, you can determine the scrolling type, whether a border is displayed and the number of rows for the field.
On the Dependencies tab, from the Available fields list, select the fields you want to designate as dependent fields in the IFRAME, and then click the Add Selected Records button to move the selected fields to the Dependent fields list.
On the Events tab, click onSave or OnLoad, and then click Edit.
In the Event Detail Properties dialog, on the Details tab, select the Event is enabled check box to enable the event, and in the text box, enter the body of the script that you want to use when the selected event is run.
On the Dependencies tab, in the Available fields list, select any fields you have referenced in scripts, and then click the Add Selected Records button to move the selected fields to the Dependent fields list.
Click OK to close the Event Detail Properties dialog.
Click OK to close the Form Properties dialog.
Test your script in the three modes a form can be used: create, update, and read-only:
On the Preview menu, click Create Form, Update Form, or Read-Only Form.
If you have added an OnLoad event for the form, when you open the form in each mode, verify that your event executed as expected.
If you have added an onSave event for the form, for create and update modes, on the Form toolbar, click Simulate Form Save to see if the event executes as expected.
To close the Preview form, on the File menu, click Close.
Select the tab, section, field, or IFRAME you want to remove.
If the section or field is locked by default, it cannot be removed. If you have locked it, you must unlock it before removing it.
In the Common Tasks area, click Remove.
In the confirmation message, click OK.
You can preview how the main form will appear and how events will function:
On the Preview menu, click Create Form, Update Form, or Read-Only Form.
If you have added an OnLoad event for the form, when you open the form in each mode, verify that your event executed as expected.
If you have added an onChange event for a field, for create and update modes, enter the data in the field and verify that the event executes as expected.
If you have added an onSave event for the form, for create and update modes, on the Form toolbar, click Simulate Form Save to see if the event executes as expected.
To close the Preview form, on the File menu, click Close.
When you finish editing the form, click Save and Close to close the form.
When your customizations are complete, publish your customizations:
To publish customizations for the entity you are currently editing, on the Actions menu, click Publish.
To publish customizations for all entities at once, open the Customize Entities list. On the More Actions menu, click Publish All Customizations.
To publish customizations for specific entities, open the Customize Entities list and select the entities you want to publish. On the Actions toolbar, click Publish.
Notes
You can not apply a requirement level A setting that determines whether users must enter data. For example, when the requirement level of a field is set to Business Required, users will be unable to save the record without entering data in that field. The field will also appear in the Quick Create form. to a field using this form. Requirement level constraints are applied to the attribute A property of an entity with a specific data type. Attributes are analogous to columns in a database table. When attributes are added to an entity form, they are displayed as fields that correspond to their data type..
If you delete a field from a form, make sure the field is not required by other components or custom scripts. For example, the Opportunity form requires the Price List field to determine the pricing to use when adding a product to that opportunity. Removing the Price List field would prevent adding a new product to an opportunity.
Any time you change user interface elements or implement form scripts for an entity you must publish changes to apply them. Any customizations that change the data schema of Microsoft Dynamics CRM Online such as custom entities, relationships, or attributes are applied immediately.
You cannot modify the visual style of forms, such as the font style, font size, or colors used in the form using the form editor. Modification of the Cascading Style Sheets (CSS) pages in the Web application or style properties of the form through scripts is not supported.
Add or edit a script to run when the form is loaded or saved
menu, click Publish.
to move the selected fields to the 
to move the selected fields to the 