Process Compare — User Guide

Overview

Process Compare (Flow Parity) checks whether Power Platform workflows — Cloud flows, Classic workflows, and other process types — are enabled or disabled across Dataverse environments. It matches processes by unique ID first, then by name, and highlights any status mismatches.

Prerequisites

Two or more active connections to Dataverse environments
Read access to the workflow entity in each environment

Getting Started

Select Process Compare from the sidebar
Select the Source and Target environments

Workflow

1. Choose Environments

Source — The reference environment (e.g. Production)
Target — The environment to compare against (e.g. UAT or Development)

2. Load Processes

Click Load to fetch all workflows from both environments.

The plugin supports all workflow types:

Type	Includes
Cloud flows	Modern Power Automate flows
Classic workflows	Legacy synchronous/asynchronous workflows
Business process flows	Multi-step guided processes
Actions	Custom process actions

3. Review the Comparison

Results are displayed in a table with one row per matched process:

Column	Description
Name	Process display name
Type	Workflow type
Source Status	On / Off in the source environment
Target Status	On / Off in the target environment
Match	How the process was matched: by ID or by name
Status	✅ Match / ⚠️ Mismatch / ➕ Source only / ➖ Target only

Rows with a mismatch or missing status are highlighted for quick identification.

4. Filter Results

Use the filter bar to show:

All processes
Mismatches only — processes where On/Off status differs
Source only — processes not found in target
Target only — processes not found in source

5. Export

Click Export to download the full comparison as CSV or Excel.

Matching Logic

Match by unique ID — Processes with the same workflowid are matched first
Match by name — Remaining unmatched processes are paired by display name (case-insensitive)
Unmatched — Processes that cannot be paired appear as "Source only" or "Target only"

Tips

Tip	Detail
Run post-deployment	Check after every solution deployment to confirm flows are turned on in the target
ID matching is more reliable	Flows deployed via solution retain the same ID — name-only matches may produce false positives
Disable in lower environments	It is expected for flows to be Off in Dev/Test — filter to mismatches to focus on real issues

Troubleshooting

Problem	Resolution
Process not listed	The workflow may have been deleted or is not visible to your security role
All processes show as "Source only"	Confirm the target connection is correct and the solution has been deployed
Match shows wrong pairing	Rename the flow consistently across environments for reliable name matching