An outbound web service action can only be triggered by D365 FO. When triggered, the outbound web service action automatically runs the defined messages.
You can run an outbound web service action on these levels:
Name | Responsible | Description | |||||||||||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
Run project |
Application Consultant |
You can use a project to exchange data. To be able to run a project, tasks must be set up for the project. If you run the project, all related tasks are run. Depending on the tasks that are set up for the project, you can use a project to run:
Usually, you run a project in batch. Based on the defined sub-projects and tasks dependencies, tasks are run in parallel. If you do not run the project in batch, all sub-projects and tasks are run sequentially. |
|||||||||||||||||||||||||
Run task |
Application Consultant |
You can use a task to run the execution of:
If you run a task, all defined messages, outbound web service actions, batch classes, and master data entities are run. Usually, you run a task by running the related project. In this case, all tasks of the project are run, taking into account the defined task dependencies. However, you can run a single task, for example, for testing purposes. |
|||||||||||||||||||||||||
Run web service action |
Application Consultant |
If you want to run an outbound web service action immediately, you can run it from the Web service action page. |
|||||||||||||||||||||||||
Run web service action from a button |
Application Consultant |
You can use button on a form to run an outbound web service action. You can add a button to a form in these ways:
|
|||||||||||||||||||||||||
Process data synchronization log |
Application Consultant |
For messages and web service actions, you can use table events to track data changes. You can define, for each table, which table events are logged. The table events are logged in the Data synchronization log.To fully process the logged events, process the:
This topic explains how to process the data synchronization log.
|
Number of pages | Page size | Limit records | Number of records to be processed | Result |
---|---|---|---|---|
5 | 10,000 | No | 40,000 | 4 pages of 10.000 records are processed |
5 | 10,000 | Yes | 40,000 | 4 pages of 10.000 records are processed |
5 | 10,000 | No | 80,000 | 5 pages of 16.000 records are processed |
5 | 10,000 | Yes | 80,000 | 5 pages of 10.000 records are processed |
Process outbound queue
Application Consultant
This topic explains how to process the outbound queue.
In the outbound queue, several entries can exist for a unique message or webservice action. How these entries are processed, depends on whether bundling is active. You can activate bundling on the data synchronization setup of an outbound:
If the bundling field is set to:
Name | Responsible | Description | |||||||||||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
Run project |
Application Consultant |
You can use a project to exchange data. To be able to run a project, tasks must be set up for the project. If you run the project, all related tasks are run. Depending on the tasks that are set up for the project, you can use a project to run:
Usually, you run a project in batch. Based on the defined sub-projects and tasks dependencies, tasks are run in parallel. If you do not run the project in batch, all sub-projects and tasks are run sequentially. |
|||||||||||||||||||||||||
Run task |
Application Consultant |
You can use a task to run the execution of:
If you run a task, all defined messages, outbound web service actions, batch classes, and master data entities are run. Usually, you run a task by running the related project. In this case, all tasks of the project are run, taking into account the defined task dependencies. However, you can run a single task, for example, for testing purposes. |
|||||||||||||||||||||||||
Run web service action |
Application Consultant |
If you want to run an outbound web service action immediately, you can run it from the Web service action page. |
|||||||||||||||||||||||||
Run web service action from a button |
Application Consultant |
You can use button on a form to run an outbound web service action. You can add a button to a form in these ways:
|
|||||||||||||||||||||||||
Process data synchronization log |
Application Consultant |
For messages and web service actions, you can use table events to track data changes. You can define, for each table, which table events are logged. The table events are logged in the Data synchronization log.To fully process the logged events, process the:
This topic explains how to process the data synchronization log.
|
Number of pages | Page size | Limit records | Number of records to be processed | Result |
---|---|---|---|---|
5 | 10,000 | No | 40,000 | 4 pages of 10.000 records are processed |
5 | 10,000 | Yes | 40,000 | 4 pages of 10.000 records are processed |
5 | 10,000 | No | 80,000 | 5 pages of 16.000 records are processed |
5 | 10,000 | Yes | 80,000 | 5 pages of 10.000 records are processed |
Process outbound queue
Application Consultant
This topic explains how to process the outbound queue.
In the outbound queue, several entries can exist for a unique message or webservice action. How these entries are processed, depends on whether bundling is active. You can activate bundling on the data synchronization setup of an outbound:
If the bundling field is set to:
Related to | Notes |
---|---|
Set up data synchronization - Table events - Outbound web service action |
  |
Run outbound web service |
  |