Define entity forms and custom logic within the Dynamics 365 for Customer Engagement portal

A data-driven configuration to allow end users to add a form to collect data in the portal without the need for a developer to surface the form in the portal, entity forms are created in Dynamics 365 for Customer Engagement and then placed into webpages in the portal or used in conjunction with subgrids and entity lists to build out complete web applications. More information: Add a webpage to render a list of records

Contact us form

Add a form to your portal

The entity form contains relationships to webpages and additional properties to control the initialization of the form within the portal. The relationship to webpages allows dynamic retrieval of the form definition for a given page node within the website.

To view existing entity forms or to create new entity forms, go to Portals > Entity Forms.

When creating a new entity form, the first step is to decide the Entity and Form Name that you will be rendering, in addition to the mode: Insert, Edit, or Read Only. The mode selected will determine if you are creating a new record from the portal, editing an existing record, or just displaying information about a record on the portal.


  • An Entity Form must be associated with a webpage for a given website for the form to be viewable within the site.
  • The Connection entity subgrids are not supported in entity forms. If you add a Connection entity subgrid to the form using Form designer, error messages are displayed when you render the form on the portal and use the Connection entity.
  • Duplicate fields, multi-select option set, and custom controls are not supported in entity forms.
  • If you create an entity form in the Insert mode, you can't change a button's alignment or place an action button above the entity form.
  • If you render a lookup control as a dropdown list on the form, the related records filter does not work.

The webpages associated with the entity form can be viewed by selecting the Web Pages link listed in the Related navigation links in the leftmost menu.

When creating or editing a webpage, an Entity Form can be specified in the lookup field provided on the Web Page form.

The various master pages used by the portal found in the Dynamics 365 for Customer Engagement portal installation directory contain declarations of the EntityForm server control. When rendering the webpage containing either the Page (/Pages/Page.aspx) page template or Full Page (/Pages/FullPage.aspx) page template, the controls will determine whether the entity form lookup contains a value, in which case the form will be rendered.

Secure your forms

To secure your forms, you must create entity permissions that determine access and ownership of the records in Dynamics 365 for Customer Engagement according to web roles. If a user lands on an entity form and does not have permissions, they will receive an error message. To enable permissions for an entity form, set Enable Entity Permissions to true. More information: Create web roles for portals.

Geolocation configuration for entity forms

A managed form can be configured to display a map control to either display an existing location as a pin on a map or to provide the ability for the user to specify a location. See Add Geolocation.

The form's map control requires additional configuration to tell it what the IDs of the various location fields are, to assign values to them or retrieve values from them. The Entity Form record in Dynamics 365 for Customer Engagement has a configuration section that defines these field mappings that you must specify. The field names will vary depending on the schema you have created.

Geolocation data in entity form


  • The address field in a read-only entity form is replaced with the map when geolocation is enabled.
  • The Geolocation section is not visible in the German Sovereign Cloud environment. If a user has enabled geolocation by using a different form, it will not be displayed during rendering on portal.

See also

Configure a Dynamics 365 for Customer Engagement portal
Web Form properties for portals
Web Form steps for portals
Web Forms metadata for portals
Web Form subgrid configuration for portals
Notes configuration for Entity Forms and Web Forms for portals