UiPath to PAD Migration Output Details

UiPath to PAD Common Items

Selectors

PAD supports the following attributes and technologies when converting selectors from UiPath

Technology

Attributes

Notes

Web

tag, id, aaname, name, idx, type, tablerow, tablecol, css-selector, class, src, title

UIA

app, title, cls, name, role, automationid, idx, ctrlname, aaname, tableRow, tableCol

AA

app, title, cls, name, role, ctrlid, idx, ctrlname, aaname, text

Direct support not yet available in PAD.

Java

title, app, cls, idx, aaname, role, name, virtualname, tableRow, tableCol

SAP

app, title, id, idx

OCR / Native Text

Not supported

When possible Blueprint will create multiple selectors per UI element to increase the possibility of a matches.

Parent Attributes

In UiPath, parent attributes are not in fact parent attribute, they are ancestor attributes. For example, when a selector has parentName="container" this means that the first ancestor to have a name, is container. This ancestor is not necessarily the parent. Furthermore, if a selector has multiple parent attributes, for example parentclass and parentid, those attributes do not necessarily reference the same ancestor.

Anchors

Anchors are supported using the :has() pseudo selector in PAD.

VARIABLES

  1. UiPath Global Variables
    Setting these variables will help improve migration quality.

    Variable

    Behavior

    How to Reconcile in PAD

    %BasePath%

    In UiPath, relative file or folder paths are relative to the main xaml file. In PAD, relative file or folder paths are relative to PAD installation folder.

    Set %BasePath% where specific project files will be located after migration

    %SPECIAL_FOLDER_X%

    Possible Special Folders:

    ApplicationData, CommonApplicationData, LocalApplicationData, Cookies, Favorites, History, InternetCache, Programs, MyMusic, MyPictures, Recent, SendTo, StartMenu, Startup, System, Templates, DesktopDirectory, Personal, ProgramFiles, CommonProgramFiles

    Set %SPECIAL_FOLDER_X% where specific folder will be located after migration

Mid-Value Wildcard Support in Selectors

As of the 8.3 release, Blueprint now supports mid-value wildcards when migrating selectors from UiPath to Power Automate Desktop (PAD).

What Are Mid-Value Wildcards?

Mid-value wildcards are wildcard characters (typically *) used within a string value, not just at the beginning or end. For example:

  • btn-*submit matches btn-primary-submit, btn-secondary-submit, etc.
  • file-*2025*.csv matches file-report-2025-Q1.csv, file-2025-summary.csv, etc.
Migration Behavior

When migrating from UiPath to PAD:

  • UiPath selectors that use mid-value wildcards (e.g., aaname='btn-*submit') are now preserved and translated into equivalent PAD selector formats.
  • PAD supports these patterns using regex or wildcard syntax, depending on the control type and selector engine.
Example

UiPath Selector:

<wnd app='app.exe' title='*Invoice*2025*' />

PAD Equivalent:

Window title: *Invoice*2025*

This ensures that dynamic or partially known values in selectors are retained, improving automation reliability.

.NET Script Imports

Update as of V.8.3

Improved Namespace Handling in PAD Migration

As part of the UiPath to PAD migration process, Blueprint now automatically assigns the necessary .NET namespaces to the %defaultRunDotNetScriptImports% variable on a per-XAML basis.

Why This Matters:
  • Ensures that each script has the correct context to run without manual intervention.
  • Reduces the need for users to troubleshoot missing namespace errors.
  • Aligns with PAD’s best practices for modular and maintainable automation flows.
Tip:

You can still override or customize the %defaultRunDotNetScriptImports% variable if needed, but the default values provided by Blueprint should cover most use cases.

 Generate Data Table from Text (CSV Parsing)

New Mapping Support as of V.8.3

Blueprint now supports automatic mapping of the UiPath "Generate Data Table" activity to Power Automate Desktop's "Convert text to data table" action using the CSV parsing method.

 What This Means:
  • When a UiPath workflow includes the Generate Data Table activity with CSV-style input, Blueprint will now convert this to the equivalent PAD action.
  • The PAD action will be configured with:
    • Column delimiter set to ,
    • Row delimiter set to \n (or as detected)
    • First row as header enabled if applicable
Example Mapping:

1 Generate Data Table

2 Input: "Name,Age\nAlice,30\nBob,25"

PAD Output:

1 Action: Convert text to data table

2 Text: "Name,Age\nAlice,30\nBob,25"

3 Column delimiter: ,

4 Row delimiter: \n

5 First row contains column names: Yes

 Notes:
  • This mapping is only applied when the input format clearly matches CSV structure.
  • For non-CSV formats, manual adjustments may still be required post-migration.

Select Menu Item Mapping

New Mapping Support – V.8.3

Blueprint now supports mapping the UiPath "Select Item" activity used in SAP GUI automation to the equivalent Power Automate Desktop (PAD) SAP action.

What’s New:
  • When a UiPath workflow includes a Select Item activity targeting an SAP menu or dropdown, Blueprint will now generate a PAD SAP GUI automation step that selects the corresponding item.
  • This mapping uses PAD’s “Populate text field on SAP screen” or “Click UI element in window” actions, depending on the SAP control type.
Example Mapping:

UiPath:

1 Activity: Select Item

2 Target: SAP Dropdown

3 Item: "Create Sales Order"

PAD Output:

1 Action: Click UI element in window

2 Target: SAP GUI element with selector for dropdown

3 Followed by: Send keys or select item logic

Notes:
  • This mapping is only applied when the SAP selector is clearly identifiable and the control supports interaction in PAD.
  • In cases where the SAP control is not natively supported in PAD, a fallback to keyboard navigation or scripting may be used.

How did we do?