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
Can you share details of what you mean by parent and child categories?
A screenshot that illustrates you issue and your workflow configuration would help.
Please see below; I mean the Procurement Category hierarchy.
I can select the parent and the child category without a problem.
What D365FO system version do you operate?
Is this possibly an older one?
Do you know if modifications have been made to the categories?
It's version 10. No modifications.
Yes, I can select either one of them too.
But the issue is, If I select a parent in the workflow condition, and when I submit a PO for a child that belongs to that parent - the workflow doesn't flow through to the user group/ workflow doesn't work.
But if I select a child in the workflow condition and I submit a PO for the same child - it works.
So we have to create a workflow conditions and approvals for each one of the child out of 100s like this.
and each time a new child adds, maintenance becomes too much.
Thanks for the clarification.
I see and understand your issue now.
If you want to run the workflow based on the procurement category then you have this limitation that probably a lot of maintenance might be required.
Yet, I think that there are alternatives.
As an example, if you create service items with the same name as your procurement categories and/or if you link those service items to your categories then you can apply a condition on the item and make use of the 'begins with' or 'contains' filter criteria.
Wouldn't that be an acceptable workaround that does not require a modification?
Thanks for the confirmation and quick responses Ludwig,
I will test and discuss with the team to see if this works.
Will keep you posted.!
As alternative, you can create a customization where you do some setup in a new table. Then create a new workflow participant provider based on this table which can be linked to your workflow. You can then add logic in the participant provider to setup either parents, child or both.
Hi Ludwig and Andre,
Thanks for your input.
We finally leveraged the Reason code on PO header to get around with it.
That's another alternative option :-)
If there is nothing else left open / not answered then let's verify the answers to get this thread complete.
Many thanks and best regards,
Business Applications communities