DevOps Center: Flow "Check for Matching Records" Setting Disabled on Deployment

[jdamiens]

When deploying a Salesforce Flow via DevOps Center, we've identified an issue where the "Check for Matching Records" feature within "Create Records" or "Update Records" DML operations is consistently disabled in the target environment after deployment, despite being enabled in the source environment.

Problem Description:
If a Flow contains a "Create Records" or "Update Records" element with the "Check for Matching Records" checkbox selected (enabled) in the source sandbox, DevOps Center deploys this Flow to the target environment (e.g., UAT, Staging, Production) with this specific setting automatically deselected (disabled). This behavior forces a manual correction: we must open the deployed Flow directly in the target environment, create a new version, and re-enable the "Check for Matching Records" option.

Steps to Reproduce:

1. Source Environment (e.g., Developer Sandbox):

   • Create a new Salesforce Flow (e.g., Screen Flow or Autolaunched Flow).
   • Add a "Create Records" or "Update Records" element to the Flow.
   • Configure this DML operation and ensure the "Check for Matching Records" checkbox is enabled (selected).
   • Save and activate the Flow.

2. DevOps Center:

   • Commit this Flow metadata to a new Work Item in DevOps Center.
   • Promote and deploy this Work Item through your pipeline stages to a higher environment (e.g., Production).

3. Target Environment (e.g., Production):

   • After the deployment completes successfully, navigate to the deployed Flow in the target environment.
   • Open the "Create Records" or "Update Records" element that was configured with "Check for Matching Records" enabled in the source.

Expected Behavior:
The "Check for Matching Records" setting within the "Create Records" or "Update Records" element of the deployed Flow should remain enabled, reflecting its configuration in the source environment.

Actual Behavior:
The "Check for Matching Records" setting is found to be disabled in the deployed Flow, requiring a manual adjustment in the target environment.

Impact:

• Increased Manual Work: Requires post-deployment manual intervention for every affected Flow, adding overhead and potential for human error.
• Pipeline Desynchronization: The version of the Flow in the target environment (after manual correction) no longer matches the version stored in the DevOps Center Work Item and its associated Git branch. This complicates future deployments and version control.
• Reduced Trust in Automation: Undermines the reliability and consistency expected from a CI/CD pipeline managed by DevOps Center.
• Data Integrity Risk: If the "Check for Matching Records" feature is critical for preventing duplicate records or ensuring correct updates, its unexpected disabling could lead to data integrity issues.