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. |
CDGC-91544 | In Metadata Command Center, the data quality task for a catalog source fails when you enable remediation because the system incorrectly repeats the drive letter in the file path. This creates an invalid naming syntax that prevents the results file from being created. You experience this issue only on a Microsoft Windows machine where the Secure Agent is installed. |
CDGC-90152 | Column level lineage look incomplete when the lineage tree has more nodes than the default fetch limit. |
CDGC-89020 | In Metadata Command Center, if you remove the value specified in the Classification Category field of a data element classification, the system continues to use the latest value that was selected for the field. |
CDGC-88645 | If you select a single-hop lineage expansion, it results in additional unintended hops being displayed. |
CDGC-88592 | You cannot create or view data quality widgets in the chart view. You can view the search results in a list. |
CDGC-88578 | Authorization checks for user roles are missing. As a result, a user role such as the data steward has the same access and privileges as the administrator. This includes unauthorized access to services such as Administrator and Metadata Command Center. |
CDGC-88557 | On a Domain asset's details page, the Data Quality tab displays an inaccurate information for the Validity parameter because Data Governance and Catalog only processes the first 10,000 business terms that are associated with the Domain asset. |
CDGC-88448 | The dashboard fails to display search-based widgets where the results are filtered by a custom attribute. |
CDGC-88126 | When you use the Search for Assets API to view data element details from a catalog source, some text lose their capitalization. As a result, the response body might show the asset name and the associated glossary name in lowercase for names that are uppercase on asset pages. |
CDGC-87481 | If you add a custom business name to a technical asset in an exported file and then re‑import the file, it causes the bulk import job to fail. As a result, the custom business name is not applied. |
CDGC-86293 | Users authenticated through Single Sign-On (SSO) cannot be assigned a stakeholder role. |
CDGC-84926 | If you clear the description of a published Glossary Business Term and initiate a workflow, the description is repopulated with the original published content during subsequent workflow steps. |
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-80479 | For rules built in advanced mode, the Failed Preview rows in the Data Quality rule occurrence show all rows instead of only the failed rows. |
DQC-40297 | In Metadata Command Center, the data observability job fails to run on the SAP ERP catalog source. |
MDP-13484 and MDP-9223 | In Metadata Command Center, when you run a metadata extraction job for SAP SuccessFactors, the job fails to profile sources with multiple tables. For some tables, the job cannot identify certain fields in the source metadata. While for other tables, the job populates associated workflows with the wrong metadata. As a result, some tables do not show profiling in Data Governance and Catalog. |
MDP-12156 | On data collection pages, you cannot modify stakeholders in the Stakeholders tab. The stakeholder propagation job fails intermittently and fails to recover. |
MDP-11856 | Dates displayed with the varchar datatype in data quality preview rows are incorrectly truncated. |
MDP-9869 | Data Quality jobs fail when agent cache is enabled on tables with many rule occurrences. |
SCAN-32283 | For Snowflake metadata extraction, if you enable data observability and metadata extraction, a dynamic table appears twice, as a view and as a table. |
SCAN-29399 | Metadata Command Center fails to extract description for DbtCalculation assets from a dbt source system. |
SCAN-28602 | Lineage expressions are incorrectly extracted with single quotes. |
SCAN-28539 | For Microsoft Azure Data Factory assets, Data Governance and Catalog cannot parse date formats with a forward slash. For example, the date format 2025/10/03 cannot be parsed. After you run a catalog source job for Microsoft Azure Data Factory, there are unidentified assets in its lineage. |
SCAN-28331 | Metadata Command Center stops extracting metadata from objects of a SAS source system if the objects contain an ENDSAS conditional clause. |
SCAN-27229 | For Azure Data Factory metadata extraction, dependent activities without run metadata are not handled correctly, which might cause the scan to fail or show misleading errors during activity conversion in operational metadata context. |
Issue | Description |
|---|---|
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 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-86369 | When you create a search widget grouped by stakeholders, the widget does not display all the assigned stakeholders. |
CDGC-85848 | When you use a search query to find assets with CLAIRE-generated data classifications or assets that are associated with CLAIRE-generated classifications, the search query returns no results. |
CDGC-85846 | If your organization uses the Neo4j graph database, the stakeholder filters do not display all entries. |
CDGC-85540 | When you search columns with the propert or Property keywords in the Contains tab of a data element, you don't see all columns that have 'property' in their names. |
CDGC-84817 | When you use the Create Assets API to create a System asset, the request fails if the System Type attribute uses a label value instead of the corresponding code value. |
CDGC-84787 | You can't view the lineages that are discovered by CLAIRE for a catalog source even if your user profile is assigned the Governance Administrator role. |
CDGC-84605 | When you expand all of the lineage hops to load the lineage graphs, you see that the loading operation takes up to three minutes and fails with an error. |
CDGC-84517 | When running a bulk import to update an asset, the job fails even if you are a stakeholder of the asset. If you do not have the Manage Access privilege, you cannot perform any operation to the asset through a bulk import. |
CDGC-84290 | You cannot save a workflow event in Metadata Command Center if the workflow that you used to create the event contains a task with a name that includes the double-quote (") character. |
CDGC-84103 | When you try to bulk import exported assets, if you do not specify a valid origin value the ingestion fails. |
CDGC-84083 | When you try to import an asset that you had previously exported, Data Governance and Catalog displays an error if the asset has a custom attribute configured for it in Metadata Command Center. This issue occurs if you use the same file to import that asset together with at least one other type of asset. |
CDGC-83993 | After you upgrade Data Governance and Catalog, the Data Elements grid in the Contains tab of an asset displays data elements in a different order than the default sorting. This issue occurs if your administrator has configured a custom layout for the asset in Metadata Command Center and a new predefined column is added to the Data Elements grid during the upgrade. |
CDGC-83946 | When you add a stakeholder to an asset using the same name as a previously deleted stakeholder and then import that asset, the bulk import job fails with the following error message: The entered '[]' stakeholder is invalid. |
CDGC-83650 | When multiple paths of lineage lead to a single endpoint, you see the same endpoint multiple times instead of single endpoint with multiple lineage paths. |
CDGC-83644 | When you tag users in comments on any technical assets, they do not receive email notifications as expected. |
CDGC-83284 | When you use Find to locate an asset in a search-based widget, the operation returns assets that start or end with the keyword of your find. For example, if you use the keyword "work" to locate an asset with the name "Associate Work Email", the operation returns incorrect or no results. |
CDGC-82790 | When you purge a catalog source, assets that were extracted from that catalog source continue to be visible in the Data Governance and Catalog interface. |
CDGC-80873 | When you cancel a Marketplace Propagation job, the job does not transition to the Cancelled state as expected, instead, it remains in its previous state. |
MDP-11322 | If you decline a glossary for a technical asset from the Data Governance and Catalog user interface and you later use the bulk import operation to accept that glossary, the user interface continues to display the glossary as declined for the asset. |
MDP-10819 | When you use a bulk import template to create an asset in the Draft lifecycle and you then modify the asset in the Data Governance and Catalog user interface, the user interface displays your changes inconsistently. |
SCAN-25328 | When you view the lineage for technical assets in a Databricks catalog source in Data Governance and Catalog, deleted or non-existent assets appear in the lineage. |
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-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 the following location: <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-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-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. |
CDGC-83284 | |
CDGC-82222 | Glossaries are not associated to the nested field object types extracted from a Databricks source system after running the glossary association job on the catalog source. |
CDGC-81866 | When you import a rule occurrence using bulk import, the date displayed for the rule occurrence in the catalog is the creation date instead of the date on which the rule occurrence was run. |
CDGC-81649 | If you try to export more than five assets using the export API, the API request fails with an error. |
CDGC-81663 | While configuring data observability for a catalog source, you can enter values 1 and 2 in the Minimum Number of Data Points field even though these values are not allowed. |
CDGC-81276 | If a saved search contains relative date filters such as "last 7 days" or "created today" and the saved search is used in dashboard widgets, then the search is not dynamically updated in the widgets. The widgets continue to display data from the start date when the saved search was created rather than the updated data based on the current date. |
CDGC-81188 | The nested field object types extracted from a Databricks source system are not being tagged with data element classifications after running the data classification job on the catalog source. |
CDGC-81129 | You see an error during bulk import when you import a column after assigning a business name that exists in multiple glossaries. |
CDGC-81095 | Users who don't have permissions to view a data profiling project that contains multiple data quality rule occurrences are able to access the Data Preview option for failed rows on the data quality rule occurrences in the catalog. Instead of receiving a permission error, the users are redirected to the Informatica® Intelligent Data Management Cloud™ (IDMC) landing page. |
CDGC-80870 | The custom layouts that you create for specific asset types in Metadata Command Center are not displayed correctly in Data Governance and Catalog. Custom attributes are prepended to the layout even when they are not selected in the layout. |
CDGC-80400 | Search queries related to data entity classifications still return assets that were previously associated with the data entity classification even though the classification is currently rejected for the asset. |
CDGC-79770 | When you manually add a business name to an asset, the system sets core.description to an empty string. This causes the search query all without description to behave incorrectly. The query fails to return assets with empty descriptions. |
CDGC-79401 | The bulk import job shows an error if you import a data quality rule occurrence with the same values for Target and Threshold fields. |
CDGC-79376 | When you import business terms with the same names using bulk import, Data Governance and Catalog creates the same business term with duplicate external IDs. |
CDGC-77517 | On the New Tasks Inbox page, the Task Details tab of a selected task doesn't display the Assigned To field for the task. Workaround: To view the assignee of a task, expand the task. The task page displays the Assigned To field for the task. |
CDGC-76602 | The bulk import template that you download from Data Governance and Catalog displays disabled stakeholder roles. |
CDGC-75694 | When you run a catalog source with the glossary association Auto-acceptance option enabled, the audit history for the assets in the catalog source shows the Changed By user as Deleted. |
SCAN-25328 | In Data Governance and Catalog, when you view the lineage for technical assets, deleted or non-existent assets appear in the lineage. |
SCAN-20968 | The catalog source run for a Databricks source system creates duplicate assets in Data Governance and Catalog. |
SCAN-19980 | If you run a data observability job for a catalog source and cancel the job before completion, Metadata Command Center deletes the catalog source. |
SCAN-19958 | You cannot view lineage for the DocumentReport assets from the MicroStrategy source system. |
SCAN-18601 | You cannot view the lineage for the Microsoft Azure Data Factory Pipeline assets if structured parameters with functions are used in the Dataset assets. |
Issue | Description |
|---|---|
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-2585 | When creating a data filter rule, using the “Any of” operator results in NULL values being filtered out as well as the intended value. |
CDAM-1242 | If a user has changed the columns in a data source, you must re-run catalog extraction of that data source in Metadata Command Center. Otherwise NULL values for all target columns can result when you run a mapping with that data source in Data Integration. |
CDGC-78967 CDGC-76996 MDP-6191 | Bulk import fails to correctly import custom attributes of assets that have a multiselect drop-down, if a value of the attribute has one or more commas in it. Data Governance and Catalog separates the value with the commas, rather than considering the value as a whole. |
CDGC-78854 | In Data Governance and Catalog, when you export an asset that contains a custom attribute of the dropdown list data type, the exported file contains incorrect values of the dropdown list. This issue occurs if you create the custom attribute in Metadata Command Center and then modify the dropdown list values. After this error occurs, if you import a file with the values you want for the custom attribute, the import fails. |
CDGC-78707 | If you run a saved search that includes @group:<group name> to specify a user group as a stakeholder, the search fails and does not show results. |
CDGC-75987 | If you update a data quality rule occurrence using a bulk import template, the import job takes a long time to complete. |
CDGC-75922 | If you create a data quality rule occurrence that uses a rule specification with multiple input ports, and if you use the Data Quality Rule Occurrence bulk import sheet to update the stakeholder of this rule occurrence, a secondary data element input port shows empty when you open this rule occurrence in Data Governance and Catalog after the bulk import. |
CDGC-75689 | In Data Profiling, if you run a profiling task with multiple rule specifications on a table, and if you modify the data in the table such that the rule occurrence shows a different threshold result, you do not receive an email notification. For example, consider a table on which two rule specifications are run. When the rules are run in Data Profiling, the first rule results in a 'Good' score while the second rule results in a 'Not Acceptable' score. Now, if you modify the contents of the table such that both the first and second rule results in a 'Good' score, you do not receive an email notification. |
CDGC-75674 | If you add a special character in the definition of a Business Term glossary asset and export the asset to a .csv file using the search API, you might get unexpected results. |
CDGC-75622 | An error message appears if a user who can access a technical asset in Data Governance and Catalog with the Export privilege in Administrator attempts to export the technical asset from the interface. |
CDGC-75607 | The export job for a business asset fails for a user even though the user has the asset access permissions granted through access policies but the Do Not Use - View Business Asset privilege is disabled in Administrator. |
CDGC-75437 | If you attempt to delete Business Terms, Data Governance and Catalog fails to delete all assets and shows the OBJECT_HAS_OUTGOING_PARENT_CHILD_RELATIONSHIP error message. |
CDGC-74664 | You can associate a data profiling run object to a data quality rule occurrence even if your user role does not have update privilege for rule occurrences. |
CDGC-67206 | If you export dashboard objects from a Google Looker catalog source, the exported file does not include dashboard information. |
CDGC-64476 | On the History tab of the ticket page, the Changed By field displays the name of the approver of the change instead of the name of the latest user that performed the action on the asset. |
Issue | Description |
|---|---|
CDGC-75109 | When you perform a global search for stakeholder roles using the query all with stakeholder role @role:, the search suggests user roles instead of stakeholder roles. |
CDGC-75078 | When you associate glossaries with data classifications in the exported glossary sheet and reimport the file into the catalog, the relationship between the glossary and data classifications is not displayed even though the bulk import job is successful. |
CDGC-75072 | The Adaptive search for the following query fails with an error: business terms related to manual data element |
CDGC-74791 | If a stakeholder role, which is associated with assets through stakeholder role access policies, is disabled in Metadata Command Center, the disabled stakeholder role still appears in the exported file for the assets. |
CDGC-74034 | The Export API job runs for a long time and fails if there's no data to export. |
CDGC-73156 | Date type custom attributes for assets show inconsistent dates for users in different time zones. |
CDGC-73176 | You can use the image icon in the Description field of an asset to upload a PDF. This results in a broken image. |
CDGC-73097 | When you use the bulk import process to associate a technical asset with a business term that was rejected for another technical asset, the bulk import job fails with an error. |
CDGC-71214 | If you modify some fields of a glossary asset and re-import the assets in the catalog, the images in the description of the glossary assets are deleted even if you don't make any changes to the description of the asset. |
SCAN-15498 | Some external tables extracted from the IDMC source system may not display lineage. |
SCAN-13539 | The ForEach activity in the Azure Data Factory catalog source reuses the Copy activity instance for every iteration and causes all source tables to link with all target tables. As a result, the final data lineage appears incorrect because each source table is not linked to its target table. |
SCAN-13233 | Some Microsoft Power BI Reports may not display the source objects in the lineage. |
SCAN-13223 | If you extract metadata from a Microsoft Excel file where some columns are merged, the values in the merged columns appear as separate columns in Data Governance and Catalog. |
Issue | Description |
|---|---|
CDGC-72924 | In the Notifications Settings page, the changes you make to the Notification Category section are not saved. |
CDGC-71989 | When you enter * as a search query and click Catalog Source Name in the Filters pane, the catalog sources appear as blank entries. |
CDGC-71112 | If you export a technical asset and modify the Glossary assets that were associated automatically to the technical asset, the import job for the asset fails or the import job succeeds but your changes are not reflected in the technical asset. |
CDGC-70246 | When you search for an asset and click Catalog Source Name in the Filters pane, the catalog sources appear as blank entries. |
CDGC-69064 | If you extract metadata from a Microsoft Excel file that contains very long texts in the cells, and if you search for a data element from the file in Data Governance and Catalog, the search result shows the long texts as overlapping and garbled characters. |
CDGC-67222 | If an exported file contains a date column and you enter a value in the column so that you can import it back to Data Governance and Catalog, the date column permits you to enter dates only within a supported range. |
CDGC-67061 | If you configure custom branding for your organization, the service interface does not reflect the brand settings you have made. |
CDGC-67058 | If you search for an asset in Informatica QuickLook using the CTRL+Q keyboard shortcut, the search fails or displays a service error. |
CDGC-66652 | If a Project asset has another project as a parent, you cannot remove the parent asset using the bulk import template. |
CDGC-56912 | If the administrator modifies a value for a custom attribute in Metadata Command Center and publishes the change, and if you make an API call to see the details of an asset that includes this custom attribute, the response body does not show the updated value of the attribute. |
MDP-5228 | In a Data Quality Rule Template file, if you specify a measuring method other than Informatica Cloud Data Quality and leave the Technical Rule Reference field blank, the import job fails. |
MDP-4188 | When you use the <baseApiUrl>/data360/search/v1/assets/<assetID> API, the response displays all details of an asset even if you do not have the required permissions. |
SCAN-10893 | If you create a Power Query report in Microsoft Power BI, the reports do not appear in the lineage for the data set. |