Excel_Utility like Blue Prism?

(1) Share

Report

Posted on by Syed_Reyasdeen

I am planning to create a utility similar to Blue Prism. I will develop a Power Automate flow named Excel_Utility, where I will organize multiple sections, (PAGES) each handling a specific action (e.g., read data, write data). Instead of creating separate flows for each action, this single utility flow will consolidate all Excel-related operations. (Each Page one action)

If I use the Excel_Utility across multiple bots, will any connection issues occur? Is this approach advisable from the Microsoft platform perspective?

I am worried that creating a separate subflow for each action will be very hard to manage, especially if there are hundreds of subflows.

Categories:

Power Automate Desktop

I have the same question (0)

All responses (2)

Answers (0)

Sort by

Suggested answer

Valantis 6,735 on at

Like
a
(1)

Report
Copy link

Link copied!

Hi @Syed_Reyasdeen,

The pattern you're describing is valid and Power Automate Desktop does support it via subflows within a single desktop flow.

Organizing Excel operations as separate subflows (pages) inside one parent flow is a clean architecture.

On your connection concern: desktop flows don't have shared connection issues the way cloud flows do. Each bot run executes the desktop flow in its own machine session so there's no conflict between bots using the same flow definition.

However there are two practical considerations:
1. The Excel_Utility flow will run on a machine. If multiple bots try to call it simultaneously they'll queue on that machine. For parallel execution you'd need multiple machines or a machine group.
2. Calling subflows across separate desktop flows isn't natively supported in PAD. Subflows live inside a parent flow and can only be called from within that same flow. If you want multiple bots to reuse Excel logic, the options are: embed the Excel_Utility subflows into each bot's flow, or use a single parent desktop flow that all bots trigger with different input parameters to select which Excel action to run.

The second approach (one parameterized flow with an input that selects the action, like a Switch on an input variable) is probably closest to what you're describing and is manageable.

Best regards,

Valantis

✅ If this helped solve your issue, please Accept as Solution so others can find it quickly.

❤️ If it didn’t fully solve it but was still useful, please click “Yes” on “Was this reply helpful?” or leave a Like :).

🏷️ For follow-ups @Valantis.

📝 https://valantisond365.com/

💼 LinkedIn

▶️ YouTube

Was this reply helpful? Yes No
Suggested answer

11manish 3,333 on at

Like
a
(0)

Report
Copy link

Link copied!

I would not recommend building a single Excel_Utility flow that contains every Excel action. Likewise, creating a separate flow for every individual action can

become difficult to govern.

A modular utility framework, where related Excel operations are grouped into a small number of reusable utility flows, aligns better with Microsoft Power

Automate best practices and provides a scalable architecture similar to the Business Object model used in Blue Prism.

This approach offers the best balance between maintainability, reusability, performance, and long-term supportability as your automation estate grows.

Was this reply helpful? Yes No