Filtered survivorship mappings on another attribute match on non-OV values: explainOv diagnosis and fixes (data cleanup, OtherAttributeWinnerCrosswalk, SRC_SYS)

Question

We have two survivorship mappings for the same attribute. Each is conditioned on a different value of another attribute (a flag with the values Yes and No). On a profile where the flag’s operational value (OV) is “No”, the result looks like the “Yes” mapping was applied. The source we expected to win on recency does not survive. Why?

Answer

Survivorship filters evaluate all values of the referenced attribute, not only the OV.

Filters are applied before OV is calculated, so the filter condition cannot tell which value will end up as the OV. If the referenced attribute holds both “Yes” (from one source) and “No” (from another), both equals "Yes" and equals "No" evaluate to true, and both filtered mappings match. The condition does not require the matching value to be the OV, or to come from the same crosswalk as the value being calculated.

Example

Example configuration (attribute and source names are generic):

 
json
[
  {
    "attribute": "configuration/entityTypes/Individual/attributes/Status",
    "filter": {
      "equals": [
        { "uri": "configuration/entityTypes/Individual/attributes/Flag", "value": "Yes" }
      ]
    },
    "survivorshipStrategy": "LUD",
    "sourcesForOv": [ "configuration/sources/SOURCE_A" ],
    "fallbackUsingCriteria": "ZERO_OR_MORE_THAN_ONE",
    "fallbackStrategies": [
      {
        "attribute": "configuration/entityTypes/Individual/attributes/Status",
        "survivorshipStrategy": "LUD",
        "sourcesForOv": [ "configuration/sources/SOURCE_C", "configuration/sources/SOURCE_D" ],
        "fallbackUsingCriteria": "ZERO_OR_MORE_THAN_ONE",
        "fallbackStrategies": [
          {
            "attribute": "configuration/entityTypes/Individual/attributes/Status",
            "survivorshipStrategy": "LUD",
            "sourcesForOv": [ "configuration/sources/SOURCE_B" ]
          }
        ]
      }
    ]
  },
  {
    "attribute": "configuration/entityTypes/Individual/attributes/Status",
    "filter": {
      "equals": [
        { "uri": "configuration/entityTypes/Individual/attributes/Flag", "value": "No" }
      ]
    },
    "survivorshipStrategy": "LUD",
    "sourcesForOv": [
      "configuration/sources/SOURCE_B",
      "configuration/sources/SOURCE_C",
      "configuration/sources/SOURCE_D"
    ]
  }
]

On the profile:

  • Flag = “No” from SOURCE_B (OV) and Flag = “Yes” from SOURCE_A (non-OV).
  • Status = “X” from SOURCE_C and SOURCE_D, and Status = “Y” from SOURCE_B, which is the most recent update.

Both filters match. The first mapping’s chain (SOURCE_A tier, then the SOURCE_C/SOURCE_D tier) can resolve a single winner before it ever reaches the SOURCE_B tier. SOURCE_B’s value then shows as not participating, even though Flag = “No” and SOURCE_B is the most recent.

How to confirm: use options=explainOv

 
GET /entities/{entityUri}?options=explainOv

In the ovDetails of the attribute, check:

 
json
"ovDetails": {
  "matchedFilters": [
    { "equals": [ { "uri": ".../attributes/Flag", "value": "Yes" } ] },
    { "equals": [ { "uri": ".../attributes/Flag", "value": "No" } ] }
  ],
  "unmatchedFilters": [],
  "appliedSurvivorshipRules": {
    "appliedSurvivorshipRule": "LUD",
    "sourcesForOv": [ "configuration/sources/SOURCE_A" ],
    "fallbacks": [ { "appliedSurvivorshipRule": "LUD", "...": "..." } ]
  },
  "participationStatus": "strategy"
}

Signs that this is the issue:

  • Both filters appear in matchedFilters, and unmatchedFilters is empty.
  • The applied chain belongs to only one matching mapping.
  • The value you expected to win shows "participationStatus": "not participating" and "appliedSurvivorshipRule": "N/A".

Note that explainOv may report only one mapping’s chain even when several mappings matched, so compare the filters in matchedFilters against your mappings.

Resolution options

Option 1: Make only one filter match (data fix)

Remove the obsolete or conflicting filter attribute value from the contributing source, or correct it upstream. When only “No” exists on the profile, only the “No” filter matches.

  • Remove the specific attribute value. Do not end-date the whole crosswalk unless you intend to remove everything that source contributes.
  • Optionally, set discardIgnoredDeletedValues in the filter so that ignored values and values on end-dated crosswalks are excluded from the filter check. It does not exclude active values.
 
json
"filter": {
  "discardIgnoredDeletedValues": true,
  "equals": [
    { "uri": "configuration/entityTypes/Individual/attributes/Flag", "value": "No" }
  ]
}

Option 2: Follow the source that wins the other attribute (OtherAttributeWinnerCrosswalk)

Use this if the intent is “whichever source wins the flag should also determine the value.” The strategy takes the winner crosswalks of the primary attribute and selects the values they provide. Non-OV values of the flag no longer influence the result. Add a fallback in case the winning source contributes no value:

 
json
{
  "attribute": "configuration/entityTypes/Individual/attributes/Status",
  "survivorshipStrategy": "OtherAttributeWinnerCrosswalk",
  "primaryAttributeUri": "configuration/entityTypes/Individual/attributes/Flag",
  "fallbackUsingCriteria": "ZERO_OR_MORE_THAN_ONE",
  "fallbackStrategies": [
    {
      "attribute": "configuration/entityTypes/Individual/attributes/Status",
      "survivorshipStrategy": "LUD"
    }
  ]
}

This changes the rule. The value now follows the flag's winning source by recency, not a fixed source list.

Option 3: Use a fixed source hierarchy (SRC_SYS)

If you have an established order of source trust, define a single mapping with no filter:

 
json
{
  "attribute": "configuration/entityTypes/Individual/attributes/Status",
  "survivorshipStrategy": "SRC_SYS",
  "sourcesUriOrder": [
    "configuration/sources/SOURCE_B",
    "configuration/sources/SOURCE_A",
    "configuration/sources/SOURCE_C"
  ],
  "fallbackUsingCriteria": "ZERO_OR_MORE_THAN_ONE",
  "fallbackStrategies": [
    {
      "attribute": "configuration/entityTypes/Individual/attributes/Status",
      "survivorshipStrategy": "LUD"
    }
  ]
}

The highest-priority source that has a value wins regardless of recency, so the order must match your business intent.

Best practices

  • Don’t design filters that depend on another attribute’s OV status. Filters see all values on the profile.
  • Keep the driver attribute consistent across sources, so conflicting values don’t coexist on one profile.
  • Test survivorship changes in a lower environment, and check matchedFilters, unmatchedFilters and the applied rule with options=explainOv before promoting.
  • Review the fallback tiers with ZERO_OR_MORE_THAN_ONE: a later tier is only reached when the earlier tier returns no winner or several.

Related documentation

Was this article helpful?
0 out of 0 found this helpful

Comments

0 comments

Please sign in to leave a comment.