Create or edit the main form for an entity
When you create a new form for an entity, its form type is Main. When the new form opens, it is identical to the form named Information. You can add or edit fields, sections, tabs, and navigation, and properties associated with the form, and then save it with a new name.
This procedure works for any form with a Form Type of Main. Each 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.
If you want to base your new form on an existing form, you can clone a form. More information: Create a new form based on an existing form
- In the Navigation Pane, click Settings.
- Under Customization, click Customizations.
- In the Customization area, click Customize the System.
- Under Components, expand Entities, and then expand the entity you want.
- Click Forms.
To create a new form, in the main pane on the Actions toolbar, click the New button.
- OR -
To edit an existing form, double-click any form with a Form Type of Main.
- Make any of the following design changes, as needed:
- Edit the properties for parts of the form, as needed:
- Add event scripts, as needed. More information: Add or edit event scripts for fields and forms
- Determine which security roles will be able to view the form:
- Preview how the main form appears and how events functions:
- On the Home tab, click Preview, and then select Create Form, Update Form, or Read-Only Form.
- To close the Preview form, on the File menu, click Close.
- When you finish editing the form, click Save As. Enter a name for the form, and then click OK.
- When your customizations are complete, publish them:
- To publish customizations for only the component that you are currently editing, on the Home tab, in the Save group, click Publish.
- To publish customizations for all unpublished components at one time, click Publish All Customizations.
- You can not apply a requirement level to a field using this form. Requirement level constraints are applied to the attribute.
- Before deleting 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 such as custom entities, relationships, or fields 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.