Web service exports enable a tight integration with other applications by enabling data to be sent directly from one system to another. Sales orders can be exported individually, if desired, providing real-time integration.
Should you need to integrate large numbers of orders at scheduled times, take a look at the data file example of exporting.
Data is exported via templates which specify the fields exposed for exporting, as well as the data file type, the field and record separators, and the record types used in the destination file. Templates are also used to define fields that can be used as criteria to filter exported data.
Web Service Export Example
The sales orders template used to manage the export of basic customer data, addresses, contacts, and bank information is “SOH” (Sales Order - Header).
You need a SOAP connection pool in X3, named IMPORT-EXPORT, to use the provided Postman collection. If you need to create one, refer to Creating a SOAP Connection Pool.
You also need OAuth2 authentication configured for X3. If it is not, follow the instructions in the SOAP Web Services Guide.
After importing the collection into your Postman, follow these steps to export customers:
- Select the Export Sales Orders request.
- Update the URL to point to your X3 solution.
- Under the Authorization tab, click Get New Access Token.
- Complete the GET NEW ACCESS TOKEN dialog box using the values from your OAuth2 service, then click Request Token. Refer to Using Google OAuth2 to Make a Web Service Call, for help.
- Click Use Token in the MANAGE ACCESS TOKENS dialog box.
- Click Send.
Note: If you wish to export the same records more than once, you will need to set the I_CHRONO property to “NO”. For many tables, X3 tracks which records have been exported, and this option can prevent re-exporting records that have not changed.
To find out how you can build your own export templates, and take advantage of more functionality, see the Import/Export Guide.