Why is my attribute not showing as OV true using a match rule using a filter?

Question

As part of some update activity we have loaded the data through Reltio Data loader in EMEA Production for attached set of customers(638). We tried to add email id for these customers. Unfortunately the value which we are adding is getting loaded but that is not coming in OV in UI. 

Please refer to the attached screenshot where the value which is added it there in source tab, also the survivorship rule is recency. But this is not appearing in OV.

When we tried to pin the value, its coming up in OV. But ideally when we load the data, it should show up in Operational value. 

Could you please check why the OV value is not showing up in UI even after loading it into Reltio.

This is stopping records from reaching to downstream. 

Answer

This is a configuration issue.

{
                            "attribute": "configuration/entityTypes/HCP/attributes/Email",
                            "filter": {
                                "equals": [
                                    {
                                        "uri": "configuration/entityTypes/HCP/attributes/Email/attributes/TypeIMS",
                                        "value": "E-MRKTNG"
                                    }
                                ]
                            },
                            "fallbackStrategies": [
                                {
                                    "attribute": "configuration/entityTypes/HCP/attributes/Email",
                                    "comparisonAttributeUri": "configuration/entityTypes/HCP/attributes/Email/attributes/Email",
                                    "fallbackStrategies": [
                                        {
                                            "attribute": "configuration/entityTypes/HCP/attributes/Email",
                                            "comparisonAttributeUri": "configuration/entityTypes/HCP/attributes/Email/attributes/Rank",
                                            "survivorshipStrategy": "MinValue"
                                        }
                                    ],
                                    "fallbackUsingCriteria": "MORE_THAN_ONE",
                                    "survivorshipStrategy": "MinValue"
                                }
                            ],
                            "fallbackUsingCriteria": "MORE_THAN_ONE",
                            "survivorshipStrategy": "LUD"
                        },

  {
                            "attribute": "configuration/entityTypes/HCP/attributes/Email",
                            "sourcesForOv": [
                                "configuration/sources/NONE"
                            ],
                            "survivorshipStrategy": "LUD"
                        },

• Add one more filter

{
                                        "uri": "configuration/entityTypes/HCP/attributes/Email/attributes/TypeIMS",
                                        "value": "E-Marketing"
                                    }

• As the above is a change in the rule they need to run reindex with separate indexing.

curl --location --request POST 'https://<envirnonment>.reltio.com/reltio/reindex?taskPartsCount=4&distributed=true&tenantId=&updateEntities<tenantID>=true&forceIgnoreInStreaming=true&enableSeparateIndexing=true' \
--header 'Authorization: Bearer 43437a0d-48bd-4100-bf9f-9dc99aa55ea5' \
--header 'Content-Type: application/json' \
--data-raw ''