Thanks for the reply.

I did look at the page you referenced but it doesn't do what I need.

I need to lookup the vendor provided value to see if it's valid or not.

I have many imports that happen so it's probably best to write one business rule to validate the field no matter what imports the data.

Today, at least in this environment, the imports sure can create CI with null or bad data. Doesn't seem they reject anything.

So, I'm ok with vendor sending an unknown model. It's more important to let the CI create then have someone remediate these 'bad' or 'unknown' values.

I don't want a person to have to sift through import sets or logs to find any imports that sent unknown or bad values.

I want the business rule to lookup the field such as model_number and if it doesn't match an existing model_number in cmdb_model then don't stop the CI update or CI creation. I want to capture that in a ci_exception table to note that serial number has an "Invalid Model" so someone can investigate.

If a user attempts to add a bad model those are already rejected today. The user then has to investigate and resolve. However, during an import at 4am there is no one there to intervene at the point of CI creation to resolve. I want an import to move forward but make a note so later someone can remediate.