--- title: "View data exchange history" slug: "view-data-exchange-history" tags: ["Task", "Data Modeling Studio", "DMS"] updated: 2026-03-20T11:29:25Z published: 2026-03-20T17:44:45Z canonical: "docs.staedean.com/view-data-exchange-history" --- > ## Documentation Index > Fetch the complete documentation index at: https://docs.staedean.com/llms.txt > Use this file to discover all available pages before exploring further. # View data exchange history In Data Modeling Studio, for monitoring purposes, executed actions are logged. The main activities for which logging is done are: - **Deploy**: All actions that are executed when you deploy a data model are logged. Each time you deploy a data model, an execution ID is created to which all executed deploy actions are related - **Data export**: All actions that are executed when you export data are logged. - **Metadata updates**: Metadata updates are only logged if on the **Data modeling studio parameters**, **Log metadata updates** is '**Yes**'. > [!NOTE] > Note > > On deploy or data export, executed SQL statements are only logged if on the **Data modeling studio parameters**, **Log executed SQL statements** is '**Yes**'. Logging is done on three levels: - **Summary**: Each deploy or data export results in a record in the summary. Each record is identified by the context (data model) and the execution ID. - **Log**: The actions that are executed by the deploy, data export, or metadata update. - **Processing**: The export statistics for each exported business entity (data set or data entity) as defined for the deployed or exported data model. ### Steps 1. Go to **Data modeling studio > Data modeling studio > Data exchange monitoring**. 2. You can choose to show the data exchange history: Select **Yes** in the **Show all log and processing records** field. > [!NOTE] > Note > > Metadata updates are logged without an execution ID. So, you cannot find and select metadata updates in the **Summary** section. When **Show all log and processing records** is set to '**Yes**', in the **Log** section, you can find metadata update logs with the '**Metadata caching**' context. - **By execution ID**. To do so, set the **Show all log and processing records** field to '**No**' and in the **Summary** section select the desired record. - **For all logged entries**. To do so, set the **Show all log and processing records** field to '**Yes**'. Use this option, for example, to view metadata update logging. 3. Sub-task: View history by execution ID. 1. If you want to monitor the data exchange history by execution ID, in the **Summary** section, select the desired execution record. As a result, in the: In the **Summary** section, find and select the desired record. - **Log** section, you can view the actions that are executed for the selected execution record. - **Processing** section, you can view, per business entity, the export statistics. > [!NOTE] > Notes > > Field descriptions of the **Data exchange monitoring** page. ### Summary | Field | Description | | --- | --- | | Context | In the **Summary** section, this is the data model name. | | Execution | Each deploy or data export results in a record in the summary, which is identified by a unique execution ID. | | Status | The status of the execution. For example, '**Failed**' if a Deploy went wrong, '**Succeeded**' if a data export went well, or '**Started**' if currently a data export is running. | | Last updated by | The user who started the deploy or data export. | | Origin | The origin always is '**D365FOE**'. | | Started | The date/time on which the deploy or data export is started. | | Ended | The date/time on which the deploy or data export is ended. | ### Log | Field | Description | | --- | --- | | Origin | The origin can be: - **D365FOE**: For all deploy and data export actions. - Diagnostics: For metadata updates. | | Subject | A short description of the logged action. > [!NOTE] > Note > > On the **Data modeling studio parameters**, for diagnostics reasons, you can indicate if executed SQL statements must be logged as well. If so, the subject is '**Diagnostics**'. | | Message | A more detailed description of the logged action. | | Type | Indication of the result of the logged action. If 'Info', the action is executed successfully. Otherwise, possibly, some action is required. | | Last updated by | The user who started the deploy, data export, or metadata update. | | Execution | The unique identification of the related deploy, data export, or metadata update. | | Last updated | The date/time on which the action is logged. | | Context | If the logged action is related to: - Deploy or data export, the related data model name is shown. - Metadata update, the context is 'Metadata caching'. | ### Processing | Field | Description | | --- | --- | | Object | The business entity (data set or data entity) which data is exported. | | Group | The group 'tag' as defined for the data set. | | Origin | The origin always is '**D365FOE**'. | | Action | The action always is '**Export**'. | | Mode | The mode depends on the data selection as defined for the related data set. If the data selection is: - '**All data**', the mode is '**Full**' - '**Change tracking**', the mode is '**Incremental**'. - **Timestamp**, the mode is '**Timestamp**'. | | Source | The number of records in the source table in D365 F&SCM. | | Delta | The number of records that are exported by this export action. The number of exported records depends on the: - Data selection as defined for data sets. - Change tracking setting of the data entity tables. | | Started | The date/time on which the export is started. | | Ended | The date/time on which the export is ended. | | Result | The result of the export action. | | Execution | The unique identification of the deploy or data export activity to which the export action is related. | | Context | The name of the data model for which the export action is executed. | | Throughput | The number of records exported per second. | | Duration | The number of seconds the export took. | | Destination | The number of records in the related table on the target database. | ## Related - [Monitor data exchange](/monitor-data-exchange.md)