1. To-Increase Dynamics 365 for Finance & Operations
  2. EDI studio
  3. Activities

Add message to task
Application task

For each task, you can define several messages. If you run a task, all defined messages are run.


Standard procedure

1. Click Connectivity studio Integration Design.
2. Click Tasks.
3. In the list, find and select the desired task.
4. Expand the Messages section.
5. Click New.
6. In the Message field, enter or select a value.
 

Note:
- You can also click Select to add several messages in one go.
- You can also add messages that belong to another project than the current task.
7. On import, usually, the target company is defined by the target connector of the message. You can overrule this target company here.
  In the Target company ID field, enter or select a value.
8. For each message, you can choose one of these actions:
- Undefined: A decision must be made to run or skip the message.
- Run: If the task is run, the message is run.
- Skip: If the task is run, the message is not run.
  In the Action field, select an option.
9. Sometimes, you want to import only the delta, which are the changes since the last import.
Example: During a migration project, often, some time elapses between the migration of the data and the go-live moment. Therefore, just before the go-live moment, you want to import the latest open transactions. However, you do not want to run the full migration again (see picture).
In Connectivity studio, you can do a delta run. To do a delta run:
- For a task, add the applicable messages with the Run for delta field set to Run.
- When you start the project run, on the dialog, set the Delta run field to Yes.
As a result, if a task is run, only the messages are run that have the Run for delta field set to Run. When a message is run in a delta run, only the record inserts are done. So, no update or delete of records is done.
  In the Run for delta field, select an option.
10. You can define a source connector for a task message. This source connector overrules the source connector of the message. In this way, you can use one message to:
- Import data into D365 FO from several sources.
- Export data from several D365 FO companies.
So, no separate message is required for each of the sources.
Example: Several sources provide item information to D365 FO. Each source places the data files in a separate storage. The file content structure is the same for each source. In this case, using different source connectors for task messages, you can import this item data into D365 FO with the same message.
  In the Source connector field, enter or select a value.
 

Note: To apply a task message source connector:
- For each source, enter a task message with the same message but a different source connector.
- The source connector you define for the task message must match the type of the source connector of the message. If the message connector type is:
- D365 FO -> D365 FO
- Database -> Database
- Staging journal -> Staging journal
- Azure file storage, Azure Blob Storage, and SharePoint are interchangeable.
- Connectors of type 'Web service' or 'Upload and download' are not supported.
- The data structure of the different sources must be the same.
11. You can define a target connector for a task message. This target connector overrules the target connector of the message. In this way, you can use one message to:
- Export data from D365 FO to several targets.
- Import data to several D365 FO companies.
So, no separate message is required for each of the targets.
Example:
D365 FO provides item information to several targets. For each target, the data files are placed in a separate storage. The file content structure is the same for each target. In this case, using different target connectors for task messages, you can export this item data from D365 FO with the same message.
  In the Target connector field, enter or select a value.
 

Note: To apply a task message target connector:
- For each target, enter a task message with the same message but a different target connector.
- The target connector you define for the task message must the match type of the target connector of the message. If the message connector type is:
- D365 FO -> D365 FO
- Database -> Database
- Staging journal -> Staging journal
- Azure file storage, Azure Blob Storage, and SharePoint are interchangeable.
- Connectors of type 'Web service' or 'Upload and download' are not supported.
- The data structure of the different targets must be the same.
12. Close the page.
13. Close the page.

See also

Provide feedback