Control D&B hierarchy behavior during enrichment
Learn about the monitoring headers that control how D&B hierarchy relationships are created, updated, or skipped.
Overview
Reltio supports multiple enrichment APIs that process data from Dun & Bradstreet (D&B), including background monitoring, batch enrichment jobs, and on-demand API sync requests. These operations support optional headers/parameters that control how D&B hierarchy relationships (such as ORG-ORG and ORG-LOC) are created, skipped, or replaced during enrichment.ORG-ORG=configuration/relationTypes/DnBHierarchy.ORG-LOC=configuration/relationTypes/HasAddress
Supported Headers
Reltio-Build-Relations-Mode
This header controls which hierarchy relations are created or skipped during a D&B monitoring job.
| Value | Description |
|---|---|
FULL | Default behavior. Creates missing ORG-ORG and ORG-LOC relations. Removes residuals. |
ADD_ONLY | Adds missing ORG-ORG and ORG-LOC relations. Does not delete existing ones. |
SKIP_ORG_ORG | Skips all ORG-ORG creation. Still creates ORG-LOC relations. |
SKIP_ORG_LOC | Skips all ORG-LOC creation. Still creates ORG-ORG relations. |
DIFF | Read-only mode. No writes. Returns a forecast of the relationship that would be created/removed. |
OFF | Disables all hierarchy operations. No reads, writes, or forecasts. |
Reltio-Hierarchy-Write-Policy
This header defines how upward hierarchy (ORG-ORG) relationships behave when pre-existing parent links are detected.
| Value | Description |
|---|---|
DEFAULT | Standard policy. Doesn't override existing parent links. |
OVR_UPW | Creates a new upward hierarchy according to the DnB hierarchy specified in the corporate linkage from the target organization to the global ultimate organization. This mimics legacy overrideUpwHierarchy=true. |
OVR_UPW_FORCE | Enables targeted replacement of existing ORG-ORG parent relationships (known as the 134-fix). When an existing parent link is detected, it is explicitly removed and replaced with the new one provided by D&B — regardless of whether the node is considered "new." This applies only when mode=FULL, ADD_ONLY, or DIFF. Note: Use this policy to enforce the most accurate hierarchy based on the latest D&B linkage, especially when cleanup of outdated parent links is required. |
Default behavior: DEFAULT (if header is not passed)
Usage Notes
These headers apply to any enrichment API that creates or updates hierarchy relations using data from the D&B connector.
The following table summarizes the expected system behavior for each combination of Reltio-Build-Relations-Mode and Reltio-Hierarchy-Write-Policy.
| case Name | case code | overrideUpw Hierarchy | Reltio-Build-Relations-Mode | Reltio-Hierarchy-Write-Policy | mode/policy spec | Relation Behavior | Code/Notes |
|---|---|---|---|---|---|---|---|
|
Legacy 1 (both headers NULL) |
[legacy 1] |
TRUE |
NULL |
NULL |
FULL / OVR_UPW | ORG-ORG add+remove; ORG-LOC add; override relaxes canCreate; no 134-fix | mode=FULL, policy=OVR_UPW; ORG-LOC no de-dup |
|
Legacy 2 (both headers NULL) |
[legace 2] |
FALSE |
NULL |
NULL |
FULL / DEFAULT | ORG-ORG add+remove; ORG-LOC add; no 134-fix | mode=FULL, policy=DEFAULT |
|
Explicit 1 |
[explicit 1] |
FALSE |
FULL |
DEFAULT |
FULL / DEFAULT | ORG-ORG add+remove; ORG-LOC add | Baseline FULL |
|
Explicit 2 |
[explicit 2] |
FALSE |
FULL |
OVR_UPW |
FULL / OVR_UPW | Like explicit 1 + relaxed canCreate | No 134-fix |
|
Explicit 3 |
[explicit 3] |
FALSE |
FULL |
OVR_UPW_FORCE |
FULL / OVR_UPW_FORCE | Like explicit 2 + 134-fix (replace) | Targeted replace |
|
Explicit 4 |
[explicit 4] |
FALSE |
ADD_ONLY |
DEFAULT |
ADD_ONLY / DEFAULT | ORG-ORG add-only; ORG-LOC add | Residuals stay |
|
Explicit 5 |
[explicit 5] |
FALSE |
ADD_ONLY |
OVR_UPW |
ADD_ONLY / OVR_UPW | Like explicit 4 + relaxed canCreate | Residuals stay |
|
Explicit 6 |
[explicit 6] |
FALSE |
ADD_ONLY |
OVR_UPW_FORCE |
ADD_ONLY / OVR_UPW_FORCE | Add-only; 134-fix on conflict | Residuals still stay |
|
Explicit 7 |
[explicit 7] |
FALSE |
SKIP_ORG_ORG |
ANY |
SKIP_ORG_ORG / ANY | Skip ORG-ORG; build ORG-LOC | ORG-LOC no de-dup |
|
Explicit 8 |
[explicit 8] |
FALSE |
SKIP_ORG_LOC |
ANY |
SKIP_ORG_LOC / ANY | Skip ORG-LOC; ORG-ORG add-only | 134-fix only if FORCE |
|
Explicit 9 |
[explicit 9] |
FALSE |
DIFF |
DEFAULT |
DIFF / DEFAULT | Forecast only; ORG-LOC forCreate=all | No writes |
|
Explicit 10 |
[explicit 10] |
FALSE |
DIFF |
OVR_UPW |
DIFF / OVR_UPW | Like explicit 9 | Forecast with override |
|
Explicit 11 |
[explicit 11] |
FALSE |
DIFF |
OVR_UPW_FORCE |
DIFF / OVR_UPW_FORCE | Like explicit 10 + replaced forecast | forecastReplacements |
|
Explicit 12 |
[explicit 12] |
FALSE |
OFF |
ANY |
OFF / ANY | Full stop | Empty result |
|
Latent 1 |
[latent 1] |
TRUE |
ADD_ONLY |
NULL |
ADD_ONLY / DEFAULT | See explicit 4 | Legacy policy ignored |
|
Latent 2 |
[latent 2] |
TRUE |
SKIP_ORG_ORG |
OVR_UPW_FORCE |
SKIP_ORG_ORG / OVR_UPW_FORCE | See explicit 7 | FORCE irrelevant |
|
Latent 3 |
[latent 3] |
TRUE |
OFF |
NULL |
OFF / DEFAULT | Full stop; Locations in input → SKIP_LR_PROHIBIT | Guard in ctor |
|
Latent 4 |
[latent 4] |
FALSE |
NULL |
OVR_UPW_FORCE |
FULL / DEFAULT | Expected FORCE, actually ignored (no mode) | Behaves as legacy FULL/DEFAULT |