Automatically create a XMLport from a XML schema.
Simply load the schema, give an object number, select the root node, and click “Generate”. Finished! The rest is small business.
In my Payroll development I created a solution to import and export setup data from one company to another. This is done via XMLPort.
This is the third (and last) post in a series about using XMLPorts in Web Services. The first post showed XMLPorts can be used in Web Services without any line of C/AL code. The second post explained why C/AL code is not needed to export data with the Web Service and how the data is converted into a strong type by Visual Studio.
If you haven’t already read part 1 you should do so here,before continuing to read this post.
You have seen how to use an XMLPort in a Web Service without any line of code. That was amazing,wasn’t it? Now,how was this possible?
About two weeks ago I posted an explanation why Pages are not always sufficient for use with web services. Using XMLPorts in web services offer powerful possibilities that are not available with Pages.
You are trying to create a CSV file in NAV2009 using an XMLPort, but you want no field delimiter.
When you try to enter a blank in the field “FieldDelimiter” it keeps defaulting to <">
Periodically we receive support requests about XMLport errors, which really are missing features in xmlport’s functionality.
However most of these requests are rejected because: xmlports are not supposed to fulfill all possible xml standard scenarios.
Vertalen
