web
You’re offline. This is a read only version of the page.
close
Skip to main content

Announcements

News and Announcements icon
Community site session details

Community site session details

Session Id :
Small and medium business | Business Central, N...
Suggested Answer

B.C. functionality: Workflow Groups (Sequence)

(2) ShareShare
ReportReport
Posted on by
Dear all,
 
I would have a question regarding the following post:

Setting Up Workflow User Groups in Microsoft Dynamics 365 Business Central

In the post, Mr. Wang states that:

"Flat List of Approvers: If you want all users in the group to have equal authority to approve requests, assign them the same sequence number. In this case, only one approval is needed from any member of the group to move the workflow forward."
 
The same topic is described on the Microsoft Learn website (parallel approval):

Using approval workflows - Business Central | Microsoft Learn
 
The description on the Microsoft Learn website states that the workflow isn´t concluded until all requests have been approved (so it is different to the statement of Mr. Wang).

My question:
I tested it myself in the system and the statement on Microsoft Learn applies.
I would like to know if Mr. Wang had a different setup in mind, because many clients ask exactly the requirement, which he described: that the approval is sent to all users with the same sequence number and the request is approved when any of the users approves it. Is there a way to set this up?

I haven´t found an option to write to Mr. Wang directly therefore I first wrote to a Community Manager. As I didn´t get a reply I am asking here.
 
Thank you in advance.
I have the same question (0)
  • Assisted by AI
    Saif Ali Sabri Profile Picture
    2,762 Moderator on at
    You have raised a very important point that often causes confusion in Business Central workflow approvals. Let me clarify the difference between the two interpretations and provide a structured solution reply:

    🔹 Flat List of Approvers (Mr. Wang’s statement)

    • When multiple users are assigned the same sequence number, the system sends the approval request to all of them simultaneously.
    • However, Business Central does not natively support “any one approver is enough” logic. Instead, it treats this as a parallel approval requirement, meaning all users must approve before the workflow moves forward.
    • This aligns with what you observed in your own testing and what is documented on Microsoft Learn.

    🔹 Why the difference?

    • Mr. Wang’s description seems to reflect a desired customization or a conceptual simplification, not the standard product behavior.
    • Out-of-the-box, Business Central requires all approvers in the same sequence group to approve. There is no built-in option to conclude the workflow after just one approval.

    🔹 Possible Solutions

    1. Workflow customization
      • Using Power Automate or AL code extensions, you can design a custom approval logic where the workflow completes once any one approver in the group approves.
      • This is the recommended approach if clients specifically require “first-come approval” logic.
    2. Delegation setup
      • Another workaround is to assign a single approver in the workflow group and use delegation rules to allow others to act on their behalf.
      • This way, only one approval is technically required, but multiple users can perform it.
    3. Third-party add-ons
      • Some ISV solutions available on AppSource extend workflow functionality and may already support “any approver” scenarios.

    Conclusion

    • The standard Business Central workflow requires all approvers in the same sequence to approve.
    • Mr. Wang’s statement likely referred to a customized setup or a conceptual simplification.
    • To achieve the requirement where only one approval is sufficient, you will need either Power Automate customization, AL extension development, or a third-party solution.
  • Suggested answer
    Mansi Soni Profile Picture
    10,192 Super User 2026 Season 1 on at
    Hello,
     
    Your testing aligns with the current standard behavior of Business Central and Microsoft Learn. When multiple approvers are assigned the same sequence number, the workflow creates parallel approvals, meaning all approvers at that level must approve before the workflow proceeds. There is no standard configuration in Business Central that supports an any one approver can approve scenario for Workflow User Groups. If this business requirement exists, it would require a customization or an alternative approval design using Power Automate or custom AL development.

    Hope this answer helps you!

    Regards,
    Mansi Soni
  • CU23041502-0 Profile Picture
    on at
    Thank you both for the reply.
     
    @: can you please specify further the following possible solution:
    Delegation setup
    • Another workaround is to assign a single approver in the workflow group and use delegation rules to allow others to act on their behalf.
    • This way, only one approval is technically required, but multiple users can perform it.
     
    Can you please let me know how that would be set up and provide an example?

    Thank you in advance.

Under review

Thank you for your reply! To ensure a great experience for everyone, your content is awaiting approval by our Community Managers. Please check back later.

Helpful resources

Quick Links

Season of Sharing Community Challenge Launch!

Jump in, show your community spirit, and win prizes!

Women in Power Builds Momentum

Expanding mentorship, skilling, and AI innovation

Congratulations to the May Top 10 Community Leaders

These are the community rock stars!

Leaderboard > Small and medium business | Business Central, NAV, RMS

#1
OussamaSabbouh Profile Picture

OussamaSabbouh 1,474 Super User 2026 Season 1

#2
YUN ZHU Profile Picture

YUN ZHU 864 Super User 2026 Season 1

#3
Grigorios Mavrogeorgis Profile Picture

Grigorios Mavrogeorgis 851 Super User 2026 Season 1

Last 30 days Overall leaderboard

Featured topics

Microsoft Training Manuals

Product updates

Dynamics 365 release plans