You can create a new form based on an existing form. The existing form must have a form type of Main.
By basing a new form on an existing one, you can re-use the existing form's navigation, fields, properties, event scripts, and security roles. In the new form, you can also edit these existing elements, remove them, or add new ones.
You can add or edit fields, sections, tabs, and navigation, and properties associated with the form, and then save it with a new name.
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. In the main pane, double-click any form with a Form Type of Main.
In the form that opens, you can make any of the following design changes:
Select the tab, section, field, or IFRAME that you want to remove.
Note: If a section or field is locked by default, it cannot be removed. If you have locked the section or field, you must unlock it before removing it. More information: Edit form field properties, Edit a section
Click the tab you would like to edit. Then, on the Home tab, click Change Properties. The Tab Properties dialog box opens.
On the Display tab, enter a unique name in Name.
On the Formatting tab, specify whether you would like the tab to have one or two columns.
On the Events tab, you can add and edit form libraries and the TabStateChange event, which indicates when the tab is expanded or collapsed. More information: Add or edit event scripts for fields and forms
On the Home tab, in the Form group, click Assign Roles.
In the Assign Roles dialog box, select the security roles to which this form will be available. More information: Controlling Data Access
To make this the fallback form A form, with a form type Main, that displays for any user with read access for an entity but does not have an explicitly assigned form or forms., select the Enabled for fallback check box.
At least one form per entity must be a fallback form, the form that is displayed to a user when no other form is available for that user's security role.
Click OK.
Preview how the main form will appear and how events will function:
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.
Notes
You cannot 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 through a form. You apply requirement level constraints directly to the field.
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 prevents 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.