Design Patterns is the standard solution, which can be repeated to solve the most common problems. It is generally a part of the full system design. It can be taken as a proven concept in the application.

There are three different types of Design Patterns, which are clearly distinct in Microsoft Dynamics NAV 2016.

The C/AL Editor has been redesigned to provide more coding capabilities. Coding in the new C/AL Editor is just as before except for some new features such as IntelliSense, name completion, change tracking, improved syntax highlighting, and colorization. The following sample code in the C/AL Editor clearly shows its capabilities:

Monitoring is an essential part of software security and surveillance. You can monitor events on Microsoft Dynamics NAV Server to diagnose conditions, and troubleshoot problems that affect operation and performance. Microsoft Dynamics NAV 2016 introduces event channels on events that occur on Microsoft Dynamics NAV Server instances. Event channels provide a way to collect a view event data from a specific provider, which, in this case, is Microsoft Dynamics NAV Server, and for a specific type of event, such as Admin, operational, or debug. The implementation of event channels offers the following enhancements to event logging and viewing.

Microsoft Dynamics NAV uses Event Tracing for Windows (ETW), which is a subsystem of the Windows operating systems. ETW provides a tracing mechanism for events that are raised by an application or service. ETW enables you to use industry-standard tools, such as Windows Performance Monitor, PerfView,...

In Microsoft Dynamics NAV 2016, you can define multiple namespaces on XMLports that import or export data as XML. This improves the ability to create XMLports that are compatible with XML schemas, which are used by the system that consume or provide the Microsoft Dynamics NAV data.

You can define a namespace in the new namespaces property of the XMLport object as shown in the next screenshot.

Each namespace is defined by a prefix and the namespace, which is typically a URI (uniform resource identifier).

You then apply the prefix to specific elements of the XMLport by setting the new NamespacePrefix property:

Select the Export option in the request page for the Sales Order Export XML report, and click on OK:

You will be prompted with a Save/Open dialog box, as seen...

In Microsoft Dynamics NAV 2016, a report has a built-in report layout by default; it can be a Word report layout, a Standard RDLC report layout, or both. You can update custom report layouts with the help of upgrade codeunits. It handles all the changes in the report datasets that affect the report layouts. Upgrade codeunits enable you to programmatically update multiple custom report layouts in the database to changes in report datasets, which cannot be resolved by users from the Microsoft Dynamics NAV client; however, there are certain changes to the dataset that the user is required to modify manually in the report layouts before they can be used. These types of change include, for example, deleted fields or field name conflicts as a result of renaming. Upgrade codeunits enable you to handle these breaking changes to report datasets and layouts without requiring end user interaction.

To design the report upgrade logic in an upgrade...

The new and improved features in Dynamics NAV 2016 enhance the user experience for accountants and bookkeepers. The following are some of the main points I would like to emphasize in this section:

I will try to explain these points with some basic examples.

We use Development Environment to develop Microsoft Dynamics NAV 2016 applications. The Development Environment has a similar look if we take Microsoft Dynamics NAV 2015 as a reference.

The basic object types are the same. We still have seven basic object types: Table, Page, Report, Codeunit, Query, XMLport, and MenuSuite.