Daily Notification of Refresh Conflicts
Overview
When a data source is refreshed, refresh conflicts may arise as a result of the refresh.
There is not any out of the box functionality to notify of the refresh conflicts, an owner would need to navigate to their schemas and expose the ‘Refresh Conflicts’ column in order to see them after each refresh to see if any actions are necessary.
The existence of the refresh conflicts will prevent the refresh from running properly until the refresh conflict has been resolved.
This workflow runs on a daily basis, preset to 3AM on the server time, and it will scan the environment for the existence of Refresh Conflict attributes, the asset it is on and gather the value of the Refresh Conflict and also the Owner (role can be configured in variables).
The workflow then generates an email to those users to inform them of the assets with refresh conflicts found.
Media
More details
Release Notes
Release Notes – v0.1.1: Fixed bug when there are no refresh conflicts
Compatibility
- Collibra Data Intelligence On-Prem
- Collibra Data Intelligence Cloud
Dependency
- Collibra API v2
License and Usage Requirements
Release History
Release Notes
v0.1 – Initial Release
Compatibility
- Collibra Data Intelligence Cloud
- Collibra Data Intelligence On-Prem
Dependency
- Collibra API v2
License and Usage Requirements
See existing Q&A in the Data Citizens Community
Browse discussions with customers who also use this app.
Start a New Topic in the Data Citizens Community
Collibra-hosted discussions will connect you to other customers who use this app.
Pavan Kumar
This doesn’t work with v5.7.6 version. Please let us know. Also the email doesn’t have details about which Domain, community the conflict asset belong to.
Luca Spoo
Doesn’t work with version 2021.11. Please update.