Why the HCO address shows ov: false while the linked Location shows ov: true

Question

Why the HCO address shows ov: false while the linked Location shows ov: true

Answer

For HCO 00tsSnd, the address tied to Location 0515hIN is reference Address/03uy7pJ. In the HCO payload, that entire address reference is marked ov: false, so every projected child attribute under that reference also appears as ov: false.

However, when Location 0515hIN is viewed directly, the same address elements such as AddressLine1, City, StateProvince, Zip, and Country are present as ov: true on the standalone Location record.

Why this happens

In Reltio, an address on an HCO/HCP that points to a Location is a reference attribute. Reference attributes can point to another entity, but the OV shown on the parent record is still determined by the reference instance on that parent, not just by the standalone referenced entity’s OV values. Reltio documents reference attributes as non-atomic attributes that reference another entity, such as an Address referencing a Location.

In this case, the HCO reference 03uy7pJ is an end-dated / inactive reference. Its refRelation crosswalk shows a deleteDate of 2025-07-01 for the InQuicker HasAddress relation. Per Reltio documentation, when a crosswalk is end-dated by setting deleteDate, that crosswalk’s contribution is inactivated, becomes ov=false, and is not displayed as an active contribution in Hub. Reltio also states that end-dated crosswalks are immediately ignored for OV purposes.

What this means

This does not indicate that Location OV failed to sync to the HCO.

Instead, it means:

• The standalone Location 0515hIN is healthy and has the expected winning values.
• The HCO is carrying a non-winning/end-dated HasAddress reference via Address/03uy7pJ.
• Because that HCO reference is inactive/non-winning, the projected address values under that specific HCO address reference correctly appear as ov: false.

There is also a strong indicator of this in the HCO itself: HCO 00tsSnd has another address reference, 0C0FnT4, that is marked ov: true. That means 03uy7pJ is not the winning address reference in the HCO view.

You may see a difference between:

• the standalone Location record, where the Location’s own winning address values are ov: true, and
• the HCO/HCP projected address, where a specific reference instance can be ov: false if that relation/reference is end-dated or non-winning.

This is expected when the HCO is holding an inactive or non-winning reference to the Location.

Recommended next steps

If the business expects Location 0515hIN to be the active winning address on HCO 00tsSnd, please review the HasAddress relation and its crosswalk state for reference 03uy7pJ.

If the reference was end-dated unintentionally, the deleteDate can be cleared through API. Reltio Support documents that removing a crosswalk deleteDate is supported via API, not through the UI.

If relation updates are used to restore the reference, Reltio also notes that relation updates may require options=partialOverride to avoid unintentionally removing relation attributes during the update.

Conclusion

The discrepancy is caused by the state of the HCO’s address reference, not by a problem with the Location record itself. The Location has valid winning values, but the HCO is referencing that Location through an end-dated/non-winning HasAddress relation, so the HCO correctly returns that projected address as non-OV.