DQE One Package Setup on PowerApps / Dynamics

Overview

The DQE One Dynamics package operates in two complementary modes:

Real-Time validation flow:

Dynamics 365 (PCF controls on forms)  ⟷  DQE Plugin (Custom API backend)  ⟶  DQE API (Webservices)

Standalone integration flow:

Dynamics 365 (Standalone tab / iframe)  ⟶  DQE Standalone (External server, URL configured in DataQ Settings)

• Real-Time validation: PCF components on Account, Contact and Lead forms call DQE webservices (Address, Email, Phone, First Name, Company) via Dynamics custom APIs. Validation happens inline as the user types.
• Standalone integration: A dedicated tab in the DQE navigation loads an external DQE application in an iframe. The Dynamics environment URL is passed as a parameter (?dynamics_org=…) to enable bidirectional context.

1. Access Setup

The DQE package includes three security roles. Assign them based on what each user needs to do.

1.1 Role assignment

• DQE administrator: assign DQE – Data Administrator.
• End users (forms): assign DQE – User.
• Standalone application user: assign DQE – Unify Application User.

1. Go to the Power Platform admin center → select the target environment.
2. Navigate to Security roles, find the DQE role, and assign it to the relevant users.
3. Click Save.

1.2 Azure App Registration

The DQE Standalone (Unify) module authenticates against Dynamics via an Azure Active Directory application. Register this application in your Azure tenant before creating the Dynamics application user.

1. In the Azure portal, go to Azure Active Directory → App registrations → New registration. Enter a name (e.g. DQE One) and click Register.
2. On the Overview page, copy the Application (client) ID and the Directory (tenant) ID. Keep these for the next steps.
3. Go to API permissions → Add a permission → Microsoft APIs → Dynamics CRM. Select user_impersonation and click Add permissions.
4. Go to Certificates & secrets → New client secret. Set a description and expiry (DQE licences are valid one year and renewable), then click Add. Copy the secret value immediately — it will not be shown again after you leave the page.

Note: Keep the Directory (tenant) ID, Application (client) ID and Client Secret in a safe place — they are required for §1.3 and §2.5.

1.3 Application User (S2S)

Create a non-interactive server-to-server (S2S) application user in the target Dynamics environment and grant it the required DQE roles.

1. In the Power Platform admin center, select the target environment and go to Settings → Users → Application users → New app user.
2. Click Add an app and paste the Client ID obtained in §1.2. Select the application from the list and click Add.
3. Select a Business Unit (optional) and click Create.
4. Open the newly created application user, click Edit security roles, and assign the following roles: DQE – Unify Application User, DQE – Data Administrator, DQE – User. Click Save.

2. Configuration

All configuration is done in DQE DataQ Settings, accessible from the DQE application navigation (Parameters → DQE DataQ Settings). The navigation redirects automatically to the single configuration record.

2.1 Package Installation

The DQE One managed solution must be installed in the target Dynamics Sales or Power Apps environment before proceeding with any configuration below.

2.2 Licence Activation

Enter the licence key and enable the webservices covered by the customer's contract.

1. In DQE DataQ Settings → General, enter the DQE Licence key provided by your DQE project manager.
2. Set each subscribed product to Yes. Only activate what is in the customer's contract:

1. Click Save & Close.

2.3 API URL

The DQE API URL is the address of the DQE webservice server. It is used by the Dynamics backend plugins to call validation APIs (address, email, phone, name, company).

1. In DQE DataQ Settings → General, locate the API URL address field.
2. Enter the URL provided by your DQE project manager.
3. Click Save & Close.

Note: The DQE Metadata entity present in earlier versions of the package has been removed. The API URL is now managed directly in DataQ Settings.

2.4 Standalone URL

The Standalone URL points to the external DQE Standalone application. It is displayed in an iframe inside the Standalone tab of the DQE navigation.

1. In DQE DataQ Settings → General, locate the Standalone URL field.
2. Enter the URL provided by your DQE project manager.
3. Click Save & Close.
4. Navigate to the Standalone tab in the DQE application to verify the iframe loads correctly. If the URL is unreachable, an accessibility warning is displayed with an option to edit the URL inline.

Important: The Standalone URL must be publicly accessible from the user's browser. It is not called server-side — the browser loads it directly inside the iframe. Make sure CORS and firewall rules allow access from Dynamics users' networks.

2.5 Standalone Credentials

To connect the Standalone application to your Dynamics 365 environment, you must add a Dynamics credential directly inside the Standalone interface. These credentials are provided by your DQE project manager and correspond to an Azure AD application registered against your tenant.

1. Log in to the DQE Standalone application.
2. Open the User Profile and navigate to the Credentials section.
3. Click New and select Microsoft Dynamics as the connector type.
4. Fill in the four required fields:

1. Click Log In. The Standalone server authenticates against Dynamics and stores the credential for future use.

Note: The Dynamics application user linked to this credential must have the DQE – Unify Application User security role assigned in the Power Platform admin center.

Once the package is configured, proceed to set up each webservice individually in the form editor. See Configure address, email, phone and B2B validation in Dynamics.