Configuring OV Values
You can send OV values for cleansing using the ovOnly parameter in the cleanseFunction section of the tenant configuration.
The ovOnly parameter controls which values are sent to the cleanse service. Use the following guidelines to understand how it works:
- When
ovOnlyis absent or set tofalse, Cleanse uses all mapped values, including values marked as"ov":"true"and"ov":"false". - When
ovOnlyis set totrue, Cleanse only uses values marked as"ov":"true".
Use OV-only cleansing with stable OV values
When ovOnly is set to true, the cleanser only uses values marked as OV. If an address input attribute resolves to zero or multiple OV values, or if survivorship does not consistently select one winner, different evaluations can send different inputs to the cleanser. This can produce different normalized outputs and affect downstream logic that uses exact address comparisons for matching, retain, or merge decisions.
To help maintain stable cleanse results, use the following guidelines:
- Use a deterministic survivorship strategy with fallback behavior that resolves zero-winner and multiple-winner outcomes, for example, set
fallbackUsingCriteria: "ZERO_OR_MORE_THAN_ONE". - Make sure each address input used for cleansing resolves to exactly one OV value.
- Apply the same survivorship approach across related address fields.
- Validate that repeated cleansing produces the same normalized output for the same entity.
Example configuration
The following example shows how to use the ovOnly parameter:
{
"cleanseFunction": "Loqate",
"options": {
"loqateKey": "******************",
"ovOnly": "true"
}
},