Collibra Integration
This article covers what is specific to Collibra. How connections, mappings, Push, Pull, Status and the run report work is described in Data Governance Integrations — read that first.
What you need from Collibra
| Requirement | Where to set it |
|---|---|
| A Collibra service account (username and password) | Collibra, by a Collibra admin |
| Your Collibra URL | Your Collibra instance |
| A target Community and Domain | Your Collibra environment |
| The attributes you want to populate already exist in Collibra | Your Collibra environment |
Use a service account, not a person's login. The connection is account-wide, so a personal login would tie every user's pushes to one person's credentials.
Connecting
On the Collibra card at Dashboard → Integrations → Data Governance, the connection form asks for:
- Username and Password of the service account
- Collibra URL — the path to your Collibra instance
The Save button becomes available once all three fields are filled.
Mapping container: Community and Domain
A Collibra mapping targets a Domain inside a Community.
On the mapping's Settings tab, select a Community first; the Domain list is then filtered to domains within it.
At minimum, a Domain and one attribute must be defined for a mapping to work.
Attributes
The Collibra column of the Attribute mapping tab offers the attribute types available in your Collibra instance.
Dropdown options. When you push a dropdown or multi-select value that the Collibra attribute does not offer yet, SqlDBM adds it to the attribute. Options are only ever added, never removed.
Objects
Objects are matched to Collibra assets by fully qualified name. If an object is not matched, check that it has the same name and the same schema in both Collibra and SqlDBM.
Push to Collibra
The push confirmation shows the Target domain as Community / Domain:
A push runs as an import job in Collibra, which SqlDBM polls to completion. While it runs, Current run in the Status popup shows a percentage complete and an object count (for example, 123 out of 260 objects). Select Cancel to stop the job.
Push size. A Collibra push has to fit in one request; background batching is not available for Collibra. An oversized push is refused with This mapping holds more values than one push to the external system can carry, so nothing was sent. — push fewer objects or fields at a time.
Pull from Collibra
Pull follows the shared flow with no Collibra-specific limits or warnings beyond those in Data Governance Integrations.
Troubleshooting
| You see | It means | What to do |
|---|---|---|
| A community or domain is missing from the picker | The service account cannot see it, or the lists are stale | Select Refresh. If it is still missing, confirm it exists in Collibra and that the service account has access to the community |
| An object is not matched on the Objects tab | The fully qualified name differs | Check the object has the same name and schema on both sides |
| This mapping holds more values than one push to the external system can carry, so nothing was sent. | The push does not fit in one request | Push fewer objects or fields at a time |
| The import job shows Error | The Collibra job failed | Open the Report. Invalid credentials and attributes that do not exist in the target domain are the usual causes |