Set up the metadata-related parameters.
| 1. | Go to Data modeling studio > Data modeling studio > Parameters. |
| 2. | Click the Metadata synchronization tab. |
| 3. | Sub-task: Set application metadata parameters. |
| 3.1 | These fields together define the default value of the Application metadata field for each created data model: - Export labels - Export enumerations - Export data dictionary On creation of a data model, only if all three of these parameters are set to 'Yes', the Application metadata field on the Data model page is set to 'Yes'. If for a data model the Application metadata field is set to 'Yes', on deploy, these tables are created and filled in the target database: - CDPLabelStaging: This table contains the labels from D365 FO. So, in the target database, the UI labels are shown instead of the technical names. - CDPEnumerationsStaging: This table contains the enum value names from D365 FO. So, in the target database, the enum value names are shown instead of the enum value numbers. - CDPDictionaryStaging: This table contains all D365 FO tables. |
| In the Export labels field, select the desired option: 'Yes' or 'No'. | |
| 3.2 | In the Export enumerations field, select the desired option: 'Yes' or 'No'. |
| 3.3 | In the Export data dictionary field, select the desired option: 'Yes' or 'No'. |
| 3.4 | You can indicate if, on deploy, the CDPManifestTableSTAGING must be created in the target database. This table contains information of the Data modeling studio as installed for D365 FO. The information includes, for example, version information and used prefixes. On deploy, for the created CDPManifestTableStaging table, also the data is exported from D365 FO to the target database. |
| In the Export manifest field, select the desired option: 'Yes' or 'No'. | |
|
Note: In the target database, the CDPManifestTableSTAGING is (re)created on deploy of each data model. |
|
| 4. | Sub-task: Set processing metadata parameters. |
| 4.1 | These fields together define the default value of the Processing metadata field for each created data model: - Synchronize data export log - Synchronize data export details On creation of a data model, only if both of these parameters are set to 'Yes', the Processing metadata field on the Data model page is set to 'Yes'. If for a data model the Processing metadata field is set to 'Yes', on deploy, these tables are created and filled in the target database: - CDPLogStaging: This table is used to log the deploy and export history. It shows the export history using messages. - CDPProcessingStaging: This table is used to log the deploy and export processing history. It shows the technical details of the export history. On data export, the data in these tables is updated. |
| In the Synchronize data export log field, select the desired option: 'Yes' or 'No'. | |
|
Note: You can view the log and processing history on the Data exchange monitoring page. |
|
| 4.2 | In the Synchronize data export details field, select the desired option: 'Yes' or 'No'. |
| 4.3 | The deploy and export history is logged. You can view this history on the Data exchange monitoring page. Over time, the number of logged records grows. To limit the number of logged records in the database, you can refresh the history. If you refresh the history, the retention settings of these parameters are applied: - Log record retention (days): On refresh, only the log records are kept that are within the number of defined retention days. - Processing record retention (days): On refresh, only the processing records are kept that are within the number of defined retention days. Example: Number of retention days is 7. Today, on the Data exchange monitoring page, you click Refresh. As a result, all logged records are deleted that are older than a week. |
| In the Processing record retention (days) field, enter a number. | |
| 4.4 | In the Log record retention (days) field, enter a number. |
| 5. | Sub-task: Set data model metadata parameter. |
| 5.1 | The Synchronize data set configuration field defines the default value of the Data model metadata field for each created data model. If for a data model the Data model metadata field is set to 'Yes', on deploy, these tables are created and filled in the target database: - CDPFieldsStaging: This table contains the fields of the data sets and data entities tables that are added to the data model. - CDPInputsStaging: This table contains the tables of the data sets and data entities that are added to the data model. |
| In the Synchronize data set configuration field, select the desired option: 'Yes' or 'No'. | |
| 6. | Sub-task: Set entity export status parameter. |
| 6.1 | You can use the Entity export status table to store all entities (data set tables and data entities) as used on data models. When data exports are done, this table also stores the export status for each of the tables. |
| In the Entity export status field, select the desired option: 'Yes' or 'No'. | |
| 7. | Sub-task: View metadata table dates. |
| 7.1 | For the Data modeling studio metadata tables, the data is collected in D365 FO and stored in these tables in D365 FO. On deploy or export, for some of these metadata tables, the data is taken from these metadata tables in D365 FO. For other metadata tables, the data is used in data modeling. It is important to keep the data in the metadata tables up to date. |
| To update the metadata in the metadata tables in D365 FO, click Update metadata. | |
|
Note: Make sure to update the metadata tables after each change or creation of a data model. |
| Related to | Notes |
|---|---|
|
Set up parameters |
