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 November 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
Data Governance and Catalog
.

July 2025 known issues

Issue
Description
CDAM-5553
If you’re using a connection to Databricks to apply
data access policies
through pushdown or proxy services, you cannot use the Secret Vault configuration option.
CDAM-5360
Attempting to change the enforcement method of a
data filter policy
through the data filter API with the PATCH or PUT method invalidates that
data filter policy
.
CDAM-4711
If in your organization, you define user roles of the same name with a different case, an error occurs when
Data Access Management
attempts to push a
data access policy
to your cloud data provider. The policy is not pushed down.
CDGC-82928
The
Save
button for the catalog source is disabled if you apply the data observability exclude metric filter for
Data Type
and
Data Freshness
.
CDGC-82861
Data de-identification policies
automatically inherit stakeholders from the associated
precedence tiers
. Although the user interface does not display these stakeholders, you can still initiate a workflow.
CDGC-82823
When you open a data observability anomaly event page for the first time, the bar chart for the selected metric might not appear.
As a workaround, refresh or reopen the data observability event page to load the bar chart.

April 2025 known issues

Issue
Description
CDAM-4195
If an administrator deselects the View
Data Access Management
feature privilege for a user role, the Data Access tab still appears in the left navigation for users with that user role.
CDGC-78895
On the
History
tab of a ticket page, the
Task Assignee Users
and
Task Assignee Groups
attributes display the values,
Deleted User
and
Deleted Group
even when the asset has no stakeholders that were deleted.
CDGC-77401
On the
New Tasks Inbox
Unassigned Tasks
tab, the system displays tasks that are assigned only to you until you click the
Claim
button. The
Claim
button appears even for tasks without multiple stakeholders.

February 2025 known issues

Issue
Description
CDAM-4045
When using Managed Access in
Data Marketplace
with an Oracle source system, if the Oracle connection permissions are incorrect, it might fail silently, not presenting any tables to the user.
CDAM-2623
When running a mapping that includes an Access Policy transformation in
Data Integration
, policy resolution fails and an error appear if the source is Amazon S3 in Parquet or Avro format.
MDP-6191
When you import assets that have custom attributes values with commas, the bulk import job reports an error.
SCAN-16942
The Amazon S3 file type
ORC
appears as 'Undefined' in
Data Governance and Catalog
.

November 2024 known issues

Issue
Description
MDP-5743
If there are duplicates in the reference source system or in the endpoints, after you perform case-insensitive connection assignment, the unmatched assets might still appear as reference objects in the endpoint hierarchy.
SCAN-14621
Reference resource names for SAP Business Warehouse and SAP BW/4HANA catalog sources appear as 'XXXX' in the lineage.

September 2024 known issues

Issue
Description
MDP-2133
The job for previewing failed rows for SAP Business Warehouse (BW) and SAP S/4HANA catalog sources fails with an error.
To work around this issue, perform the following steps:
  1. In
    Metadata Command Center
    , open the catalog source.
  2. On the
    Data Profiling and Quality
    tab, select the
    Agent Cache
    option in the
    Cache Result
    field.
  3. Run the catalog source.

0 COMMENTS

We’d like to hear from you!