Trust score is calculated based on the settings.
Manually updated means, did you perform direct update in the database?
If you execute revalidate for that particular record then it will recalculate trust and updates accordingly.
Yes, I have manually updated the record directly in database, since it is development environment it takes ~280 hours for revalidate job to complete successfully, so I thought of confirming before triggering it.
Also is there a way to perform revalidation for a particular record or a set of records?
I can perform recalculate for particular record/table, but I do not see any procedure or package to perform revalidation for particular record.
Since the record is directly updated in xref, I need to perform revalidation to revalidate the trust scores before recalculation.
You should avoid using direct SQL update as the dependent tables doesn't get updated with the relevant values and it could create an issue during BVT calculation.
Did you made any changes to the validation rules recently because of which the data needs to be revalidated? Please note that revalidate job only needs to be executed when you are modifying the validation rules since the last load. If there is just data change, you do not need to execute the revalidate job at all.
In such a scenario, you just need to update the data via a regular Load Job or SIF API for it to reflect the correct trust values.
If you are facing performance issues with revalidate - you may want to tweak the multithreaded batch properties for performance improvement -
Thank you for your suggestion, since this is an already existing record, the difference in count returns 0, and the dirty indicator is also 1 for this record. So is there any other way to perform revalidation for selected records only?
As per Rahul's suggestion earlier, you can use this KB# Support to basically queue a subset of records for revalidate. Instead of <rnum condition in the Query#3 for update, you can try to replace with particular rowid_object in the queries of the KB before executing revalidate.
We have not tested this, but it should work in the same way.
Hi Kunal, thank you for your suggestion. Since the record is manually updated and since it is already present in database, the first count statement is returning 0 records (No difference between BO_xref and BO_VXR, also the dirty indicator is 1)
We are using Informatica MDM 9.1 and we do not have any SIF API's.
Please confirm if this scenario will work? Though revalidation is not required if the validation needs to be performed for one single record, will it still override the trust score for the manually updated record (Decrease the trust score from 80 to 20 for a record which was marked as partially deleted manually, present trust score is 80)
Can you please confirm - "you are modifying the validation rules since the last load". If not, I will recommend that you revert the data back and send an update using the load job. This should reflect the correct trust. For 9.1, not sure if the data changes will reflect in Trust settings even after you revalidate.
You can just add a filter on the stage mapping to have only that record go thru stage and load job.
No, the validation rules remains same, I will try both revalidate and load approach and let you know the outcome.
Yes, please execute a load job and use KB# 525128 to under revalidate job.
What you may need is to execute the recalculate BVT job for a single record - Recalculate BVT Jobs
The behavior should be same in 9.1.
Revalidating the Address table and then running recalculate procedure have fixed the issue.
Have one question, can revalidate job be cancelled/set to incomplete status once after triggering it? Will there be any impact if we do so?
You should be able to cancel the execution but whether it will halt successfully will depend on the execution point of the job at the time. As it is an unsupported version, we do not have any references for the same at this time.