Breaking news from around the world
Get the Bing + MSN extension
Now Available in Community - MBAS 2019 Presentation Videos
Catch the most popular sessions on demand and learn how Dynamics 365, Power BI, PowerApps, Microsoft Flow, and Excel are powering major transformations around the globe. | View Gallery
2019 release wave 2 Discover the latest updates to Dynamics 365Release overview guides and videos Release Plan | Early Access Availability
Ace your Dynamics 365 deployment with packaged services delivered by expert consultants. | Explore service offerings
Connect with the ISV success team on the latest roadmap, developer tool for AppSource certification, and ISV community engagements | ISV self-service portal
The FastTrack program is designed to help you accelerate your Dynamics 365 deployment with confidence.
FastTrack Program | Finance TechTalks | Customer Engagement TechTalks | Talent TechTalks | Upcoming TechTalks
I've been tasked with altering a GL Workflow Condition step.
What is desired is that during the pipeline processing, the step should check to see if the Workflow.Originator has a supervisor of X (HCMWorker).
So, to put a Condition on a workflow decision step, I'd like to either:
A) Figure out some way to add "Workflow.Workflow.Originator.Supervisor" to the list of fields in the dropdown.
B) Alter the underlying Workflow attached table (a custom General Ledger table) to include the Workflow Originator. Which would get populated during the workflow initiation. Then, in the WorkflowDocument's Query add the relation to the Originator's HCMWorker Supervisor linked table so that the "Originator_Supervisor" would show up as one of the fields in the Condition dropdown.
The problem is—I don't know how to do option A). Which would be preferred as I wouldn't have to modify the underlying table.
With option B) I'll have to try and trap the Submission step in the Workflow sequence and ID the user. Which I think might work, but getting the Supervisor field to show up in the Conditions dropdown may be iffy.
Does anyone have any recommendations/alternatives?
Hello Dave Cline,
I am not a developer and cannot directly help you with that except by providing you with this link to a blog that has a couple of videos posted that show how you can modify the standard workflow engine and add other people /fields/etc for selection and evaluation in workflows.
Please see: organicax.com/.../
Hope this helps.
What we ended up doing is to trap the Submit event on a workflow. Grab the currentWorker(), grab the Supervisor off the HCMWorker table (custom field) and then populate that in the target table.
When we design a workflow process step and add a condition, the Originator.Supervisor now shows up as a optional field on the target table and we then get to compare it (now that it's been set during the Submit event) to a fixed Worker (who is a supervisor).
Business Applications communities