Prodly’s new data processing logic was implemented to enhance performance, precision and accuracy of deployments. Users can now choose to activate this logic while running org to org deployments and for new features rolled out for Version Control deployments.

Enable Next Generation Data Processing:

1. Visit Release Tab.
2. Visit Settings.
3. Scroll to the Next Generation Data Processing toggle in the Deployments section.
4. Toggle on to activate. Users can activate and deactivate the feature with the toggle at any time.

<aside> <img src="/icons/info-alternate_blue.svg" alt="/icons/info-alternate_blue.svg" width="40px" />

To enable Next-Gen Data Processing, users must be granted the custom permission set PDRI.Prodly Next-Gen Data Deploy.

</aside>

Assigning the Next-Gen Custom Permission

To use Next Generation Data Processing, users must be granted the PDRI.Prodly Next-Gen Data Deploy custom permission.

<aside> <img src="/icons/info-alternate_blue.svg" alt="/icons/info-alternate_blue.svg" width="40px" />

This custom permission is not included in the standard Prodly AppOps Admin or User permission sets and must be assigned manually by one of the following standard Salesforce methods.

</aside>

Option A: Add to a Profile

Edit the desired user Profile and add PDRI.Prodly Next-Gen Data Deploy to the "Enabled Custom Permissions" related list. This method is straightforward for organizations with a simple profile structure.

Option B: Use a Dedicated Permission Set (Recommended)

For more granular and scalable control, create a new Permission Set. Add the single PDRI.Prodly Next-Gen Data Deploy custom permission to this set, and then assign the new Permission Set to all relevant users. This is the recommended best practice for managing access.

Key considerations

• Failure to grant the custom permission will restrict users from deploying with Next Gen functionality.
• Users require both the toggle enabled and the custom permission granted to utilize Next Gen Data Deploy. If desired, they can disable the toggle in their settings to deploy without Next-Gen Data.

Supported Features

1. Org to Org Deployments
2. Deploy From Branch: Use a Data Set