Today I would like to talk about how to add “actions (buttons)” on Request Page of Report/XMLport in Business Central.
In Dynamics 365 Business Central, actions are displayed at the top of each page, referred to as the action bar.
Today I would like to talk about how to add “actions (buttons)” on Request Page of Report/XMLport in Business Central.
In Dynamics 365 Business Central, actions are displayed at the top of each page, referred to as the action bar.
In this video, I show, not one, not two, but three different ways to process XML data without using an XMLPort. AL now has native XML data types and all three methods use the new data types.
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
We all know how to remove Namespaces from the XML if we want to import it from NAV XmlPort, I just faced a situation where I was using XmlPort to send Soap Request with Default Namespace.
When developing in dynamics NAV I cam across an annoying issues when trying to run an XML port through the SOAP service. The application was a build server that would, after importing and re-compiling all new objects, run XML ports with new updated data.