This section describes how you can extend the functionality of Microsoft Dynamics NAV 2013 R2 by using the following features.
| Feature | Description | See | ||
|---|---|---|---|---|
Component Object Model (COM) technologies | You can extend the functionality by implementing automation and custom controls. The Microsoft Dynamics NAV Windows client supports automation servers by acting as an automation controller and using OCXs (custom controls).
| |||
Microsoft .NET Framework interoperability | You can extend the RoleTailored clients and Microsoft Dynamics NAV Server with functionality that is available in Microsoft .NET Framework assemblies. You can take advantage of .NET Framework interoperability so that Microsoft Dynamics NAV objects can interact with the .NET Framework objects. | Extending Microsoft Dynamics NAV Using Microsoft .NET Framework Interoperability | ||
Control add-ins | A control add-in is a custom control, or visual element, for displaying and modifying data on pages in the Microsoft Dynamics NAV Windows client. Control add-ins are delivered as Microsoft .NET Framework-based assemblies. Microsoft Dynamics NAV includes the client extensibility API for creating your own control add-ins. |
 Note |
|---|
| When Microsoft Dynamics NAV data is consumed in a browser or by a Microsoft .NET Framework assembly, users cannot be authenticated if their user name or password contains Unicode characters. This is a limitation in the basic authentication mechanism that is defined in the HTTP/1.1 specification. The same limitation applies to exposing Microsoft Dynamics NAV data in web services. |