Access and manage the main form properties
This topic applies to Dynamics 365 Customer Engagement (on-premises). For the Power Apps version of this topic, see: Model-driven app form properties
You can access Form properties in solution explorer. Under Components, expand Entities, expand the entity you want, and then select Forms. In the list of forms, open the form of type Main. Then on the Home tab, select Form properties.
The following table lists the form properties:
| Tab | Property | Description |
|---|---|---|
| Events | Form Libraries | Manage which JavaScript web resources are available in the form and the order in which they will be loaded. |
| Event Handers | Configure which JavaScript functions from the Form Libraries will run for the OnLoad and OnSave form events and the order in which they’ll be run. |
|
| Display | Form Name | Enter a name that will be meaningful to people. This name will be shown to people when they use the form. If they can use multiple forms configured for the entity they will use this name to differentiate between available forms. |
| Description | Enter a description that explains how this form is different from other main forms. This description is only shown in the list of forms for an entity in the solution explorer. | |
| Form Assistant | Select from the check box if you want to enable form assistant or view the form as expanded by default. | |
| Page Navigation | You can choose not to show navigation items. In forms for updated entities this means the primary name value for the record currently being viewed will not appear in the navigation bar to allow navigation to associated views. In forms using the classic presentation, the navigation options to choose associated views on the left side of the form will not be shown. |
|
| Image | When an entity has an image field and the entities’ Primary Image option is set, this setting will enable showing the image field in the header of this form. See Enable or disable entity options for more information about entity options. |
|
| Display | Enter in pixels the max width that you want for the form here. | |
| Parameters | Parameters | Each form can be opened with code using a URL. The URL may also contain data that can be passed to the form using a query string that is appended to the URL. Query strings look like this example:?p_firstName=Jim&p_lastName=DalyAs a security measure, forms will not accept any unknown query string parameters. Use this parameters list to specify parameters this form should accept to support code that will pass data to the forms using a query string. The name and type of data will be checked and the form won’t open if invalid query string parameters are passed to it. Note: The name cannot start with an underscore () or crm\. It must start with alphanumeric characters followed by an underscore (_). For example, parameter_1 or 1_parameter. The name cannot contain hyphens (-), colons (:), semicolons (;), commas (,) or periods (.). |
| Non-Event Dependencies | Dependent Fields | Each event handler has a similar Dependent Fields property so that any fields that are needed by the script can be registered. Anyone who tries to remove the dependent fields will not be able to. Some scripts operate on the form but are not configured in an event handler. Scripts that are initiated from the command bar do not have a place where dependent fields can be registered. This form property provides a place for dependent fields for those scripts to be registered. |