Known issues
The following is a non-exhaustive list of issues that we have encountered in this release. We intend to fix these issues as quickly as possible.
|
Ticket |
Issue |
Found in |
Fixed in |
|---|---|---|---|
| Not applicable |
On the Homepage editor, the URL field on the Add a Quick Link card does not accept a complex link, for example, https://productresources.collibra.com/docs/collibra/latest/Content/DGCSettings/ServicesConfiguration/to_services-configuration.htm. Note To avoid this issue, consider adding a simple link in the URL field, for example, https://productresources.collibra.com. |
2023.02 | 2023.03 |
| Not applicable | In Data Marketplace, when you use the out-of-the-box Data Marketplace scope without making any changes to it, Data Marketplace shows an error message "We could not load this widget." in the Data Marketplace landing page. To solve the issue, go to Settings → Data Marketplace → Scope, change the scope and save your changes. |
2023.02 | 2023.03 |
| Not applicable | In the global Search field, if you enter a word with a special character, for example, sales % or search %, the following message is shown: Sorry, something went wrong. Try to refresh the page. | 2023.02 | 2023.05 |
| Not applicable | When you use technical lineage via Edge and a proxy is required to connect to your data source, the authentication information is required to configure the forward proxy on Edge. | 2023.02 | 2023.05 |
| Not applicable | When you create technical lineage for Snowflake by using the SQL-API ingestion method, you can use an optimized SQL query to reduce processing time significantly in Snowflake. The SQL query will be included in the out-of-box version of the lineage harvester, starting from 2023.05. To use this query before the release of the lineage harvester version 2023.05, contact Collibra support. | 2023.02 | 2023.05 |
| Not applicable | Data Marketplace stops working if you try to save a relation index that contains a special character, such as /, ?, @, [, }, <, >, in the name or in one of the relations. | 2023.02 | To be defined |
| Not applicable | When exporting the CSV of the user table the Required license column will use the term AUTHOR for Standard license and CONSUMER for Read-only license. | 2023.02 | To be defined |
| Not applicable |
After Usage Analytics is deployed, the following error message may be temporarily shown in place of the Usage Analytics dashboard: Your configuration restricts query requests to only be served from pre-aggregations, and required pre-aggregation partitions were not built yet. Please make sure your refresh worker is configured correctly and running. This message disappears and the Usage Analytics dashboard is shown approximately 6 hours after the deployment. |
2023.02 | To be defined |
| Not applicable |
If you use the Google Translate extension to translate Data Marketplace, Homepage, or Usage Analytics, the application may stop responding. Note To continue working without Google translation, refresh the page. |
2023.02 | This is a Google Translate extension issue. |
| Not applicable |
In Protect, when creating a data access rule, if, after selecting an asset that contains masking and row filtering data, you apply masking and row filtering to the asset, remove the asset, and then select an asset that does not contain masking and row filtering data, the data from the previously selected asset is still retained and you can save the rule. Note Although the rule is saved, the synchronization status fails, as expected. |
2022.11 | 2023.05 |
| Not applicable | When creating a data access rule, depending on the number of assets, the asset types, or the prescriptive paths, Protect may show all the data categories or data classifications for masking or row-filtering, including those that are not applicable to the selected assets. | 2022.11 | To be defined |
| Not applicable | In Data Marketplace, it is possible that fewer or more search results appear in the All filter tab compared to other filter tabs. This is because the out-of-the-box filter tabs, Tables, Data Sets and Reports, are not impacted by the Data Marketplace scope configuration. Administrators can configure the available filter tabs. | 2022.11 | To be defined |
| 101776, 102145 | To fix the Data Marketplace issue "Request failed with status code 503", Data Marketplace no longer shows user avatars in the Responsibilities tab in asset previews. | 2022.11 | To be defined |
| Not applicable | The REST Import API returns an error when processing assets that have relations and the name of a related asset contains a comma. | 2022.11 | To be defined |
| Not applicable | The new licensing terms, Standard and Read-only are being overwritten by the old terms, Author and Consumer in some instance.
This happens when language customizations have been made to the interface text. You can see how to reset the interface text in our documentation. |
2022.11 | Not applicable |
| Not applicable |
From version 2022.11 onwards, Collibra takes the default language of your browser into account to select the interface text language of some sections. Collibra now also has translations of some interface text available out of the box. Consequently, you can no longer edit that interface text, nor translate it into unsupported languages. This includes the interface text of Usage Analytics, Data Marketplace and the Homepage. This means that the language of some user interface text may not always match the language settings in your user profile. |
2022.11 | Not applicable |
| Not applicable | Within 24 hours after Usage Analytics is enabled, if you do not sign in to Collibra Data Intelligence Cloud or visit an asset, empty cards are shown on the Usage Analytics dashboard. | 2022.11 | Not applicable |
| Not applicable | Collibra doesn't work in Safari, and Collibra Everywhere doesn't work on devices running on iOS. | 2022.09 | 2022.09.1 |
| 87158 | If a network issue occurs while registering a JDBC data source via Jobserver, Collibra again retries repeatable network requests. | 2022.09 | 2022.09.1 |
| If you are using the Databricks connection driver version 2.6.25, you cannot use partial scan when profiling via Edge. | 2022.05 | 2022.08 | |
| If you do not fill in the optional fields, Access Key ID and Secret Access Key, in the S3 File System Connection Details page, an incorrect error message appears:
"Jobserver no longer available. Select another Jobserver."
To prevent this error, fill in the Access Key ID and Secret Access Key fields. |
2022.05 | 2022.06.1 | |
| 81272, 81501, 81592, 81612, 81727, 81794, 82017, 82327, 82418, 82630, 83593, 83601, 83922, 83970, 84768, 84828, 85060, 85470, 85572 | You cannot move assets between domains in different subcommunities that have the same parent community if the permission is only set on the parent community. As a workaround, ensure that you also have the necessary permission on the subcommunity level. | 2022.01, 2022.02, 2022.03 | 2022.04 |
| 79928 |
Normally, you only see relations if you have view permissions for the head and the tail asset of the relation. If you do not have view permissions for an asset, you don't see the relations to that asset, for example in views or on the asset page of the related assets. However, the History tab page of asset pages mentions all relations, even if you don't have view permissions for the related asset. |
2022.02 | Won't be fixed |
| Time-based review rules that were configured to trigger Time based asset review workflows on an annual basis, did not start at the beginning of the calendar year 2022. We strongly recommend that you review any Time-based Review Rule assets you have configured, to see if there are target assets that should be reviewed. Read more. | 2022.01 | planned for 2022.03 but subject to changes | |
| 30943, 36378 | A data source ingestion fails if a foreign key has the same name as a table. | 5.5 | Won't be fixed |
Common issues
-
The Collibra Data Intelligence Cloud 5.7.2-13 release fixed performance issues with the Escalation Process workflow.
To take advantage of the improvements, you must deploy the new version of the Escalation Process workflow in your Collibra 5.7.2-13 or newer.
Note If you are using a modified Escalation Process workflow, you must port your changes to the new workflow.
Warning The new Escalation Process workflow is only valid for Collibra 5.7.2-13 or newer.
- Workflows with different values for the
processRefattribute of theparticipanttag and theidattribute of theprocesstag are not working in Collibra 5.6.0 or newer, despite having worked in older versions. These workflows have invalid BPMN files that cause ajava.lang.NullPointerExceptionerror, visible in the Collibra Console logs. For more details, see the troubleshooting section.