Microsoft Dynamics NAV - C/SIDE Solution Development -

Microsoft Dynamics NAV – C/SIDE Solution Development

Locus IT ServicesMicrosoft Dynamics NAV – C/SIDE Solution Development

Lesson 1: Prerequisite Knowledge

Prerequisite Knowledge

Before you design and develop the solution for managing master data, you must review Microsoft Dynamics NAV 2013 standard functionality. In each module, this “Prerequisite Knowledge” lesson presents Microsoft Dynamics NAV 2013 standards and principles that you can apply while customizing the solution for CRONUS International Ltd.


Triggers are methods that execute when a system event occurs or when they are invoked by code. Following are two types of active triggers (triggers that contain executable code):

  • Event Triggers have names that begin with “On…” and execute when specific events occur. For example, the OnInsert trigger executes when a user inserts a record in a table.
  • Function Triggers are custom triggers that developers define. There are many function triggers that are defined as a part of the base application. You can add many more as part of your customization. These triggers execute when they are called by other C/AL code.

The Documentation Trigger is the third type of trigger. There is only one Documentation trigger per object, and anything that is written in it is not processed by the application, even if it contains C/AL code. It typically contains free-form documentation.  This trigger lets you document the changes that you have made to objects. This chapter demonstrates how to use these triggers in various scenarios.

Multi-Language Support

Microsoft Dynamics NAV 2013 is a multilanguage application. This means that a localized version of Microsoft Dynamics NAV 2013 can present itself in different languages. In other words, two or more RoleTailored clients that are connected to the same database can present their user interface in two or more languages at the same time.  Users can change the language at any time, and the change is applied immediately.

To enable multilanguage functionality for your custom solutions, use the following guidelines:

  • Always define the Name property of an object, a control, or a table field in English (United States), or ENU. You must make sure that this is never visible to the user, by specifying the Caption property.
  • Always provide language-specific names in the CaptionML property of the objects, controls, or table fields.
Locus IT Project Management Office
What’s it?