The XMLport object is conceptually related to a dataport. You can also use XMLports to import and export data, but in XML format. XMLports make the process of exchanging data in XML between systems more simple and streamlined. You only need a basic knowledge of XML and you do not have to create XML documents using external products.
If you have used dataports to import or export data, your application will run on the Classic client but will result in run-time errors on the RoleTailored client. If your application runs on both the Classic and the RoleTailored clients, we recommend that you use XMLports instead of dataports to import and export data. XMLports are supported on both the Classic and RoleTailored clients. You can configure XMLport objects to achieve the same functionality as dataports in previous versions of Microsoft Dynamics NAV.
When you are developing for Microsoft Dynamics NAV Server, you can use additional properties and have access to additional functionality. Request pages and import and export text functionality have been added to XMLports. These properties are visible in the Classic client so that you can access them in XMLport Designer. However, setting or executing an XMLport with these properties in the Classic client has no effect.
Importing and exporting text also works differently in XMLports:
-
XMLports do not have an OnBeforeExportRecord trigger.
-
XMLports support multiple languages for the CaptionML and Language properties.
-
XMLports support UTF-8 and UTF-16 formats for XML.
 Note |
|---|
|
With dataports, you can use the CurrFile object to read and write directly to the input or output file. XMLports do not have a CurrFile object. |
