Diff Mode in Flow Studio

We are happy to introduce a new feature update in Flow Studio app. “Diff Mode”

• Navigate to Diff on the left hand side.

• Use the top dropdowns to select your environment, flow and (optionally) version. Hit “Load”

• You can use Monaco (VS Code) editor to copy Flow definition differences to the right hand side.

• The left hand side is always read-only.

• Clicking “Save” will save the right hand side flow definition.

This is a feature previously hidden in “Snapshots” and “Diff” flow. But that experience only lets you compare between the flow and its previous versions. The new experience also let you compare a flow between two different environments. So if you have Dev, Test and Prod environments with unmanaged solutions - you may need this to keep your flows in sync.

Do test this out in https://dev.flowstudio.app v1.3.58 for now and give us your feedback. We’ll aim to push this to production build within 1 week.

Thank you for supporting Flow Studio App

Flow Studio Price Update 2025 & Introducing Flow Studio for Teams

Since July 2019, Flow Studio has remained at its previous pricing of $20 per month per person and $200 per year. Over the years, we’ve introduced numerous enhancements, including:

• Flow Snapshots – Easily track and restore previous versions of your flows.

• Export to Zip – Package and share flows efficiently.

• Export runs to Excel

• API Enhancements – Faster, more reliable flow management.

At the same time, Azure costs have steadily increased, impacting our infrastructure expenses. To continue delivering a high-quality experience, we are updating our pricing.

Flow Studio Pro

Plan	Current Price	New Price	Effective Date
Monthly	$20 per month per person	$25 per month per person	End of March 2025
Yearly	$200 per year	$250 per year	End of April 2025

🔹 Existing customers will continue at their current pricing—this update applies only to new sign-ups.

Introducing Flow Studio for Teams

We’re excited to introduce Flow Studio for Teams, designed for business, projects and teams that need better visibility and management of their flows. With this new offering, teams can:

✅ Set up automatic monitoring of critical flows
✅ Receive alerts when flows fail or behave unexpectedly
✅ Store flow run details beyond 30 days
✅ We host, or BYO Storage

Flow Studio for Teams Pricing

Plan	Price	Effective Date
Monthly	$100 per month inc 3 seats	Now
Yearly	$1000 per year inc 3 seats	Now

We appreciate your support and look forward to continuing to improve Flow Studio. If you have any questions or feedback, feel free to reach out!

Mathematically Elegant way to Flatten an Array of Arrays in Power Automate

When working with data in Power Automate, you may encounter nested arrays (arrays within arrays)—especially when dealing with JSON responses, SharePoint lists, or API results. However, many Power Automate actions require a flat array to work properly.

In this post, I'll show you a mathematically elegant way to flatten an array of arrays into a single-level array using Power Automate expressions.

Understanding the Problem

Let's say you have the following array:

[
    ["Ford", "Toyota"],
    ["BMW", "Audi"],
    ["Honda", "Nissan"]
]

Instead of dealing with nested arrays, you want to flatten it into a single array:

["Ford", "Toyota", "BMW", "Audi", "Honda", "Nissan"]

The slow way - Array variable

The slow way is to use an array variable, then while looping through the top level array, append or union the results into the array variable.

Variables are so slow I don’t even want to make them and add a picture.

The faster way - String manipulation

Convert the array into JSON string, remove the extra array [ and ] characters, re-construct the array in string, and convert back to JSON.

This is a method I was using, it’s much quicker, but has a risk of needing to be careful when removing bracket characters. If you have nested JSON objects this needs more care.

The new fastest way - div and mod flattening

To understand this - you need two numbers: m and n
m = number of elements in the top array
n = number of elements in the child array

Create a range of the total result size of the array (m) * (n)

Use select - loop through this range of numbers, then for each, select the nested result using:
outputs(‘nested-items’)?[ div( item(), outputs(‘n’)) ]?[mod( item(), outputs(‘n’)) ]

do you see how elegant this is 🤔

View fullsize

From:
range(
  0, 
  mul( 
    length(outputs('Nested_Array')),
    outputs('Compose_-_child_size')
  )
)

Map:
body('Nested_Array')
?[div(item(),outputs('Compose_-_child_size'))]
?[mod(item(),outputs('Compose_-_child_size'))]

what’s going on here?
let’s picture for each of the 6 elements above.

0 = array[0][0] div(0, 2) = 0, mod(0,2) = 0
1 = array[0][1] div(1, 2) = 0, mod(1,2) = 1
2 = array[1][0]
3 = array[1][1]
4 = array[2][0] div(4, 2) = 2, mod(4,2) = 0
5 = array[2][1]

so in one select, we can flatten an (m * n) -sized array.

What if my child array is irregularly sized?
That’s OK. By using ?[n] Select will return null for that element, so we can follow the select with a filter-array to remove the nulls.

View fullsize

View fullsize

Bonus

This works wonderfully with Pieter’s Method, which returns array of Body jsons.

Bonus

This works well for cross-join of two arrays, and then flattening them into one.
(These bonus ideas are massive additional blog posts let me know if want to read them…)

Upgrading SharePointSSO Copilot SPFx to Botframework-WebChat 4.18

This is a quick post about how to make a few packages work together.

Firstly, we have this SharePoint SSO Copilot Studio Sample.
https://github.com/microsoft/CopilotStudioSamples/tree/master/SharePointSSOComponent

It uses SPFx 1.18, which uses typescript 4.7
It also uses botframework-webchat 4.15.9

There are a few really nice upgrades in Botframework-webchat since 4.15. But they also picked up a dependency on typescript 5.0.

Lots of people have reported issues with this…
https://github.com/microsoft/BotFramework-WebChat/issues/5345
https://github.com/microsoft/CopilotStudioSamples/issues/260

Now if only we can easily upgrade SPFx to typescript 5.0…
Which is exactly what MVP Andrew Connell has written here:
https://www.voitanos.io/blog/sharepoint-framework-typescript-v5/

So the final steps are:

1. Commit everything first

2. npm uninstall @microsoft/rush-stack-compiler-4.7 -DE

3. npm install [email protected] -DE
   npm install [email protected] -DE

4. npm install @microsoft/[email protected] -DE

5. Update ./tsconfig.json (see AC’s blog!)

6. npm install [email protected]

7. I had the build failed because a task (lint) wrote output to stderr.
   So I had to switch off a few rules and suppress the error warning.
   
   

Surprisingly, everything works and deploys fine in SharePoint online.

A debug tip for complex conditions in Power Automate #FlowNinjaHack 126

This is #FlowNinjaHack 126

Sometimes, we have complex Condition blocks in Power Automate.

And when we run the flow, it just shows “false”, which is a bit hard to debug.

One way I’ve started doing, is to write a Compose debug statement that shows the output of each component of my condition.
I show the Code View here as well so you get the idea.

To convert from the Condition block to these expressions can be a bit tricky, since you can’t use Code View easily for Condition. So here’s a second hack.

Paste this to a text editor, something that understands JSON. You’ll get this part.

        "type": "If",
        "expression": {
            "and": [
                {
                    "not": {
                        "equals": [
                            "@outputs('Get_item_-_Bulletins_list')?['body/Status/Value']",
                            "Draft"
                        ]
                    }
                },
                {
                    "not": {
                        "contains": [
                            "@body('Select_page_filename')",
                            "@variables('varTitle')"
                        ]
                    }
                },
                {
                    "contains": [
                        "@body('Select_page_filename')",
                        "@outputs('Compose_-_Old_Title')"
                    ]
                }
            ]
        }

Now this is still not the right format, but you can then go from this to:

not(contains(body('Select_page_filename'), outputs('Compose_-_Old_Title'))

With a lot less pain.
This is the debug message you’ll see when you run now.