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

Announcements

No record found.

News and Announcements icon
Community site session details

Community site session details

Session Id :
Dynamics 365 Community / Forums / Supply chain | Supply Chain Management, Commerce / Workflows conditional ...
Supply chain | Supply Chain Management, Commerce
Suggested Answer

Workflows conditional decision for group of Procurement categories + maximum number of requisitions per user

(0) ShareShare
ReportReport
Posted on by Lefteris Papadopoulos 55

Hello,

I want to ask you 2 questions about workflows.

  1. We want to separate the approval flows for purchase requisitions. Specifically, the purchase requisitions will be defined by the Procurement categories.
    We must have a characterization in the Procurement Categories, as a categorization for example direct or indirect expenses.
    This will be a conditional decision. That is, if the user selects an expense category, which has the characterization as 'direct expenses', it will follow the flow based on the Procurement category that will have this option. Otherwise, another flow will follow, based on Cost Center.We want this so we don't have to maintain approval flows every time a new Procurement category is added
  2. How can I set the maximum number of requisitions per user per day?
I have the same question (0)
  • Suggested answer
    Danny Bilodeau Profile Picture
    Danny Bilodeau 4,934 Super User 2026 Season 1 on at

    Hello Lefteris,

    Second requirement is not met with standard functionality.  You would also want to think about the number of lines on a Purch Req because there is no limit on that either..

    For your first requirement, that would mean that the lines would need to be evaluated by a line approval workflow?  There is nothing that allows you to specify a condition on an attribute that is assigned to a Procurement Category; that would necessitate a development.  However, Financial DImensions assigned to a line can be used to evaluate a line a direct it to the appropriate approval route. 

    I personnaly like to use the Business Reason on the PR Header. You can make that fieldmandatory on PR in Purchasing Policies and if you clearly define them, its pretty clear what they should be used for. Then the workflow can evaluate the Business Reason to direct the approval route, but it applies to the whole PR (not the lines).

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

Introducing the 2026 Season 1 community Super Users

Congratulations to our 2026 Super Stars!

Meet the Microsoft Dynamics 365 Contact Center Champions

We are thrilled to have these Champions in our Community!

Congratulations to the March Top 10 Community Leaders

These are the community rock stars!

Leaderboard > Supply chain | Supply Chain Management, Commerce

#1
Mallesh Deshapaga Profile Picture

Mallesh Deshapaga 296

#2
Laurens vd Tang Profile Picture

Laurens vd Tang 234 Super User 2026 Season 1

#3
Syed Haris Shah Profile Picture

Syed Haris Shah 145 Super User 2026 Season 1

Last 30 days Overall leaderboard

Featured topics

Quality order uses default receipt location instead of actual physical receipt location

Product updates

Dynamics 365 release plans