MDM Preferences
In the preferences node, set the global configuration preferences for the whole project.
General
Global Source Deletion Strategy
Global settings of Source Deletion Strategy used as default for all newly created load operations.
-
deactivate(default): Records are still part of a match and merge process and can provide business linage (logical delete). Deactivated records are available in export interface (see Export scope setting). -
delete: When a record is deleted it is no longer available to any MDM hub processes. To remove a deleted record from the repository, either run the Process Purge Service (for more information, see Read-write Services, section Process Purge Service) immediately, or remove it by using the housekeeping request (for more information, see REST API, section Purge).
Global Export Scope Setting
Global settings of the Export Scope used as default for all newly created load operations.
-
existing(default): Export operation reads all records from MDM hub storage (including deactivated). -
active: Export reads only active records from MDM hub storage.
Generate Record Counters
If enabled, this generates Record Counter steps into transformation plans (cleansing, matching, aggregations and merging). Record Counters are typically used to measure the performance of each transformation plan.
Record Counter Batch Size
Size of virtual batch (in number of records) in generated Record Counters. (Default value: 100 000).
Enforce Format in Generated Outputs
If enabled, only the columns listed in the Required Columns section of the Integration Output step will be provided to the output. If disabled (default), all columns available in the flow are provided to the output.
Length-Validation Settings
Database dependent length-validation setting for entities, columns and also for derived indexes according to the limitations of different database implementations.
Database Type
Choose the vendor of the database you are using. This value will drive validations of table, column, and index name length. (Default value: Oracle).
Length of NME Prefix
Length of NME prefix (including underscore at the end) specified in nme-config.xml configuration file (by default in Files>etc folder).
This value will drive validations of table, column, and index name length.
(Default value: 2).
If History Plugin is enabled in nme-config.xml, set the length as the maximum value of the NME or History prefix.
|
Advanced Settings
Global definition of Ignored Comparison Columns and behavior of compound PK and FK in the Instance Layer.
Do not Duplicate Compound or Alternative Keys
If enabled, only the MDM hub internal primary key source_id and derived foreign key <parent_entity>_source_id will be used in MDM hub storage.
If disabled (default), the MDM hub internal primary key source_id and derived foreign key <parent_entity>_source_id will be used in MDM hub storage, as well as compound or alternative primary and foreign keys defined in Connected Systems.
You can use this option to propagate compound or alternative keys from Connected Systems into the MDM hub storage as separate columns.
SRC String Length
Length of an attribute on source layer.
SRC prefix attributes are generated when the original attribute type is not string.
For example, birth_date is modeled with day type, but src_birth_date must be string (thus length is determined by this parameter).
EXP String Length
Length of an attribute that stores explanations. The attribute has to be string type only and this parameter determines the string length.
Default Ignore Comparison Columns
Select input columns that will be ignored only during the batch load processing, that is, in Change detection subtask. This option is usually set for attributes where data changes are not business relevant (for example, relevant record attributes remain unchanged, but record timestamp has changed because of an update of other non-processed attributes).
source_timestamp column is always ignored by default.
|
Was this page useful?