1. Data Management
  2. Connectivity Studio
  3. Activities

Run message for testing purposes
Application task

You can run a message for testing and troubleshooting purposes. You can find and analyze the results in the:

  • Message history.
  • File history if the message has an Azure file storage connector with file actions.
  • Tracer if you have used the tracer on the message run.
Note: If the message setup is validated, a message run can still result in errors or give an unexpected result. In this case, you can choose to store all processed records in the message history for analysis purposes. To do so, before the test run, on the message header, set the Store history field to 'Yes'. When the issue is solved, do not forget to set the Store history field back to 'No'.


Standard procedure

1. Click Connectivity studio - Integration design.
2. On the Message tab, in the list, find and select the desired message.
3. Click Run.
4. You can use a tracer to register what a message does when it is running. When a message has run using the tracer, you can review the registered actions in the tracer. Usually, you use this to find issues in the message run.
  Select Yes in the Use tracer field.
 

Note: You can use the tracer in combination with the test quantity.
5. To test a message, you can run it for a defined number of records only. In this way, testing is quicker and with less history or tracer records to be reviewed. You can use this, for example, to test a message in the design phase.
If the message is used to:
- Export data, the records are taken from D365 F&SCM, as defined by the source document.
- Import data using an external file-based document as source document, the records are taken from the file as defined in the message run dialog.
- Import data using an external ODBC document as source document, the records are taken from the external database.
Example: If the test quantity is 2, only the first two records found are used.
  In the Test quantity field, enter a number.
 

Note: You can use the test quantity in combination with the tracer.
6. If the message is used to import data using an external file-based document as source document, define the file with the test data.
  In the File name field, enter or select a value.
 

Note:

This field is available only if the source connector is of one of these types:

  • Azure file storage
  • Azure Blob storage
  • SharePoint
7. To test the message, you can select a specific staging journal to be processed instead of processing all staging journals.
  In the Staging journal field, enter or select a value.
 

Note:

  • The Staging journal field is available only if the source connector is of type Staging journal.
  • The source connector defines from which company you can select a staging journal: All companies or the current company.
  • You only can select staging journals with the message status 'To be processed' and the journal status 'Approved'.
  • In case of the generic staging journal, you can only select staging journals that are created with the same document as the message source document.
  • If you use the tracer, you can view the steps that are processed for the selected staging journal.
8. Click OK.
Related to Notes

Troubleshooting messages

 		 

See also

Provide feedback