Personalized Community is here!
Quickly customize your community to find the content you seek.
Choose your path Increase your proficiency with the Dynamics 365 applications that you already use and learn more about the apps that interest you. Up your game with a learning path tailored to today's Dynamics 365 masterminds and designed to prepare you for industry-recognized Microsoft certifications.
Visit Microsoft Learn
2021 Release Wave 2Discover the latest updates and new features releasing from October 2021 through March 2022.
2021 release wave 2 plan
The FastTrack program is designed to help you accelerate your Dynamics 365 deployment with confidence.
FastTrack Program | Finance and Operations TechTalks | Customer Engagement TechTalks | Upcoming TechTalks | All TechTalks
Hi Derek, quick question about routing by people.
I get the part about "Requested by" and using that so that it can go to the department manager, if you don't have hierarchy correctly configured in AD. After the direct manager, we also need to insert the CFO if over 25k and then the CEO if over 50K.
So, would I have to add the CFO and CEO to every single department, or would i do all the department processing and then insert the CFO if over 25k and then insert the CEO if over 50?
What I have found is that you have to add them to every single department. If you try to add a step outside of this, it goes to them at the same time as it goes to the manager, because it's meeting the conditions of both steps. So, to prevent this I have to add them after the manager step, but this is obviously a royal pain I have to add the CFO 10x one for each department and same with CEO 10x, one for each dept.
So it kind of looks like this
1. If Request By RKLAPROTH go to JSMITH (if condition not met, go to next step)
2. If Request By RKLAPROTH AND amount >= 25k go to CFO (if condition not met go to next step)
3. If Request BY RKLAPROTH AND amount >= 50k go to CEO (if condition not met go to next step)
1. If Request By JDOE go to BSLIDELL (if condition not met, go to next step)
2. If Request BY JDOE and amount >= 25k go to CFO (if condition not met, go to next step)
3. If Request by JDOE and amount >= 50k go to CEO (if condition not met, go to next step)
There has to be an easier way.. something I'm missing.
Hi, I tried to setup the requisitions to go to different departments and/or approvers. I follow the step to setup the workflow steps for the Purchasing Requisition Approval workflow.
1st Step to have a condition such as 'Where Purchasing Requisition Line.Requested By is IT', then have it go to approver Manager.
2nd Step to have a condition such as 'Where Purchasing Requisition Line.Requested By is AC', then have it go to approver CFO.
The PR with 1st Step condition it successfully route to Manager approval. Unfortunately, when I created the PR with 2nd Step condition the PR show [No Action Needed].
With above setting am I missing something? Thank you.
Remembering that the originator and approver is the Windows AD user accounts used to submit the transactions for approval and assigned as the approver via the Workflow steps. If you have it set so the originator cannot be the approver, and the approver / Windows user account submits a transaction for approval, instead of that transaction going to that approver for approval, it will first look for a alternate approver, and if there isn't one, it will go to the overall Workflow Manager, as long as it isn't the same Windows user account as the originator and approver.
There isn't any way to setup a workflow step to look at who the originator of the transaction/document/batch/etc is, as it is a Windows user account.
There are some workflows, such as a Purchase Requisition, for example, that has a 'Requested By' field, which inserts the GP user ID that was used when the requisition was submitted for approval. You could potentially use something like that to differentiate between who the originator and approver is, but that is about it.
Hi, I have a scenario where User A will need to approve all transactions except for those he entered himself. Any transactions entered by User A will need to bypass him and be approved by User B. On the workflow maintenance, I have unchecked the 'allow originator to be an approver', but will this bypass User A as an approver when he submits transactions? How can I set up conditional steps by originator?
Business Applications communities