Why "Required" fields from Dynamic Forms aren't enforced in the Browser Extension

The PipeLaunch Browser Extension supports field-level required status set in two places:

Field-level settings: fields marked as required in the Object Manager field definition
Page Layout settings: fields marked as required on a Standard Page Layout

These are both accessible through Salesforce's standard APIs, which the extension uses to determine which fields to enforce.

However, Dynamic Forms (FlexiPages) are not supported. Salesforce stores Dynamic Forms field requirements in FlexiPage metadata, which isn't accessible through the APIs the extension relies on.

Set required fields at the field level or on Standard Page Layouts to ensure they are enforced across both Salesforce and the Chrome Extension.

Workaround

If you need a field to appear as required in the Chrome Extension, set it as required either at the field level or on your Standard Page Layout. This will be picked up by the extension regardless of your Dynamic Forms configuration.

Technical details

For those interested in why this limitation exists:

API accessibility: FlexiPage metadata is not exposed through the Layout or Field Describe APIs. The only way to access it is via the Tooling API, which requires elevated permissions that not all users have.
Inconsistent behavior: Because Tooling API access varies by user, enforcing Dynamic Forms requirements would mean some users see a field as required while others don't, depending on their permission level.
Performance: Retrieving FlexiPage metadata requires additional API calls per record type and object, which would increase load times and contribute to higher API consumption.

Updated on: 16/03/2026