The cleanest solution would probably be to introduce a new attribute for Location, to control survivorship e.g. "UseLoqate" (boolean). For the Location entity type you would then alter survivorship by introducing a filter, with different source rankings for UseLoqate = true and false. It might look something like this:
{
"attribute": "configuration/entityTypes/Location/attributes/AddressLine1",
"sourcesForOv": [
"configuration/sources/CRM",
"configuration/sources/ERP",
"configuration/sources/CRM2"
],
"filter": {
"equals": [
{
"uri": "configuration/entityTypes/Location/attributes/UseLoqate",
"value": false
}
]
},
"survivorshipStrategy": "SRC_SYS"
},
{
"attribute": "configuration/entityTypes/Location/attributes/AddressLine1",
"sourcesForOv": [
"configuration/sources/ReltioCleanser"
],
"filter": {
"equals": [
{
"uri": "configuration/entityTypes/Location/attributes/UseLoqate",
"value": true
}
]
},
"survivorshipStrategy": "SRC_SYS"
}
------------------------------
Matthew Gagan
------------------------------
Original Message:
Sent: 07-09-2024 09:55
From: Matthew Gagan
Subject: Enable Loqate in Location entity conditionally on an attribute?
Posting on behalf of a Reltio customer:
Is it possible to enable locate in Location entity based on certain condition i.e. some attribute?
Our use case is that multiple domains will share same tenant, hence some domains want to use the address cleanse while others cannot allow any change in address fields, how can we cater to both?
------------------------------
Matthew Gagan
------------------------------