This section details how to configure our EDQ form controls to work with Power Pages forms on your external-facing websites and portals.

Limitations

Form types

Note that our integration only works with forms created from Dataverse table forms. Dataverse table forms are created by using the Data workspace in Power Pages or from model-driven apps created in Power Apps.

Code component fields

A current limitation of Power Pages means that custom PCF code components can only be bound to a single field. For our components we have chosen the mandatory Mapping name field, which means the following fields of some components can't be configured:

  • EDQEmail - Validation message, Validation timestamp
  • EDQPhone - Country code field, Validation message, Validation timestamp

Prerequisites

The following pages assume the basic application setup steps have been performed, including installation, product configuration and use of the pre-configured address mappings.

They also assume a Power Pages site already exists and has been configured with a fully functioning form containing address/email/phone fields, with all the relevant permissions configured. The following Microsoft Power Pages tutorials cover these basics, should they be required:

Configuration steps

There are 4 main steps to configuring our app for Power Pages:

  1. Downloading the EDQ Page Manager library, the JavaScript file which enables validation on your website forms and which must be uploaded to your Power Pages website.
  2. Adding the EDQ Page Manager library as a Web File within Power Pages Management.
  3. Configuring the forms on your Power Pages website to use the EDQ code components.
  4. Using our Configuration app to automatically apply all the necessary Power Pages Site Settings and Table Permissions.

By default the EDQ components will inherit the styling of your chosen Power Pages theme, but should you wish to override any of the EDQ styles you can optionally add a style override file.