Unanswered

Automatically assign a BPF (Business Process Flow) to an entity based on a field condition

(0) Share

Report

Posted on by Jose Gregorio Diaz

Dear Community experts,

Do you know if there is a way that I can automatically assign a particular BPF (Business Process Flow) to an entity based on a field condition?

Thank you,

Jose G Diaz

Categories:

Building Power Apps

I have the same question (0)

All responses (4)

Answers (0)

Andras Fordos 8 on at

Like (0)

Report

Hey

Answer depends on more details of your situation: do you want to just branch off within an already running BPF? Or you want to start a specific BPF on a record based on field values? For the former, I see you got good starting points in your other forum post. For the latter you do have option with both frontend (JS) and backend (C# or workflow) depending on your needs.

But first, the important part is to understand how BPF works:
For every BPF, when created, a "helper" entity (table) is created in Dataverse, to store instance records of that particular BPF. What this means is, that every single time a record (for example a case) starts within a BPF, a new record is created in this helper table by the system to track the advance of that record within the BPF. Additionally, the particular record (case in this example) will be pointed also towards the currently active associated BPF through a "processid" field.

So, in short, by your means (frontend, backend), you would need to set the processid on your entity record (for example case) to the BPF and create a new record in the BPF "helper" table too, filling out the important fields (active stage, traversed path, etc etc). Happy coding! https://learn.microsoft.com/en-us/power-automate/best-practices-entity-attributes#using-the-active-stage-to-run-logic

Cheers,
András

Was this reply helpful? Yes No
Jose Gregorio Diaz 67 on at

Like (0)

Report

Thank you for your answer Andras, the idea is to start a specific BPF on a record based on a field value. Any advice?

Thank you,

Jose G Diaz

Was this reply helpful? Yes No
Ezra Tosatti 16 on at

Like (0)

Report

Hello,
I've managed similar need in the past, with this approach: I've created a classic workflow, triggered on attribute change, performed some verifications (for example checking the status of the entity) and added unbounded action "SetProcess", selecting the BPF as "NewProcess" and the entity as "Target".

Best regards

Was this reply helpful? Yes No
TonySileo 13 on at

Like (1)

Report

SetProcess appears to be a deprecated action. Does anyone know what the approved/new way to do this is?

Was this reply helpful? Yes No