Extending Microsoft Dynamics NAV
This section describes how you can extend the functionality of Microsoft Dynamics NAV 2018 by using the following features.
|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).
NOTE: COM is not supported by the Microsoft Dynamics NAV Web client.
|Extending Microsoft Dynamics NAV Using COM|
|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 Dynamics NAV objects can interact with the .NET Framework objects.||Extending Microsoft Dynamics NAV Using Microsoft .NET Framework Interoperability|
|Control add-ins||With Dynamics NAV you can write control add-ins that add custom functionality to Role Centers and pages on all display targets, using the same extensibility framework.||Extending Any Microsoft Dynamics NAV Client Using Control Add-ins|
|Extensions||The extensions framework provides a way to extend and customize a Dynamics NAV deployment without the need to directly modify source objects.||Developing Extensions in AL|
When 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 Dynamics NAV data in web services.
We'd love to hear your thoughts. Choose the type you'd like to provide:
Our feedback system is built on GitHub Issues. Read more on our blog.