---
title: Changes
slug: blueprint/changes
docTags: kEeQ6vT7FPx-7PjzNcWzO
createdAt: 2026-05-24T15:32:35.829Z
---

:::CtaButton{label="🔵 ALC" openInNewTab="false"}

:::

The Changes tab provides version control for PAD Flows, including automatic change tracking, visual comparison between versions, user attribution, and the ability to restore any previous version.

***

# Versioning Types

Blueprint supports two versioning types, configurable in **Settings** -> **RPA Management** -> **Analyze**. The type selected determines how and when Flow versions are captured.

- **Blueprint Versioning** — a new version is recorded each time the Flow is imported into Blueprint, either manually or automatically after 24 hours if the Flow has been modified. Blueprint does not mirror every version saved in PAD
- **Microsoft Versioning** — Blueprint fetches every version that exists for the Flow in Power Platform; all versions are retrieved on page refresh

***

**Blueprint Versioning fields:**

- **PAD Modified Date** — date and time the version was modified in Power Platform
- **PAD Modified By** — developer who modified the version in Power Platform
- **Imported Date** — date and time the version was imported to Blueprint
- **Imported User** — user who imported the version; displays "Blueprint System" for automatically retrieved versions
- **Actions** — number of actions in this version
- **Comment** — editable field for user comments

***

**Microsoft Versioning fields:**

- **PAD Modified Date** — date and time the version was modified in Power Platform
- **PAD Modified By** — developer who modified the version in Power Platform
- **Version Type** — displays Published, Latest Save, or Previously Published; rows without "Published" were saved as drafts in PAD
- **Actions** — number of actions in this version; click the icon to fetch the count
- **Comment** — editable field for user comments

***

# Comparing Versions

Select any two versions using the checkboxes and click **Compare** to view changes across two tabs:

1. **Subflows** — click any changed subflow to see a detailed breakdown:
   - **Differences** — deletions shown in red strikethrough, additions shown in green
   - **Older Version** — actions from the original version
   - **Newer Version** — actions from the newer version

:::hint{type="info"}
ⓘ The tabs shown depend on the change status of the selected subflow. An unchanged subflow only shows the Newer Version tab.
:::

2. **Variables** — displays all input, output, and Flow variables that changed between the selected versions; deletions in red strikethrough, additions in green

***

# Restoring a Version

::::WorkflowBlock
:::WorkflowBlockItem
Select the version you want to restore using the checkbox
:::

:::WorkflowBlockItem
Click **Restore**
:::

:::WorkflowBlockItem
Confirm in the popup dialog
:::
::::

:::hint{type="info"}
ⓘ Restoration requires at least two saved versions. Blueprint creates a copy of the selected version in your linked Power Automate Desktop environment, matching the exact state of the Flow at that time.
:::

***

# Schema V1 Flow Versions

When **Migrator** creates PAD Flows, they are stored in Dataverse schema v1. The first time a developer edits the Flow, it is saved in schema v2 going forward. Versions stored in schema v1 are marked with **V1\*** in the version list.

:::hint{type="info"}
ⓘ Comparing a schema v1 version with a schema v2 version will show both developer changes and schema differences, which may appear confusing. Blueprint highlights schema v1 versions and displays an explanatory note where this applies.
:::