top of page

About Power Automate

May 7
2 min read

It's been ages since my last post.

I've reached this point after repeatedly experiencing setbacks and restarts. A lesson learned.

Looking back at my blog, it seems I've been neglecting it for about a year.


To begin with, I'm slow to realize things. I only realized this again after restarting this project.

Here's a summary:


1. Power Automate has two products, and I mistakenly assumed that both could be developed in the same way.

a, Power Automate Cloud

As the name suggests, this will primarily operate in the cloud. It is advisable to save Excel files and other similar files to OnDrive.

b, PowerAutomte Desktop

・As the name suggests, this is primarily intended to run on a local PC.


I think I found similar information online.

If that was the only difference, I could have tolerated it to some extent.

The development process changes considerably once we actually begin development.


2. Is the difference in concept so significant that they seem like completely different products? Or rather, wouldn't anyone involved in the development struggle with this?

a, Power Automate Cloud

- Variables exist, but they cannot be used in a self-referential manner. For example, something like X = X + 1 is not possible.

- Use the Compose action to set values, and generally avoid setting variables.

The settings seem manageable if you understand Excel functions.

b, PowerAutomte Desktop

Variables can be used to generate variable values.

- Subroutines (subflows) can also be created, making it possible to split modules.

・Although there are some restrictions, I think it's easier for those with development experience to get in here.


It took me about a year to realize this second point. I was constantly complaining about how difficult it was to use and how incomprehensible the product was.


3. Things that shocked you, or things that you thought might be useful.

a, Power Automate Cloud

- The created flow seems to run on Microsoft's servers, so if you want to access your own file server or similar, you'll need to configure a gateway, etc.

- The triggers for running the created flows are fairly useful. For example, you can set them to run at a specific time.

- You can share the workflows you create with people in the same company.

As expected from a Microsoft product, Office-related actions are available for free.

- Access to some third-party products is subject to a fee. ← That annoyed me.

b, PowerAutomte Desktop

There are no particular restrictions on allowing access to the company's file server.

- Access to some third-party products is paid, but you can control SAP for free for now.

- If you want to make the created flow reasonably feature-rich, the number of steps in the flow will increase, making it difficult to debug.

- Sharing the workflow you've created with colleagues, etc., requires a fee. ←That annoyed me.


Also, completely unrelated, but while Copilot can be used, it's confusing because they have a tendency to lie when you get stuck setting up a flow.

Therefore, it's better not to use it.

 
 
 

Comments


bottom of page