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-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 Cloud Services 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-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 Informatica Intelligent Cloud Services 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. |
Issue | Description |
---|---|
CDGC-69195 | The Norwegian characters do not appear correctly when you view the preview of failed rows for a data quality rule occurrence on a Windows agent. |
CDGC-68428 | The catalog does not display all the calculation view assets extracted from SAP HANA catalog sources. |
MDP-4265 | The data quality rule occurrence Run Now option takes a long time to execute when the catalog source contains 2.5 million assets. |
SCAN-8742 | When you run a Microsoft Azure Data Factory catalog source job in Metadata Command Center, the job succeeds but the lineage is not visible in Data Governance and Catalog due to unsupported parameters. |
Issue | Description |
---|---|
MDP-4269 | When you use the bulk import operation to associate a technical data element to multiple glossaries and assign a business name and description, the glossaries are not associated and the business name or description is not assigned to the technical data element. |
Issue | Description |
---|---|
CDGC-63399 | If you import a technical data element sheet that contains duplicate business data set names, the data elements of the duplicate data sets get associated with each other. This results in an incorrect hierarchy of the data elements. |
CDGC-63868 | When you perform case insensitive connection assignment for catalog sources, the unmatched reference objects display incorrect hierarchy. |
CDGC-64320 | When you export search results containing Informatica Data Management Cloud assets, the exported file does not include those assets. |
CDGC-65744 | The preview job for failed rows for a Snowflake catalog source displays truncated results for the timestamp field. |
SCAN-7806 | When you extract metadata from an Informatica Intelligent Could Services catalog source, the mappings and mapping tasks show incorrect hierarchy if they are are located in different projects. |
SCAN-8714 | Microsoft Power BI data sets in the catalog may display duplicate entries for fields. This issue occurs when the Microsoft Power BI columns contain a period in their names. |
SCAN-10024 | When you extract metadata from a Google Looker catalog source, the value for the Google Looker system attribute Native ID is not displayed in the catalog. |
SCAN-10216 | You cannot view complete data lineage for the assets in the IBM Cognos catalog source if the MySQL queries in the IBM Cognos source system are converted to UTF-8. |
Issue | Description |
---|---|
MDP-3284 | The data profiling job for Amazon Redshift source systems completes successfully in Metadata Command Center but the profiling results for views are not visible in Data Governance and Catalog. |
CDGC-64596 | The bulk import job for technical assets fails if the Lifecycle field in the bulk import file is left blank. |
CDGC-64834 | When a custom workflow for an asset is configured with a human task that has only one action, then the workflow stakeholders cannot perform ticket-level operations for those assets in Data Governance and Catalog. |
CDGC-65314 | When the data quality rule is run successfully, you cannot preview the failed rows for the rule occurrence if your Data Governance and Catalog tenant is on the April 2024 version and the Metadata Platform Service is on the May 2024 version. |
CDGC-65368 | You cannot delete a schedule for a data quality rule occurrence in Administrator even if you delete the frequency attached to the rule occurrence in Data Governance and Catalog. |
CDGC-65799 | When you update the description of a data set by pasting text from external applications, the description displays junk HTML codes when you view it from the widget on the Home page. |
CDGC-64958 | When you enter a default date for a custom attribute in Metadata Command Center, the default date changes as per the browser timezone when you create an asset in Data Governance and Catalog. |
Issue | Description |
---|---|
SCAN-466 | The lineage is not extracted properly from the QlikSense Cloud source system if the alias name of the column is passed in the query. |
SCAN-1318 | If Metadata Command Center extracts metadata for a Tableau dashboard that contains commas in its name, multiple Tableau dashboard assets are created in Data Governance and Catalog for a single dashboard asset. |
SCAN-3138 | If a QlikSense source system that contains tables with the same names inside different projects, the lineage is not extracted properly in Data Governance and Catalog. |
CDGC-54878 | You cannot create or delete a stakeholder for data quality rule occurrences using the Stakeholder template for bulk import. |
CDGC-56161 CDGC-60093 | When you search using the following queries, the search times out:
|
CDGC-61944 | If you create duplicate relationships between assets in the relationship sheet, the bulk import job fails without an error. |
CDGC-62642 | The hover text for the catalog source types in the search filter displays a JavaScript error. |
CDGC-62941 | The bulk import job for assets fail if the import file contains Japanese characters. |