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 availabl

Question

Options

• ABound action
• BCustom API
• CUnbound action
• DScheduled workflow

• A
  5% (1)
• B
  5% (1)
• C
  77% (17)
• D
  14% (3)

Explanation

An Unbound action in Dataverse is the correct choice because it satisfies all the stated requirements: it is not tied to a specific table (so it can work across multiple Dataverse tables), it can return a value upon completion, and it can be invoked from an existing Dataverse action or workflow. A Bound action (A) is tied to a specific entity/table, so it cannot serve multiple tables. A Custom API (B) is a modern alternative but the scenario's requirement to 'run from an existing Dataverse action' aligns more directly with the classic Unbound action pattern in Dataverse workflows. A Scheduled workflow (D) runs on a timer and does not return values or get called from other actions.

No community discussion yet for this question.