![]() To do this, you create the file in a temporary folder, and then download it to the client after the export is completed. In this walkthrough, you will save the XML document on the client computer. You will use the name of the XMLport later in the codeunit.Īfter you have created the XMLport, you create the codeunit that will run the XMLport and save the data. In the Name text box, enter CustomerXMLport, verify that the Compiled check box is selected, and then choose the OK button. In the Save As window, enter 50001 in the ID text box. For this walkthrough you can select the following fields. Repeat these steps to select additional fields that you want to export. row and use the right arrow button to indent the field one time to make it a subset of the Customer element. White space in the name will result in a compile error. The name that you enter in the Node Name column cannot contain spaces. You can enter any name, but because of consistency you might want to enter the name of field that you select. This node represents the fields in the record. In the Node Name column, enter a name for the field. ![]() field from the Field Lookup window, and then choose the OK button. In the Data Source column, select the No. In the next empty row under the Customer row, in the Node Type column, select Element. The next step is to select the fields that you want to export. Select the Customer row and use the right arrow button to indent the row one time to make it a subset of the Root element. The data will be exported from the Customer table. In the Data Source column, select the Customer table (18) from the Table List window. This node represents a customer record in the XML document. In the second row, in the Node Name column, enter Customer. This node represents the beginning of the XML document. In the Source Type column, verify that Text is selected. In the Node Type column, verify that Element is selected. In XMLport Designer, in the first row, in the Node Name column, enter Root. In the XMLport-Properties window, locate the Format Property (XMLports), verify that the Value column is set to XML and then close the XMLport-Properties window. ![]() In the XMLport-Properties window, locate the Direction Property, choose the drop-down arrow in the Value column and then set it to Export. On the View menu, choose Properties to open the XMLport-Properties window. In Object Designer, choose XMLport, and then choose New to open XMLport Designer. In the Microsoft Dynamics NAV Development Environment, on the Tools menu, choose Object Designer. You define the table and fields that you want to export in XMLport Designer. You create the XMLport by designing it in XMLport Designer and setting the properties for the XMLport. Simon knows that he can use XMLports to convert the records in the table to XML format that can easily be shared with the colleague. The information will be shared with another colleague who works on a different computer system. The records will include only the No., Name, Address, City, and Contacts fields. He has been asked to export records from the Customer table to an XML document. Simon is a Microsoft Certified Partner working for CRONUS International Ltd. Microsoft Dynamics NAV 2018 installed with a developer license. To complete this walkthrough, you will need: This walkthrough illustrates the following tasks:Ĭreating the codeunit that will run the XMLport. ![]() This walkthrough shows you how to export data from a Dynamics NAV table into an XML document. You define the output stream that will export the data and location where the XML document should be saved in the codeunit. In this walkthrough, you will call the XMLport from a codeunit. XMLports are called and run from codeunits or run from Object Designer. You only need a basic knowledge of XML to design and work with XMLports. Exporting data from your Dynamics NAV database into XML format enables seamless exchange of information between different computer systems. XMLports are used to export data from a Dynamics NAV database to XML format or import data from an XML file to Dynamics NAV database.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |