Set up DataQ Dynamic Forms

Two components have been specifically developed to handle Salesforce Dynamic Forms:

• dqeone:DQE_Create_Record_Dynamic: overrides the New button
• dqeone:DQE_Edit_Record_Dynamic: creates a new Edit button and replaces the standard edit action

The following conditions must be met.

Dynamic Form requirements

• The DQE_One_Tooling_API named credential must be authenticated (Setup > Named Credentials > DQE_One_Tooling_API > Authenticate). While it is in Pending status, Tooling API calls fail and the override will not activate correctly — see About the DQE_One_Tooling_API status below.

• A Lightning Record Page assigned at the profile or app level must be configured for the application in which the creation form will be opened.

OR

• A Lightning Record Page defined at the Org Default level and labelled as follows: [SObjectName]_Record_Page

OR

• Only one Lightning Record Page is defined for this SObject.

Supported visibility rules

Rules can be defined based on:

• the record
• the user
• the client, such as the browser or form factor

Permission-based rules are not currently fully supported.

About the DQE_One_Tooling_API status

Both dynamic components call Salesforce's Tooling API through the DQE_One_Tooling_API named credential, which is created during package installation. Until this named credential is authenticated in Setup, its status stays Pending and every Tooling API call fails.

• On the flexipage (Dynamic Forms): dqeone:DQE_Create_Record_Dynamic and dqeone:DQE_Edit_Record_Dynamic need this named credential to read the page layout. While it is Pending, they correctly stay inactive and show an error instead of overriding the button.
• On the standard form: the non-Dynamic-Forms override (dqeone:DQE_Create_Record) does not call the Tooling API, so it currently keeps overriding the button even while DQE_One_Tooling_API is Pending. This is a known inconsistency, not an intended behavior.

Always authenticate DQE_One_Tooling_API as part of the installation checklist, before assigning either override to users.