Mastering D365BC approval workflows, part 2

Dynamics 365 Business Central

The article discusses tips for workflows based on a recent multi-approval requirement dealt with.
The team initially set up a large Power Automate approval flow but faced challenges with testing and debugging, ultimately returning to BC Approvals for simplicity and system stability.
The business in question is an inventory re-seller and services company, dividing approvals into Inventory and Services categories based on purchase values.
Reason codes on the header were used as decision points for routing approvals, with 4 paths managed using the REASON CODE field to direct approval logic.
Reason codes are helpful for routing approvals and creating workflows to catch documents with missing reason codes to prevent release.
Different approval routes were established based on the type of purchase, sender, and number of required approvers, with varying approval levels and auto-approval conditions.
Stock approvals followed specific criteria based on purchase value ranges, sender roles, and required approvers from different management levels.
The article suggests that built-in approval workflows may be easier to meet complex approval requirements compared to Power Automate in certain scenarios.

Registered users can view the full text for FREE!