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

Announcements

Check out the Community Spotlight Video Series
News and Announcements icon
Community site session details

Community site session details

Session Id :
Dynamics 365 Community / Forums / Supply chain | Supply Chain Management, Commerce / Assigning a Puchase Re...
Supply chain | Supply Chain Management, Commerce
Answered

Assigning a Puchase Requistion workflow to the requester for approval

(1) ShareShare
ReportReport
Posted on by Nibrasse 6

Hi all,
When configuring the PR workflow for a client, the need is to send the approval to the requester on the PR line if the requester is different that the preparer.
example : Person A has permission to request on behalf of person B, person A creates the PR and puts person B as the requester, I would like to setup person B as the first approval in the worflow, however I am not able to find an option to chose the requester as a dynamic field. I tried to use workflow orignator, owner options, I also tried to use the hierarchy option, however when selecting “start from = requester”, the workflow always starts with the requester's superior not the requester himself.

Any help is greately appreciated.
thank you.

Categories:
Dynamics 365 Supply Chain Management
I have the same question (0)
  • Verified answer
    SoumitraforD365 Profile Picture
    SoumitraforD365 263 Super User 2026 Season 2 on at

    Hi @CU20081135-1 

    There is no out-of-the-box way to do this. The "Requester" is not exposed as a dynamic assignee anywhere in the standard PR workflow assignment options, and the hierarchy behaviour you hit is by design.

    Your attempt did not work because;

    • Workflow user only gives you Workflow originator (the person who submitted, i.e. Person A) and Workflow owner (the person who owns the workflow configuration). Neither resolves to the requester.

    • The hierarchy always climbs upward,  Think of the org chart as a ladder. When you pick Hierarchy, you're telling D365 two things: where to start on the ladder, and how far to climb. "Start from = Requester" is only the starting point — it's a marker, not an approver. The system then climbs up from there and hands the approval to whoever is above. It never hands it to the person you started from, because the whole purpose of a hierarchy approval is "escalate this to someone senior". There's no setting for "stop at zero levels" or "include the starting person", so the first person it can ever reach is B's manager.

    I would suggest, look for the potential customization for your requirement.

    Thanks.

  • Nibrasse Profile Picture
    Nibrasse 6 on at

    Thank you @SoumitraforD365 for the confirmation

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

News and Announcements

Check out the Community Spotlight Video Series

Quick Links

Season of Sharing Community Challenge Winners!

Congratulations to our community stars!

Women in Power Builds Momentum

Expanding mentorship, skilling, and AI innovation

Congratulations to the July Top 10 Community Leaders

These are the community rock stars!

Leaderboard > Supply chain | Supply Chain Management, Commerce

#1
André Arnaud de Calavon Profile Picture

André Arnaud de Cal... 90 Super User 2026 Season 2

#2
Laurens vd Tang Profile Picture

Laurens vd Tang 83 Super User 2026 Season 2

#3
Paolo Cecchelli Profile Picture

Paolo Cecchelli 60 Super User 2026 Season 2

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