Supporting "Required" status for Dynamic Form fields

PipeLaunch Chrome Extension has certail limitation when it comes to supporting Salesforce look and feel, particularly regarding the Dynamic layouts and FlexiPages.



IMPORTANT: PipeLaunch Chrome Extension does not support the "Required" status for fields set in Salesforce Dynamic Forms.


The main reason behind this limitation is tied to how Salesforce handles mandatory fields in Dynamic Forms versus Standard Layouts. Here's a breakdown:


  1. Dynamic Forms vs. Standard Layouts: In Dynamic Forms, the "Required" status of a field is stored in FlexiPage metadata. This metadata is not accessible via the Layout or Field Describe APIs, which are the APIs our extension relies on. As a result, the extension cannot detect these fields as mandatory.
  2. Permissions and Tooling API: Accessing the FlexiPage metadata requires the Tooling API, which is not universally accessible to all users. Granting access to this API can pose significant security risks, and it would lead to inconsistent behavior where only users with broader permissions could see fields as required.
  3. API Call Volume: Fetching this metadata would require a large number of API calls, which could negatively impact performance and lead to dissatisfaction among clients already concerned about high API usage.
  4. Reliability: Introduction of Dynamic Forms metadata might cause inconsistencies in fields and layouts display based on level of API access users have

Updated on: 13/03/2026