From the Microsoft Dynamics NAV Blogs: Approval workflows; DotNet types; Named subscription users; Extensions V2 simplified

From this week's Microsoft Dynamics NAV blogs:

• Creating Dynamics NAV approval workflows: How to allow for a single approval from a group of approvers
• NAV: DotNet types and extensions V2
• Counting named subscription users in Dynamics NAV
• NAV extensions will make NAV upgrades much easier

Creating Dynamics NAV approval workflows: How to allow for a single approval from a group of approvers

On the Boyer & Associates Blog, Bradley Roberts wrote that in most documentation on workflow approval scenarios, Microsoft provides instructions on a single approver, multiple required approvers, or a hierarchical approval structure.

But to date, none of the customers he's worked with on Microsoft Dynamics NAV workflow tasks have asked for these types of approval structures. Most often the event could be approved by any one of several supervising users, he wrote.

Then, once any of these users approves it, the approval process is finished and there should be no other pending approval entries outstanding. This can be referred to as a single approval from a group of approvers, according to Boyer:

Fortunately, this scenario is easily created by making some minor tweaks to the workflow templates that are available out-of-the-box in Dynamics NAV.

You can read how here.

NAV: DotNet types and extensions V2

On the Stefano Demiliani Technical Blog, Demiliani wrote that he's seeing many Dynamics NAV partners starting "tests," so they can move some of their NAV customizations to the new Extensions V2 architecture (with AL) - a great sign for the entire NAV ecosystem.

However, he wrote that there are always ...