Overrides on records in OGC

@Ales This is the question I was referring to. Thank you.

@sgilla I’m afraid this is specific custom part of the OMNI solution where I do not have much visibility to. 

In general Ataccama Matching can accept overrides - typically an external source (file/table) containing the required overrides. This is probably your [ids_override_match].

If you delete such overrides the matching SHOULD simply not consider any override in the process and SHOULD match using standard matching rules HOWEVER there must be another step enabled somewhere in your solution - Manual Override Builder. This STEP allows you to rebuild the repo with the override inputs.

I know this is probably not giving you the ultimate answer however you may check if the whole process has all required components in place first.

@Ales  thank you for a direction, i will look into it. 

There is no manual override that was found on the component. The records match when the override_match (one of the match rules) is edited to remove the white list. But they get added back even though the records have been removed from the override table. There should be another table I am missing? I checked all the ticket tables to find any traces but none found. 

@Ales  I confirm in my case [omnihealthdata].[dbo].[ids_override_match]  is the table. It was a little tricky to find the related records, i should go by the master id and not just the instance id. Thank you for the help in pointing me back to the table.