I agree that it is looking like support will be your best route. One suggestion: try it with the API. You might get a more informative error message.
--
Original Message:
Sent: 11/12/2024 5:27:00 PM
From: john stormberg
Subject: RE: MinValue Survivorship for Status
Yeah I'm just using the UI - Console Data Modeler. I'd agree it would be more elusive if it was via API. I saw some other posts suggesting this as a solution, so its weird that it isn't just working. May open a support ticket to get it resolved.
------------------------------
john stormberg
FCSAmerica
------------------------------
Original Message:
Sent: 11-12-2024 17:07
From: Gino Fortunato
Subject: MinValue Survivorship for Status
Thanks for the clarification. I agree that if you are not getting it elsewhere, my theory would not be correct.
Are you using the Console Data Modeler? Or trying this via the API directly? If you are using the API, would you try it with the data modeler? There might be a typo somewhere that is hard to detect.
------------------------------
Gino Fortunato
Senior Solution Engineer
Reltio
Original Message:
Sent: 11-12-2024 14:32
From: john stormberg
Subject: MinValue Survivorship for Status
Hi Gino,
There is only an issue with specifically using min/max value on the status string. I can change to any other survivorship rule and save my changes. I don't believe its related to the entity model, because I don't receive any errors except for when trying to implement the min/max value rule on a the status string.
------------------------------
john stormberg
FCSAmerica
Original Message:
Sent: 11-11-2024 12:00
From: Gino Fortunato
Subject: MinValue Survivorship for Status
Hi John,
I believe the error is telling you that there is already an error in the config, one that has nothing to do with your survivorship strategy. Can you try just posting the config as it is and see if you get an error? You can try looking at the config for the entity type in the Console Data Modeler, too
------------------------------
Gino Fortunato
Senior Solution Engineer
Reltio
Original Message:
Sent: 11-08-2024 12:00
From: john stormberg
Subject: MinValue Survivorship for Status
I am attempting to use the MinValue survivorship strategy with the OtherAttributeWinnerCrosswalk strategy to always survive Status with a value of "Active". However, when I try to save the survivorship configuration, I receive this error "One or few errors was found during validation of Reltio Business Model" with no other explanation and I cannot identify anything wrong based on the documentation. Is there an explanation for this error and a potential solution to achieve the business goal of always surviving value="Active"?
"attribute": "configuration/entityTypes/Organization/attributes/StatusInformation",
"sourcesUriOrder": [
"configuration/sources/ServiceNow",
"configuration/sources/Salesforce",
"configuration/sources/ReltioCleanser",
"configuration/sources/DataProvider",
"configuration/sources/FCSADomain",
"configuration/sources/ReltioStringFunctionCleanser",
"configuration/sources/ReltioFullNameBuilder",
"configuration/sources/SAP",
"configuration/sources/DnB",
"configuration/sources/Reltio",
"configuration/sources/ReltioGrouping",
"configuration/sources/ZoomInfo",
"configuration/sources/BvD",
"configuration/sources/Workday"
],
"survivorshipStrategy": "OtherAttributeWinnerCrosswalk",
"primaryAttributeUri": "configuration/entityTypes/Organization/attributes/StatusInformation/attributes/Status"
},
{
"attribute": "configuration/entityTypes/Organization/attributes/StatusInformation/attributes/Status",
"survivorshipStrategy": "MinValue",
"fallbackUsingCriteria": "ZERO_OR_MORE_THAN_ONE",
"fallbackStrategies": [
{
"attribute": "configuration/entityTypes/Organization/attributes/StatusInformation/attributes/Status",
"survivorshipStrategy": "SRC_SYS",
"sourcesUriOrder": [
"configuration/sources/ServiceNow",
"configuration/sources/Salesforce",
"configuration/sources/ReltioCleanser",
"configuration/sources/DataProvider",
"configuration/sources/FCSADomain",
"configuration/sources/ReltioStringFunctionCleanser",
"configuration/sources/ReltioFullNameBuilder",
"configuration/sources/SAP",
"configuration/sources/DnB",
"configuration/sources/Reltio",
"configuration/sources/ReltioGrouping",
"configuration/sources/ZoomInfo",
"configuration/sources/BvD",
"configuration/sources/Workday"
]
}
]
},
{
"attribute": "configuration/entityTypes/Organization/attributes/StatusInformation/attributes/StatusReason",
"survivorshipStrategy": "OtherAttributeWinnerCrosswalk",
"primaryAttributeUri": "configuration/entityTypes/Organization/attributes/StatusInformation/attributes/Status"
},
{
"attribute": "configuration/entityTypes/Organization/attributes/StatusInformation/attributes/UpdateDate",
"survivorshipStrategy": "OtherAttributeWinnerCrosswalk",
"primaryAttributeUri": "configuration/entityTypes/Organization/attributes/StatusInformation/attributes/Status"
},
{
"attribute": "configuration/entityTypes/Organization/attributes/StatusInformation/attributes/Comments",
"survivorshipStrategy": "OtherAttributeWinnerCrosswalk",
"primaryAttributeUri": "configuration/entityTypes/Organization/attributes/StatusInformation/attributes/Status"
},
------------------------------
john stormberg
FCSAmerica
------------------------------