Calling a flow from a User Defined Function

(1) Share

Report

Posted on by CU07102133-1

I have an application that calls a number of flows, feeds them an input variable (data type number), and they each return a JSON string. I then convert those strings into collections.

The input variable can be updated on numerous pages within the app, and I don't want to replicate the extensive code to call all the flows in multiple places.

Prior to User Defined Functions I had a slider default property linked to the input variable, with the code in the onchange property. Whenever the input changed, the flows all ran and the collections were updated.

When User Defined Functions came along, I was excited until I realised that they operate from within App Formulas, and you can't call behaviours (Flows) from within App Formulas.

Then Microsoft changed something in the back end, and state changes to sliders and timers are no longer detected in published apps, despite continuing to be in the editor. The next time I published an update of my app, the timers all stopped working. I have researched widely and tried all sorts of things, but at the end of the day, no joy.

Is there some way to define a function with full functionality (i.e. run behaviours, accept all data types as inputs and outputs) without having to jump through hoops or manipulate other things?

Other languages have been doing this for decades.

Any help is appreciated.

Thanks,

Dave.

I have the same question (0)

All responses (3)

Answers (0)

Sort by

Suggested answer

sannavajjala87 522 Super User 2026 Season 1 on at

Like
a
(0)

Report
Copy link

Link copied!
Hi Dave,

What you’re running into is a current limitation of Power Apps rather than something you’re missing. User Defined Functions are strictly formula-only, so they can’t execute behaviors like calling flows, which is why they don’t replace your earlier pattern. There isn’t a true “full-function” construct today that combines both behaviors and return values like in traditional programming languages.
The recommended pattern in most cases is to centralize your flow calls in one place and trigger them explicitly, typically by:

Using a single reusable wrapper pattern (e.g., one button, hidden control, or component) that runs all flows

Calling that logic from screens via Select() or by toggling a variable

Storing results in global variables/collections that other screens can consume

The slider/timer trick used to work as a pseudo-trigger, but as you noticed, those indirect state-change triggers are no longer reliable after recent platform changes.
So unfortunately there’s no clean “function with side effects” yet, the best approach is still to centralize behavior logic and trigger it explicitly, rather than trying to rely on reactive formulas.

Was this reply helpful? Yes No
Suggested answer

11manish 3,347 on at

Like
a
(0)

Report
Copy link

Link copied!

For your scenario, the cleanest and most maintainable approach is to replace the multiple flow calls with a single "master" Power Automate flow that accepts the

input number, invokes the necessary child flows (or performs the work itself), and returns a single JSON payload. Your app then makes one Flow.Run() call and

updates the required collections in one place. This avoids duplicating code across screens, removes the dependency on timer/slider workarounds, and aligns with

the current capabilities of Power Apps until Microsoft introduces support for reusable behavior functions.

Was this reply helpful? Yes No
Suggested answer

Valantis 6,778 on at

Like
a
(1)

Report
Copy link

Link copied!

Hi @CU07102133-1,

UDFs are formula-only by design, so calling flows from them isn't supported and there's no workaround that changes that.

11manish's single master flow approach is the cleanest path for the flow side. For the trigger side, the most reliable replacement for the slider/timer pattern is a Power Apps Component.

Put all your flow-calling logic in the component's OnReset or a custom event, then call Reset(YourComponent) or raise the event from any screen whenever the input changes. Components behave consistently in published apps unlike the slider/timer state-change detection that broke.

This gives you one place for the logic, triggered explicitly from anywhere, which is the closest Power Apps gets to a reusable behavior function today.

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