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
2020 release wave 1Discover the latest updates and new features to Dynamics 365 planned through September 2020
Release overview guides and videos Release Plan | Preview 2020 Release Wave 1 TimelineWatch the 2020 Release Wave 1 virtual launch event
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 | Upcoming TechTalks
Has anyone worked out ways in NAV to a) direct approval requests to different users or groups of users based on line-level department information; b) allow users to approve amounts on the PO that relate to them (e.g., for their department) without trying to approve the entire PO? Because the PO total amount drives the Approval User chain, a first-level Approver would probably never see POs for approval, since the total PO amount would almost always be greater than their approval limit.
Approvals based on Lines are often requested, but I've never saw a solution.
When you build a solution and publish on AppSource, some people might would buy :-)
PS: Workaround for your problem could be, to create several POs for each line item that has to be approved individually.
Thank you for your reply. It looks like we might be forced to come up with something to accommodate our client's preferred workflow; when we do I will be sure to let you know!
We had to create a very elaborate customization to satisfy that approval requirement. As Hannes mentions above, if you are going to write this customization, you should publish and sell. If you need a resource to to do the leg work, message me and I will pass the contact information for my previous consulting firm.
Thank you! At this point I would be very happy to talk with anyone, who has had experience in dealing with what must be a common scenario. I don't think most companies would prefer to write multiple purchase orders to the same vendor for the same item, segregated by, say, department. Certainly the vendor would not prefer it!
As much as I would like to publish and sell, I have to admit that it was this blog post chrisdsilvablog.wordpress.com/.../ that showed me the basic components that had to be in place. I had to elaborate some to adapt it to our client's specific requirements, but without this guide I would never have figured it out. It ends up being a lot of code in one custom code unit, and small changes to base NAV workflow elements here and there.
Business Applications communities