Dynamics NAV Architecture Comparison
Object | Classic client | RoleTailored client |
Codeunit | Same as previous versions of Microsoft Dynamics NAV. | Designed and executed in the same way as the Classic client. New functions have been added to stream files and data between the RoleTailored client and Microsoft Dynamics NAV Server. Code runs on Microsoft Dynamics NAV Server. Any applications that need to allow clients access to COM objects need to be redesigned. |
Dataport | Same as previous versions of Microsoft Dynamics NAV. | Not supported Directly. |
Form | Same as previous versions of Microsoft Dynamics NAV. All code that is written on forms continues to run. Code and triggers run on the client. | Not supported. Replaced by pages. C/AL code references to forms are translated to the same method call on a page object with the same ID. |
MenuSuite | Same as previous versions of Microsoft Dynamics NAV. | Navigation based on page rather than MenuSuite. To navigate to another page, you can add actions to a page that opens the new page.You can also allow access to the traditional MenuSuite through the Departments section. |
Page | Not supported. | New object type that contains properties and methods to replace forms. Code and triggers run on Microsoft Dynamics NAV Server. |
Report | Same as Previous versions of Microsoft Dynamics NAV. Reports have three new properties that are ignored. | Report datasets, sections, and request forms or pages are designed in the C/SIDE Report Designer. Report layout is designed with a report definition language editor such as Visual Studio. The layout information is stored in the new properties in the report object. |
Table | Same as previous versions of Microsoft Dynamics NAV. A new ExtendedDataType property has been added but has no affect on table behavior. Code and triggers run on the client. | Designed and executed in the same way as in the Classic client, with the same triggers and properties. The new ExtendedDataType property allows you to add metadata to fields to change how they are rendered. Code and triggers run on Microsoft Dynamics NAV Server. |
Web service | Not supported. | Web Services are designed by creating or reusing a page or page and codeunit objects together. XMLports can be used to send complex data to a Web service. Published by adding public references to the Web Service table. |
XMLport | Same as previous versions of Microsoft Dynamics NAV. The new functions for using XMLports with import/export of non-xml structured data are not available. | Designed and executed in the same way as the Classic client. XMLports have been extended with similar functionality to dataports to allow import and export of structured files. |
NAS | Same as previous versions of Microsoft Dynamics NAV. | Will continue to work as currently but recommend moving integrations to WS based platform |
0 comments:
Post a Comment