---
title: Variable Prefixing
slug: blueprint/variable-prefixing
docTags: yO7XZ9PJxDCKZ-Mf4TSYB
createdAt: 2026-04-17T18:28:53.268Z
---

:::CtaButton{label="🟢 Migrator" openInNewTab="false"}

:::

During migration, Blueprint may generate more variables in your PAD output than existed in your original process. This is intentional — it's how Blueprint preserves correct behavior in PAD's environment.

***

# Why Variable Prefixing Is Needed

Power Automate Desktop does not support variable scoping. All variables are global, meaning two variables with the same name used in different subflows can unintentionally overwrite each other.

Blueprint uses **variable prefixing** to prevent these collisions and ensure data integrity across subflows, simulating the scoped behavior of the source RPA platform.

***

# How It Works

The **Variable Prefix** toggle in the Export Wizard is enabled by default. When on, Blueprint prepends each variable with an abbreviation derived from its subflow name.

**Example:**

- Subflow: Process Invoices
- Original variable: Config
- PAD output variable: PI\_Config

This keeps variables isolated to their subflow context, preventing overlap with identically named variables elsewhere in the flow.

***

# Changing the Default Behavior

Variable prefixing can be toggled off if your organization prefers cleaner variable names and accepts the risk of collision.

::::WorkflowBlock
:::WorkflowBlockItem
Navigate to **Settings -> RPA Management -> Migrate**
:::

:::WorkflowBlockItem
Expand **Export Wizard Options**
:::

:::WorkflowBlockItem
Disable **Variable Prefix**
:::
::::

:::hint{type="info"}
ⓘ This setting applies as the default for all future exports. Individual export runs can also override it directly in the Export Wizard.
:::

***

# Automatic Prefixing on Collision Detection

Even if prefixing is disabled, Blueprint will automatically re-enable it when a naming conflict is detected during migration. This ensures the output flow won't exhibit unintended behavior due to variable overlap.