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 wonder if someone could assist me.I understand that a PO workflow can only be activated when change management is on.
I need to customize the current PO workflow to result in a situation where the Workflow submit button only pops up if a condition is met. If the condition is not present then the PO must be approved automatically without submitting anything, thus if the PO has a line that does meet the condition then the workflow button should pop up and have the option to submit that workflow.
Who could I speak to with regards to coding this in on the AOT environment.
Hi Rui Gomes da Silva,
1 quick question --- even if you write code to achieve this; how system will understand that PO doesn't meet the condition what you set in the workflow unless you submit that PO in the workflow to verify and pass through the validation ?
Sometimes, user requirement becomes weird. However you can try to convince them again that the functionality what they are expecting, can be simply achieved through the workflow (no customization is required). Only thing is; you need to submit the PO in workflow.
Once submitted, it will fetch whether the condition is meet or not. If it doesn't meet, then it will be auto approved.
You can set both such conditions in workflow configuration.
Best regards,Sourav Dam
Have you checked whether you could avoid the modification by making use of business events and Flow?
Thanks for the reply once again!:)
I have not actually considered this I will have a look.
Thank you much appreciated.
Thanks for the input!
I actually have it set up where it gets auto approved if the condition is not met etc..
I will keep the suggestion into consideration.
Again thanks for your time
Hi Rui Gomes,
If you notice PurchTable Table contains a field "ChangeRequestRequired" and this derives value from change management (active on parameters and / or override on vendor master. What you can do is, on record creation (Insert, else it can create issue, let standard work as is once workflow is active / disabled) in purchase table/ line (depending upon which condition you want to check), override this property in the purchtable for a specific purchase order number and then it will dictate if the workflow button is visible or not.
Please help verify answer(s) if they guide you in right direction so other community members can also benefit from your question with verified answer.
Chris Garty did an interesting presentation on this at the MBA Summit in Atlanta.
Just check out the recordings to see what is possible with business events and Flow.
Maybe you can avoid a customization with those tools.
Hi Ludwig Reinhard,
Could you kindly share the link of this presentation, if any. It will be good to watch this to learn.
Will be waiting for your response on this.
Thank you! I will have a look at this. I appreciate the input
The standard pattern is to let the user click the button, then throw an error if a condition is not satisfied. It is less visual but much faster and user friendly then to let the user submit and gamble what comes next.
In this particular case PurchWorkflowApproval calls purchTable.checkFullyDistributedAndQualified() which is the best place to hack in.
I am working with Rui on this requirement. The problem we have is that the user does NOT want to click the "Submit to work workflow" button if the PurchLine is for an Item, but if it is a Service then normal Workflow should proceed. I added an Event on PurchLine_onInserted and tried a number of scenarios.
2. The second option I tried was to set all the fields manually including to ChangeRequestRequired to false and to remove the workflow from the PO . This looked as though it worked. I could confirm the PO but when I did the receipt process I got the following error.
Please any suggestions will be of great assistance.
For #2 above, is the error also for the PO's that you submit manually? This looks more like item setup issue and not workflow related. can you review item please.
Hi Satish. Thanks for prompt response. I first validated the item by completing the PO with the item and Vendor to ensure that the item is valid and that everything works fine and then added my code and used the same item and vendor and that is when I got the error. Rechecked by removing code and it works.
Business Applications communities