Question
You plan on implementing complex business logic in Microsoft Dataverse tables by using Power Automate flows.
You realize that the functionality required to implement the business logic is not available in a Power Automate flow.
The new business logic must work in multiple Dataverse tables. In addition, the operation must return a value after it finishes and must be able to run from an existing Dataverse action.
You need to recommend the method to implement the missing logic.
What should you recommend?
- A. Bound action
- B. Custom API
- C. Unbound action Correct
- D. Scheduled workflow
Explanation
An unbound (global) action is not tied to a specific table, so the same operation can be called for rows of any Dataverse table. Like any Dataverse action it can define output parameters that return a value when it finishes, and it can be called from workflows, Power Automate flows and other Dataverse actions. A bound action is tied to a single table, so it would not work across multiple tables. Custom API is a way of defining a message that can itself be bound or unbound, and it needs a .NET plug-in for its logic, so it does not by itself meet the multi-table requirement. A scheduled workflow runs on a timer and does not return a value to a caller.
