From the Microsoft Dynamics NAV Blogs: Testing Your Apps; Calculating COGS; NAVDelta and Customizations; Field Level Security Using Events

A selection of the latest insight from the Dynamics NAV blogs:

• NAV 2016, Testing "Your applications"
• Calculating COGS in NAV
• Apply-NAVDelta to Add and Remove Customizations
• Field Level Security Using Events in Dynamics NAV 2016

NAV 2016, Testing "Your applications"

On his NAV Blog, Roberto Stefanetti writes that Microsoft Dynamics NAV 2016 includes the following features to help you test your application:

• Test codeunits
• Test runner codeunits
• Test pages
• UI handlers
• ASSERTERROR statement

He then offers some best practices for designing your application tests, including separation of test code from real code and testing of both success and failure conditions (positive and negative tests). 

You can read more of Stefanetti's the best practices here.

Calculating COGS in NAV

On his Totovic NAV Blog, Aleksandar Totovic said in general, COGS (cost of goods sold) is an unknown factor that has to be recorded and calculated. Although you can have the precise information about beginning inventory and net purchases, COGS depends on the costing method.

The reason is because it is connected to the fluctuations over time in the unit acquisition costs of he inventory items. COGS will be remain and unknown value until you selected the costing method for each item, Totovic said.

Choosing a costing method does two things: it determines which purchase entries and sales entries will be applied to each other when you post a document. And it ...