Multidomain MDM
- Multidomain MDM 10.2.2 Service Pack 1
- All Products
Reference Number
| Description
|
---|---|
HORA-52304
| If you perform the stage process in the Informatica platform, you cannot use the CleansePut API.
|
HORA-52303
| If you perform the stage process in the Informatica platform, the MDM Hub cannot detect the records that are hard-deleted in source systems.
|
HORA-52297
| When you enable the option to preserve the source system keys for Informatica platform staging, source system keys are not preserved.
|
HORA-52296
| When you perform Informatica platform staging, you cannot set up delta detection and audit trails for the staging table data.
|
HORA-51360
| When you perform Informatica platform staging, source records that indicate that the last updated date is in the future are inserted into the LAST_UPDATE_DATE column in the staging table.
Workaround: Configure transformations for the stage process that can reject records that indicate that the last updated date is in the future.
|
HORA-51362
| After you open a logical data object in Informatica Developer (the Developer tool), the Save button becomes available before you make any changes.
|
HORA-51075
| When you open a logical data object in the Developer tool, the following warning appears:
Workaround: You can ignore the warning.
|
HORA-50574
| During the Model repository synchronization process, the MDM Hub does not create a mapping with a logical data object to write to. To run Informatica platform staging, create a mapping that includes a physical data object as the source, a logical data object as the output, and a mapplet for cleanse operations.
|
HORA-50573
| When you synchronize the Model repository with the MDM Hub, the synchronization process creates a customized data object and a relational data object. Do not use either the customized data object or the relational data object as direct targets in any mapping that you define.
|
HORA-50500
| When you synchronize the Model repository with the MDM Hub, the synchronization process creates a logical data object read mapping and logical data object write mapping. If you open one of these logical data objects in the editor and then save them, the objects disappear from the Model repository.
Workaround: You can ignore the issue.
|