When triggered, the outbound web service action first runs the request message, if defined. This is managed by the handler class as defined for the web service action.
The goal of the request message depends on the HTTP action of the web service action. In general, the request message provides the web service with data from D365 FO.
If the HTTP action is:
- Post, use the request message to provide the web service with the data to be created in the external application.
- Put, use the request message to provide the web service with the data to be updated in the external application.
- Get, you can use the request message to provide the web service with search criteria to get the desired data. If no request message is defined, the web service is triggered based on the resource. In this case, the web service defines which data is sent back. Note: If the web service access type is:
- SOAP: The output of the request message is added to the request in a SOAP envelope. In this case, make sure this is properly set up in the target document and the field mapping of the request message.
- REST: The output of the request message is used to parameterize the URL.
- Patch, use the request message to provide the web service with the data to be updated in the external application. Use this to only update a part of a resource. For example, only update a contact person of a customer.
- Delete, use the request message to provide the web service with the data to be deleted from the external application.
- Post or put, use the request message to provide the web service with the data to create or update data in the external application. To determine if the data must be created or updated, on the web service action, an attribute must be defined with the Key check box selected.
For a request message the:
- Source connector must be of type D365 FO.
- Source document must be an internal document.
- Target connector must be of type Azure file storage or Web service.
- Target document must be an external file-based document.