MDM page - Routines list
Repository
Master Data Management Routines List
Purpose of the page¶
This page makes it possible to create routines for importing and exporting data.
Buttons and/or links on the page
| Element | Description |
|---|---|
| - Details: makes it possible to define the content of the routine. - Copy routine details: creates a copy of the selected routine. |
Attributes tab
Please find below the most important fields.
| Field | Description |
|---|---|
| Info | : routine locked; can only be edited and run by authorised users. the user is not authorised to access the Source DB specified in the routine, or the role associated with the user or the role of their reference user does not have the 0003568 - Master data management: Export DB with MDM function enabled; the user is not authorised to access the Target DB specified in the routine, or the role associated with the user or the role of their reference user does not have the 0003569 - Master data management: Import DB with MDM function enabled; |
| Code | Routine ID |
| Target DB | Database into which the selected routine will update the tables or import the setups |
| Sorting | Order in which the selected routines will be performed |
| Disable detail audit | Determines the level of detail at which the performance of the routine is audited. If selected, it ignores changes to the synced tables and only registers the performance of the routine. Note: Please only select the tick-box to speed up operations for en masse synchronisations. |
| Automatically include the required tables | Also syncs the tables linked to the selected table to avoid primary key violations and partial synchronisations of metadata. Synchronisation of linked tables is limited to the elements called up by the tables chosen by the user. Note: please use the tick-box for all routines. |
| Run in steps only | Runs the routine in steps, requiring synchronisation to be manually confirmed for each one. Note: if not selected, the system shows the changes at the end of the operation without allowing the user to restore the previous situation. |
| Do not run deployment of the application after termination of the routine | Prevents the MDM engine from automatically launching the necessary deployments, in relation to the recently updated definition tables. Note: if the tick-box is selected, deployments must be launched manually. |
Details attributes tab
Repository > Master Data Management > Routines > Elements > Details
On this page, it is possible to define the content of the routine.
Please find below the most important fields.
| Field | Description |
|---|---|
| Action | Include or exclude the selected table. |
| Table | Specify the table or logical groupings of the tables to be synchronised. - **$ |
| Include the child tables automatically | Includes all tables linked to the selected table. |
| Deletion method | Manage data in databases before synchronising. - Delete: automatically deletes absent records from the source database, only if the table on which the routine acts has no links to other tables in the database. Note: if there are links to other tables, CCH Tagetik highlights the records that should be deleted manually from the target database in the performance audit (). - Delete only the rows produced by MDM: automatically deletes from the source database the absent records that were inserted during the previous running of Master Data Management. IMPORTANT: The origin of the record taken into account by the MDM does not correspond to the 'origin' field available in the metadata list. While the latter may change even on records entered via MDM as a result of manual changes, the origin of the records in this field will always be preserved. So Tagetik always knows if a record has been entered through previous synchronisations run by MDM. - Do not delete: syncs the existing records or new insertions without deleting or highlighting anything else. |
| Import SQL filter | Only for From database to database and From file to database routines . Filters the metadata tables to be synchronised. If applied to a node, it acts on all tables linked to that node. |
| Export SQL filter | |
| Fields exceptions | Selects the fields of the table not to be synchronised. - From database to file routine: the exclusion of columns is applied to the source environment and the excluded fields are included in the produced file. (Information is stored offline within the file's metadata) - From file to database routine: the exclusion only applies to rows added, for which the destination values will be kept. For rows being inserted, the target values of the excluded fields are left empty or set to the default values in the database. - From database to database routine: the exclusion applies to the rows added and rows updated, but the target values of the excluded fields will be kept for the latter. For rows being inserted, the target values of the excluded fields are left empty or set to the default values in the database. IMPORTANT: the exclusions are will only be applied if the tables to be synchronised were defined individually, not using a grouping. |