A view used for lookup suddenly starts to throw the error "Entry not found in index", even though there are documents that match the lookup key and no change was made to the view's design.
Problem:
The view has the option "ODBC Access: generate unique key" active and there are Replication Conflict documents displayed on the view.
Solution:
Add this formula to the view's selection formula, to exclude the Replication Conflicts and the error will stop: !@IsAvailable($Conflict)
