The NAV 2017 Client Add-in API (also known as Client Extensibility) provides the capability to extend the RTC for Windows, Web, or Tablet through the integration of external non-NAV controls. The Client Add-in API uses .NET interfaces as the binding mechanism between a control add-in and the NAV framework. Different interfaces and base classes are available to use, or a custom interface can be created. Controls can be designed to raise events that call on the OnControlAddin trigger on the page field control that hosts the add-in. They can also add events and methods that can be called from within C/AL.

Contrary to the limitations on other integration options, Client Add-ins can be graphical and appear on the RTC display as part of or mingled with native NAV controls. The following are a few simple examples of how Client Add-ins might be used to extend RTC UI behavior:

• A NAV text control that looks normal but offers a special behavior, but when the user double-clicks on it, the field's contents will display in a popup screen accompanied by other related information or even a graphical display.
• A dashboard made up of several dials or gauges showing the percentage of chosen resources relative to target limits or goals. The dials are defined to support click and drill into the underlying NAV detail data.
• An integrated sales call mapping function displays customer locations on a map and creates a sequenced call list with pertinent sales data from the NAV database.
• Interactive visualization of a workflow or flow of goods in a process, showing the number of entries at each stage, and supporting filtering to display selected sets of entries.
• Entry and storage of a written document signature on a touch screen.