Reltio Connect

Hi Team,

Was checking out on Survivorship rules for configuring one of the use cases.
Generally as per documentation, we have below rules that can be chosen via Data Modeler application.

List - 
1. Reltio Cleanser or Nothing
2. Frequency
3. Aggregation
4. Source system
5. Oldest value
6. Minimum value
7. Maximum value
8. Other Attribute Winner Crosswalk
9. Recency

Along with Filters & Fallback strategies that can be defined as per the requirement.

Use case  - Let's say we have an attribute named "SIZE RANGE" with following values -
value 1 : 0-10 (Priority 1)
value 2 : 10-20 (Priority 2)
value 3 : 20-30 (Priority 3)
value 4 :30-40 (Priority 4)
value 5 :40-50 (Priority 5)

And survivorship rule needs to be created based on these values (i.e., for the value which is highest, need to give more precedence) 
If the value is in the form of 10,20,30,40..etc, we can choose Maximum/Minimum value - but not sure on this case.

Any thoughts on this .?

------------------------------
Chetan P
Lead MDM Specialist
Freshworks
Chennai
------------------------------

Hi Chetan,

You can still use Min/Max value as it extends to Numbers, strings as well.
Let's say the attribute is string, then the Min/Max value uses 'lexicographical' sort so for the below input:

Hi Team,

Was checking out on Survivorship rules for configuring one of the use cases.
Generally as per documentation, we have below rules that can be chosen via Data Modeler application.

List - 
1. Reltio Cleanser or Nothing
2. Frequency
3. Aggregation
4. Source system
5. Oldest value
6. Minimum value
7. Maximum value
8. Other Attribute Winner Crosswalk
9. Recency

Along with Filters & Fallback strategies that can be defined as per the requirement.

Use case  - Let's say we have an attribute named "SIZE RANGE" with following values -
value 1 : 0-10 (Priority 1)
value 2 : 10-20 (Priority 2)
value 3 : 20-30 (Priority 3)
value 4 :30-40 (Priority 4)
value 5 :40-50 (Priority 5)

And survivorship rule needs to be created based on these values (i.e., for the value which is highest, need to give more precedence) 
If the value is in the form of 10,20,30,40..etc, we can choose Maximum/Minimum value - but not sure on this case.

Any thoughts on this .?

------------------------------
Chetan P
Lead MDM Specialist
Freshworks
Chennai
------------------------------

Hi Sheshadri,

I have already tried this method where even it uses lexicographical method, does't give output as expected.

For example - Values entered : 
  Value 1 : 1-10
  Value 2 :11-50
  Value 3 :51-250
  Value 4 :251-500
  Value 5 :501-1000
  Value 6 :1001-5000
  Value 7 :5001-10000
  Value 8 :10000+

The above stated are expected values, but when comparing these value, expected output should be (10000+) but what i get is (51-250). I am still Looking a way to solve this.

Hi Chetan,

You can still use Min/Max value as it extends to Numbers, strings as well.
Let's say the attribute is string, then the Min/Max value uses 'lexicographical' sort so for the below input:

Hi Team,

Was checking out on Survivorship rules for configuring one of the use cases.
Generally as per documentation, we have below rules that can be chosen via Data Modeler application.

List - 
1. Reltio Cleanser or Nothing
2. Frequency
3. Aggregation
4. Source system
5. Oldest value
6. Minimum value
7. Maximum value
8. Other Attribute Winner Crosswalk
9. Recency

Along with Filters & Fallback strategies that can be defined as per the requirement.

Use case  - Let's say we have an attribute named "SIZE RANGE" with following values -
value 1 : 0-10 (Priority 1)
value 2 : 10-20 (Priority 2)
value 3 : 20-30 (Priority 3)
value 4 :30-40 (Priority 4)
value 5 :40-50 (Priority 5)

And survivorship rule needs to be created based on these values (i.e., for the value which is highest, need to give more precedence) 
If the value is in the form of 10,20,30,40..etc, we can choose Maximum/Minimum value - but not sure on this case.

Any thoughts on this .?

------------------------------
Chetan P
Lead MDM Specialist
Freshworks
Chennai
------------------------------

Hi Chetan,

Can you shows us the config and what type of sort is applied here:

Let's say if we have above values then we can use sortAs as Number based and provide Min Value so that we may get the highest
Ex: 1-10 gives -9 and 11-50 gives -39 so the Min provides -39 and winner would be 11-50.
But the issue is with 10000+ as it can be read as integer.
You can try out the sortAs if not already tried and we may have to take off the + character so that we do not get any error.

Hi Sheshadri,

I have already tried this method where even it uses lexicographical method, does't give output as expected.

For example - Values entered : 
  Value 1 : 1-10
  Value 2 :11-50
  Value 3 :51-250
  Value 4 :251-500
  Value 5 :501-1000
  Value 6 :1001-5000
  Value 7 :5001-10000
  Value 8 :10000+

The above stated are expected values, but when comparing these value, expected output should be (10000+) but what i get is (51-250). I am still Looking a way to solve this.

Hi Chetan,

You can still use Min/Max value as it extends to Numbers, strings as well.
Let's say the attribute is string, then the Min/Max value uses 'lexicographical' sort so for the below input:

Hi Team,

Was checking out on Survivorship rules for configuring one of the use cases.
Generally as per documentation, we have below rules that can be chosen via Data Modeler application.

List - 
1. Reltio Cleanser or Nothing
2. Frequency
3. Aggregation
4. Source system
5. Oldest value
6. Minimum value
7. Maximum value
8. Other Attribute Winner Crosswalk
9. Recency

Along with Filters & Fallback strategies that can be defined as per the requirement.

Use case  - Let's say we have an attribute named "SIZE RANGE" with following values -
value 1 : 0-10 (Priority 1)
value 2 : 10-20 (Priority 2)
value 3 : 20-30 (Priority 3)
value 4 :30-40 (Priority 4)
value 5 :40-50 (Priority 5)

And survivorship rule needs to be created based on these values (i.e., for the value which is highest, need to give more precedence) 
If the value is in the form of 10,20,30,40..etc, we can choose Maximum/Minimum value - but not sure on this case.

Any thoughts on this .?

------------------------------
Chetan P
Lead MDM Specialist
Freshworks
Chennai
------------------------------

I haven't tried the Sortas option on this one. 
Any reference link or additional information on utilising this feature will help me Sheshadri.

Hi Chetan,

Can you shows us the config and what type of sort is applied here:

Let's say if we have above values then we can use sortAs as Number based and provide Min Value so that we may get the highest
Ex: 1-10 gives -9 and 11-50 gives -39 so the Min provides -39 and winner would be 11-50.
But the issue is with 10000+ as it can be read as integer.
You can try out the sortAs if not already tried and we may have to take off the + character so that we do not get any error.

Hi Sheshadri,

I have already tried this method where even it uses lexicographical method, does't give output as expected.

For example - Values entered : 
  Value 1 : 1-10
  Value 2 :11-50
  Value 3 :51-250
  Value 4 :251-500
  Value 5 :501-1000
  Value 6 :1001-5000
  Value 7 :5001-10000
  Value 8 :10000+

The above stated are expected values, but when comparing these value, expected output should be (10000+) but what i get is (51-250). I am still Looking a way to solve this.

Hi Chetan,

You can still use Min/Max value as it extends to Numbers, strings as well.
Let's say the attribute is string, then the Min/Max value uses 'lexicographical' sort so for the below input:

Hi Team,

Was checking out on Survivorship rules for configuring one of the use cases.
Generally as per documentation, we have below rules that can be chosen via Data Modeler application.

List - 
1. Reltio Cleanser or Nothing
2. Frequency
3. Aggregation
4. Source system
5. Oldest value
6. Minimum value
7. Maximum value
8. Other Attribute Winner Crosswalk
9. Recency

Along with Filters & Fallback strategies that can be defined as per the requirement.

Use case  - Let's say we have an attribute named "SIZE RANGE" with following values -
value 1 : 0-10 (Priority 1)
value 2 : 10-20 (Priority 2)
value 3 : 20-30 (Priority 3)
value 4 :30-40 (Priority 4)
value 5 :40-50 (Priority 5)

And survivorship rule needs to be created based on these values (i.e., for the value which is highest, need to give more precedence) 
If the value is in the form of 10,20,30,40..etc, we can choose Maximum/Minimum value - but not sure on this case.

Any thoughts on this .?

------------------------------
Chetan P
Lead MDM Specialist
Freshworks
Chennai
------------------------------