When a batch load or Put API inserts or updates a record,
Informatica MDM Hub
uses the staging table lookup configuration to translate source system foreign keys into
Informatica MDM Hub
foreign keys.
Disabling Referential Integrity Constraints
During the initial load/updates, or if there is no real-time, concurrent access, you can disable the referential integrity constraints on the base object to increase performance.
Undefined Lookups
If you do not populate the lookup table and lookup column to define a lookup on a child object, you must repeat the stage process for the child object prior to executing the load process before you can successfully load data.
Allowing Null Foreign Keys
When you configure columns for a staging table, you can specify whether to allow NULL foreign keys for target base objects. The Allow Null Foreign Key staging table column property determines whether null foreign key values are permitted.
In the MDM Hub, an empty string is the equivalent of a null value regardless of the database type that contributes the empty string.
By default, the Allow Null Foreign Key check box is unchecked, which means that NULL foreign keys are not allowed. The load process:
accepts records valid lookup values
rejects records with NULL foreign keys
rejects records with invalid foreign key values
If Allow Null Foreign Key is enabled (selected), then the load process:
accepts records with valid lookup values
accepts
records with NULL foreign keys (and permits load inserts and load updates for these records)
rejects records with invalid foreign key values
The load process permits load inserts and load updates for accepted records only. Rejected records are inserted into the reject table rather than being loaded into the target table.
During the initial data load only, when the target base object is empty, the load process allows null foreign keys.