XMLports are used to export and import data between an external source and Dynamics 365 Business Central. Where we can easily map the tables and fields that are available in Business Central as well as the variables and constants to import/export data with XML format or any other format using the separator.
Those of us that have been around long enough will remember that Microsoft Business Solutions-Navision 4.0 came out with the new XMLport and MenuSuite object types. I can clearly remember a sort of astonishment about this UI-less XMLport. To allow you to feed this “pipeline” with data you had to wrap it in another object
One of the object types within NAV is called XMLPort, it’s used to exchange data with external applications in XML or CSV format. They are relatively easy to configure once you know what you’re looking at. The interesting bit is that using XMLPort objects one can execute more complex trigger logic.
XMLPort is a nice tool that allows you quickly import and export xml files. The tool has some shortcomings, but there is always a work around it.
For an implementation recently I had to export an xml and it could not have empty xml nodes. For example. Bellow is an xml file created by xmlport