Don’t Repeat Yourself — Compose It Once, Use It Everywhere.

Views (9)

developerAJ

4,165

Like(0)

Report

💡 What Is the Compose Action?

The Compose action lets you evaluate and hold:

An expression
A static value
Or any dynamic content

It does not store state like a variable. It’s a read-only snapshot — no update, no memory allocation, no overhead.

✅ Think of Compose as: “📌 Store it once. 🧪 Reuse it safely. 🧱 Never mutate it.”

It’s the best way to manage logic in flows where performance, safety, and reusability matter.

Please refer to the full article using the 🎯 Don’t Repeat Yourself — Compose It Once, Use It Everywhere | LinkedIn

Comments

eliotcole 4,329 Moderator
Posted at

Don’t Repeat Yourself — Compose It Once, Use It Everywhere.

A more powerful (and validated) version of this is using the 'Parse JSON' action to create at least one set of 'constants' in your workflow.

Using 'Parse JSON' Actions To Affect Constants In Your Flow

If you create two of these near the start of your flow, then you can have a large swathe of 'Constants' readily available, validated, AND with a nice interface in the GUI.

That's because a 'Parse JSON' action allows you to add 'title' key/value pairs to the schema of the data, which can make the information more acceptable to use, especially if others need to work with your flow/workflow.

Plus, the validation properties can assist you in ensuring that information is correctly made.

Finally, because this is all done within a single 'Parse JSON' action it simplifies the view of your flow AND provides you with potentially HUNDREDS of constant values!

Here's how I usually construct them, but you can see many of my answers to community questions in the Power Automate forum on this ... at least from the last couple of years:

StaticDataObjCNST

I will always create a 'Parse JSON' action named "StaticDataObjCNST" near the very start.

This will mostly contain physically typed data, or expressions which 100% cannot fail (or the action is within a Scope that has failure branching afterwards), but all of which will evaluate to very, very, 'static' information.

ConstantsObjCNST

I will also quite often create a 'Parse JSON' action named "ConstantsObjCNST" which will hold a lot of similarly non-changing data, but this is going to be based upon initial variable settings and some/a lot of the data in the "StaticDataObjCNST" action previously mentioned. This enables within the scope of two actions to achieve a LOT.

Like (0)

Report

Community site session details

Don’t Repeat Yourself — Compose It Once, Use It Everywhere.

💡 What Is the Compose Action?

Comments

Using 'Parse JSON' Actions To Affect Constants In Your Flow

StaticDataObjCNST

ConstantsObjCNST

Responsible AI policies

Tom Macfarlan – Community Spotlight

Congratulations to the September Top 10 Community Leaders!