Web service imports enable a tight integration with other applications by enabling data to be sent directly from one system to another. Sales orders can be imported 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 importing.
Importing data leverages the very same business logic as the X3 UI (User Interface) to provide consistent validation and referential integrity across input methods. This common logic also provides default data. For example, when populating the order date, the delivery date is calculated for you.
Data is imported via templates which specify the fields exposed for importing, as well as the data file type, the field and record separators, and the record types used for the source data.
Web Service Import Example
The sales order template used to manage the import of basic customer data, addresses, contacts and bank information is “SOH” (Sales Order - Header). You’ll find the template and demonstration data in X3’s “SEED” folder.
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 import customers:
- Select the Import Sales Orders request.
- Update the URL field 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.
To find out more, and take control of more functionality, see the Import/Export Guide.