Question

A logistics company has complex freight-cost calculation logic that must be invoked in three ways: synchronously from a model-driven form when a user clicks a button, from a Power Automate cloud flow that runs nightly, and from a plug-in that fires when an order is created. The business requires that all three callers execute the exact same server-side logic and that the logic is transactional and reusable without duplicating code. What is the best design approach?

Accepted Answer

Implement the logic in a Dataverse custom API and call it from the form (via JavaScript/Web API), from the cloud flow (Perform an unbound action), and from the plug-in (via IOrganizationService).

Answer

Write the calculation as a business rule so it can be reused across the form, flow, and plug-in contexts.

Answer

Duplicate the calculation in a JavaScript web resource, a cloud flow expression, and a plug-in class to keep each caller self-contained.

Answer

Build the logic once in a Power Automate child flow and call it from the form, the parent flow, and the plug-in.