Release Notes > Known issues
  

Known issues

The tables in this section describe known issues for Data Governance and Catalog.

April 2025 known issues

Issue
Description
CDAM-4673
When using the PATCH endpoint with the data de-identification API, an error occurs if you do not include the precedence tier ID of the data de-identification policy in the request payload.
CDAM-4577
In a data filter rule, if a data element classification is mapped to more than one data element, an error occurs when you try to run a mapping in Data Integration with an Access Policy transformation. The data filter rule is unable to determine which column to filter on.
CDAM-4207
In data de-identification rules, if a data element is mapped to more than one data classification, the default data protection applies.
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.
SCAN-19980
If you run a data observability job in a catalog source and cancel the job before completion, Metadata Command Center deletes the catalog source.

February 2025 known issues

Issue
Description
CDAM-4477
If you use data filter policies or data de-identification policies that might be applied in an Access Policy transformation in Data Integration that use dates, configure them as timestamps. As a best practice, create two data filter rules: one with dates and one with timestamps with the same values.
CDAM-4278
When you set the enableFileBasedAudit parameter to "true" for writing Data Access Management audit events to disk, the customFileBasedAuditPath parameter is ignored. As a result, all audit events are written to the standard output stream (stdout).
You can find the audit event logs at <infaagent>/apps/Data_Access_Management_Agent/<version>/log/system/log/archived/.
The log messages appear with a message ID of AUDIT_LOGGER.
CDAM-4123
Due to timestamp precision, if you create a data filter rule that uses a timestamp in the filter criteria, and you use the "is any of" operator, you are unlikely to match any values, and therefore will not have any records filtered out. Conversely, if you use the "is not any of" operator, you are likely to have all records filtered out.
CDAM-4122
Due to decimal precision, if you create a data filter rule that uses a decimal in the filter criteria, and you use the "is any of," "is not any of," "is greater than," or "is less than" operator, you are likely to either not have any records filtered out or have all records filtered out.
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-3292
If your data collection includes a Data Governance and Catalog dataset object, your query will fail. To avoid this, select only table and view objects.
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.
CDAM-2344
When running a mapping that includes an Access Policy transformation in Data Integration, an error occurs if the name of a column in the source has special characters.
CDAM-2307
If you add parameters to any other asset after adding parameters to an Access Policy transformation, Data Integration prevents you from saving the mapping.
CDAM-1942
When creating a mapping that includes an Access Policy transformation in Data Integration, an error might appear if you add parameters and save the mapping. To clear the error, generate a new consistency seed and click Run.
CDAM-1578
When creating a mapping that includes an Access Policy transformation in Data Integration, a nondescript error appears if you do not have the Data Marketplace Role and you attempt to select user type.
CDAM-1447
An error occurs when you attempt to query a data source with certain PostgreSQL data types. For a list of data types that you can use, see "Data Types" in the Data Governance and Catalog help.
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. 1In Metadata Command Center, open the catalog source.
  2. 2On the Data Profiling and Quality tab, select the Agent Cache option in the Cache Result field.
  3. 3Run the catalog source.