Do we always need to run DnB Enrichment to refresh the hierarchy and company status?

Question

Do we always need to run DnB Enrichment to refresh the hierarchy and company status? Will DnB Monitoring not do it? Or is it because of the source table that it is not happening?

Answer

Two types of D&B data flows.
 

• D&B Enrichment (Get Company Details / Get Family Tree)
  • On-demand or batch job.
  • Writes into the D&B Enrichment crosswalk (the one you see with ID like R342633433, Source System Name: Dun & Bradstreet, SourceTable=PureParty).
  • Fills attributes like DUNS Hierarchy (Global Ultimate, Domestic Ultimate, Parent orgs, etc.).
  • This is where the left-panel “DUNS Hierarchy” values are coming from in your screenshot.
• D&B Monitoring
  • A subscription feed pushes updates whenever D&B makes a change.
  • Writes into a separate Monitoring crosswalk (different source ID).
  • Typically covers events like status changes, address updates, and financials.
  • By default, it does not overwrite hierarchy attributes unless the monitoring feed delivers hierarchy fields and your mapping explicitly includes them.

Why did your monitoring not update the hierarchy?
 

• You mentioned the seed file had no parent, GU, or DU. That means the monitoring payload for this entity didn’t include any corporate linkage.
• With partialOverride=true, missing attributes in the monitoring payload do not overwrite the existing hierarchy values set earlier through enrichment.
• Therefore, the outdated hierarchy from the enrichment crosswalk (see the Dec 5, 2024 snapshot) remains visible.

Monitoring did run, but due to the absence of a linkage section and the partialOverride setting, it failed to nullify or remove the hierarchy values.
 

Do you always need enrichment to refresh hierarchy & company status?
 

• Hierarchy (parent/ultimate/child info) → comes from enrichment (Get Company Details / Get Family Tree).
  • Monitoring does not guarantee hierarchy refresh, unless your subscription is configured to push linkage events.
• Company status, name, address, financials, etc. → can be updated by monitoring, because those events are included in the monitoring feed.

In practice:

• To refresh hierarchy, yes, you still need to re-run D&B Enrichment.
• To keep the company status and basic fields fresh, monitoring is enough.
• The reason it looks inconsistent in your case is that monitoring ran, but did not touch the hierarchy, leaving the stale enrichment hierarchy in place.

SourceTable confusion
 

• You’re correct that the D&B connector itself does not use SourceTable in mapping.
• What you’re seeing (PureParty) is a label carried on that enrichment crosswalk. It doesn’t change the behavior here. The key is the crosswalk type (Enrichment vs Monitoring).

Summary
 

• Will D&B Monitoring update the DUNS Hierarchy?
  → Not always. Only if the monitoring payload includes corporate linkage and your mapping covers it. In your case, the monitoring payload was empty, so the hierarchy wasn’t updated.
• Do we always need to run D&B Enrichment to refresh hierarchy and company status?
  → For hierarchy: Yes.
  → For company status: Not necessarily — monitoring can update that if it’s included in the monitoring feed.
• Is this because of the SourceTable?
  → No. SourceTable is just metadata on the crosswalk. The key is determining which crosswalk type the update originates from (Enrichment vs Monitoring).