Hi, I'm Ask INFA!
What would you like to know?
ASK INFAPreview
Please to access Bolo.

Table of Contents

Search

  1. Introduction
  2. Installation and Upgrade
  3. MDM Multidomain Edition Version 10.2 HotFix 2
  4. MDM Multidomain Edition Version 10.2 HotFix 1
  5. MDM Multidomain Edition Version 10.2
  6. Informatica Global Customer Support

Release Notes

Release Notes

Business Entity Services Known Limitations

The following table describes known limitations:
In previous releases, business entity services were called composite services.
Reference Number
Description
MDM-14375
When you specify more than one recordState for the GetRelated SOAP API, an error occurs.
MDM-13715
When you merge records with the WriteCO API, an error occurs.
HORA-51932
When you perform a partial promote of components related to composite objects in Repository Manager, validation errors might occur.
Workaround: Promote the complete composite object configuration.
HORA-51931
When you promote a searchable composite object configuration in Repository Manager, validation errors occur.
Workaround: Promote the complete composite object configuration that the searchable composite object configuration is associated with.
MDM-10553
HORA-51886
When you run a read composite service for a deleted grandchild record, the composite service call does not return data.
HORA-51824
When you promote a REST service in Repository Manager, validation errors occur.
Workaround: Promote the composite services configuration.
HORA-51494
The MDM Hub does not prevent you from creating a child record that does not share the same effective period as the parent record.
Workaround: Ensure you maintain timeline consistency within a composite object when you create a record.
HORA-51488
When you read a pending record, the composite service does not return the record and an error occurs.
Workaround: Add
?recordStates=ACTIVE,PENDING
to the REST URL.
HORA-51285
The MDM Hub does not prevent you from deleting a record that has an active child record.
HORA-49806
Repository Manager does not handle conflicts correctly during composite object configuration promotion. When multiple objects in a composite object have the same name but their hubObject values refer to different base objects, Repository Manager generates validation errors but successfully promotes the composite object configuration.
Workaround: Use unique names for objects that do not refer to the same base objects.

0 COMMENTS

We’d like to hear from you!