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

Table of Contents

Search

  1. Preface
  2. Release Notes for October 2025
  3. Administrator
  4. API Center
  5. API Manager
  6. API Portal
  7. Application Integration
  8. B2B Gateway
  9. B2B Partners Portal
  10. Business 360 Console
  11. CLAIRE GPT
  12. Cloud Data Integration for PowerCenter (CDI-PC)
  13. Data Governance and Catalog
  14. Data Ingestion and Replication
  15. Data Integration
  16. Data Marketplace
  17. Data Profiling
  18. Data Quality
  19. Data Validation
  20. Human Tasks
  21. Integration Hub
  22. MDM - Customer 360 SaaS
  23. MDM - Product 360 SaaS
  24. MDM - Reference 360
  25. MDM - Supplier 360 SaaS
  26. Metadata Command Center
  27. Monitor
  28. Multidomain MDM SaaS
  29. Operational Insights

Release Notes

Release Notes

Known issues

Known issues

The tables in this section describe known issues for
MDM SaaS
extensions
. Not all monthly releases include known issues.

February 2024 known issues

Issue
Extension
Description
CNXT-2612
Life Sciences
extension
for Customer 360 SaaS
If you deployed the extension before February 2024, enrichment assets of MedPro Systems are not imported during asset migration from one organization to another.
Workaround: To import the updated enrichment assets bundle, ensure that you have the Admin user role.
To use the updated enrichment bundle assets of MedPro Systems, contact Informatica Global Customer Support.

August 2023 known issues

Issue
Extension
Description
MDMN-114311
MDMN-117603
ESG
extension
for Supplier 360 SaaS
After you import the extension assets with the Designer user role, you can't view the custom pages and the search component.
Workaround: To view the custom pages and the search component, a user with the Admin user role can add them to the Supplier 360 business application. After you import the assets, add the pages and search component to the Supplier 360 business application with the administrator user role.

April 2023 known issues

Issue
Extension
Description
MDMN-107301
Life Sciences
extension
for
Supplier 360 SaaS
After you enrich a Customer 360 record with a MedPro Systems record, you can't enrich the Customer 360 record again. The enrichment fails with an incorrect update error.

February 2023 known issues

Issue
Extension
Description
MDMN-97919
Legal Entity Master
extension
for
Supplier 360 SaaS
When you select a value from a picklist with more than 1000 code values, the following error appears:
You do not have permission to view the values from this list. Contact your administrator to review your permissions.
Workaround: Decrease the picklist limit to 1000 code values.

January 2023 known issues

Issue
Extension
Description
MDMN-97844
Legal Entity Master
extension
for
Supplier 360 SaaS
When you enable Data Quality rules and search the GLEIF database to enrich a Customer 360 record, the enrichment fails with the following error:
"errorDetail":{"details":[ {"code":"BES.00081.7","message":"Failed executing RuleAssociation","localizedMessage":"Failed executing RuleAssociation","path":[],"rawErrorDetails":[]} ]}
MDMN-97235
Legal Entity Master
extension
for
Supplier 360 SaaS
When you enter the enrichment criteria to enrich a Customer 360 record and search the GLEIF database, the following error appears:
Something went wrong when we tried to render this page.
The issue occurs when the search doesn't return any matching data.

December 2021 known issues

Issue
Extension
Description
CNXT-521
Salesforce
extension
for
Supplier 360 SaaS
In an organization that uses Salesforce extension with real-time synchronization, the history feed in Customer 360 displays all the fields for a record as updated instead of displaying only the updated fields.

November 2021 known issues

Issue
Extension
Description
CNXT-469
Salesforce
extension
for
Supplier 360 SaaS
In an organization that uses Salesforce extension, import a hierarchy from Salesforce to Customer C360. If you now change the root node of the hierarchy in Salesforce and try to import the hierarchy again, a new hierarchy is created instead of updating the existing hierarchy.
Workaround: Delete the previous instance of the hierarchy in Customer 360.

0 COMMENTS

We’d like to hear from you!