New April Hotfix and more changes for VAT
Check out the latest updates to Microsoft Dynamics GP 2016 and 2018.
Dynamics 365 2019 release wave 2 plan Discover the latest updates to Dynamics 365.Release Plan | Weekly Deployment Notes
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 and Operations TechTalks | Customer Engagement TechTalks | Talent TechTalks
A client reported a problem with their PO Approval Workflow process failing whenever a PO was submitted for approval. As soon as the Submit button was pressed, the document was rejected, but did not show a user:
Looking in Workflow History showed the assigned user on both the Submit and Reject lines was showing as SYSTEM:
This was not a new workflow process, it is one which has been used for over a year, so I knew there was not an inherent problem.
Due to another issue I’ve been working on recently, I had a suspicion that this was AD related. To confirm this, I opened Workflow Maintenance (Admistration &175; Setup &175; Company &175; Workflow Maintenance) and tried to add a manager:
The return of the search on the name failed, which was what I had expected.
The problem was that Workflow was not able to sucessfully perform a lookup on Active Directory to determine the user. I relayed this information back to the client and they were able to determine that there was a problem with one of the domain controllers. Once resolved, the workflow was again working correctly.
Read original post Purchase Order Approval Workflow Automatically Rejected at azurecurve|Ramblings of a Dynamics GP Consultant
Business Applications communities