Skip to main content

Notifications

Announcements

No record found.

Community site session details

Community site session details

Session Id :
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 41

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?
  • Suggested answer
    Danny Bilodeau Profile Picture
    4,338 Moderator on at
    RE: Workflows conditional decision for group of Procurement categories + maximum number of requisitions per user

    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

🌸 Community Spring Festival 2025 Challenge 🌸

WIN Power Platform Community Conference 2025 tickets!

Jonas ”Jones” Melgaard – Community Spotlight

We are honored to recognize Jonas "Jones" Melgaard as our April 2025…

Kudos to the March Top 10 Community Stars!

Thanks for all your good work in the Community!

Leaderboard

#1
André Arnaud de Calavon Profile Picture

André Arnaud de Cal... 294,145 Super User 2025 Season 1

#2
Martin Dráb Profile Picture

Martin Dráb 232,917 Most Valuable Professional

#3
nmaenpaa Profile Picture

nmaenpaa 101,158 Moderator

Leaderboard

Featured topics

Product updates

Dynamics 365 release plans