You can prevent items being verified in DxDataBook by configuring the load and annotate options. If you have parts that only differ by a pointer to a datasheet, then that is more difficult as DxDataBook will see these as unique. You may also find this discussion useful
To provide further assistance you will need to provide more details about how you have DxDataBook configured.
Thanks for the help. I tried removing the checks for load and annotate on the properties that were giving me issues. The output from verification is the same. When I try to load a component back into databook, the fields that were red are now blank but it is still not found. Seems like verification is still looking for these fields as they are already present in the schematic. Any other suggestions?
I would raise an SR with customer support, they will be able to walk you through the issue more easily than via this forum.
I had some weeks ago a case where the parts are originally placed from DxDB into DxDesigner. The verification said exactly what you describe. Finally we found that the string in the database had a space or more at the end or the beginning. Deleting these spaces in the database solved this issue. These spaces came into the database during copy and paste from external data sources while filling the database.
Probably worth a try.
Thanks for the feedback Rocco. Unfortunately i have checked this and it is not the issue.
I really feel that the issue I am seeing is largely due to the search being case snsitive. Could you please let me know how to set the data to be non-case sensitive?
Are you loading symbol? It doesn't show up in the verify list but can cause verify to fail.