Reltio Connect

Hi Team,

We have defined specialty nested attribute and in that nested attribute we have specialty Type and Specialty . If Specialty Type is same we need to keep only one specialty for that type. We have defined Match field Uri on Specialty Type and Recency survivorship strategy on the Specialty . But if we load delta  data for the same crosswalk with same Specialty Type and different specialty , in the OV both specialties(old and new values) are showing . Could you please let us know how to resolve this .

Example :

Day1 : (Source A)Specialty Type : primary

             Specialty : Nurse.

Day 2:(Source A)Specialty Type : primary

             Specialty : Doctor.

In OV it is showing as 

Specialty Type : primary

             Specialty : Nurse, Doctor.

Expected: 

In OV it is showing as 

Specialty Type : primary

             Specialty : Doctor(Latest Value).

Note : enablepartialnestedattribue=true in physical config .

@Ashish Rawat @Gloria Faley , Could you please help us here .

Hi Team,

We have defined specialty nested attribute and in that nested attribute we have specialty Type and Specialty . If Specialty Type is same we need to keep only one specialty for that type. We have defined Match field Uri on Specialty Type and Recency survivorship strategy on the Specialty . But if we load delta  data for the same crosswalk with same Specialty Type and different specialty , in the OV both specialties(old and new values) are showing . Could you please let us know how to resolve this .

Example :

Day1 : (Source A)Specialty Type : primary

             Specialty : Nurse.

Day 2:(Source A)Specialty Type : primary

             Specialty : Doctor.

In OV it is showing as 

Specialty Type : primary

             Specialty : Nurse, Doctor.

Expected: 

In OV it is showing as 

Specialty Type : primary

             Specialty : Doctor(Latest Value).

Note : enablepartialnestedattribue=true in physical config .

@Ashish Rawat @Gloria Faley , Could you please help us here .

Hi Chenchu Giri Manduva,

Please excuse for late response. If crosswalk LUD date is aligned to Day2 then its data should survive. This could you be a consistency issue try Re-Indexing the record if that helps.

Hi Team,

We have defined specialty nested attribute and in that nested attribute we have specialty Type and Specialty . If Specialty Type is same we need to keep only one specialty for that type. We have defined Match field Uri on Specialty Type and Recency survivorship strategy on the Specialty . But if we load delta  data for the same crosswalk with same Specialty Type and different specialty , in the OV both specialties(old and new values) are showing . Could you please let us know how to resolve this .

Example :

Day1 : (Source A)Specialty Type : primary

             Specialty : Nurse.

Day 2:(Source A)Specialty Type : primary

             Specialty : Doctor.

In OV it is showing as 

Specialty Type : primary

             Specialty : Nurse, Doctor.

Expected: 

In OV it is showing as 

Specialty Type : primary

             Specialty : Doctor(Latest Value).

Note : enablepartialnestedattribue=true in physical config .

@Ashish Rawat @Gloria Faley , Could you please help us here .