Entry not found in index or view's index not built

HCL Domino Domino Forum
1

I have a View called Venue which just has two columns:The 1st Column Lists Sites, and the 2nd Column Lists Venues.

Everything displays as you would expect it to in the view.

I have a field called ReceivingSites on a form.

It creates a dialog list by using DbColumn to get a list of unique Sites (column 1) from the view.

@Unique(@DbColumn(“”;“”:“”;“Venue”;1))

Works perfectly.

I then have a second field called Venues. I want to create a dialog list based on the choices of the first list, ReceivingSites.

Using the formulas given in Lotus 6.5.1 help files I get:

@DbLookup( “” : “NoCache” ; “” : “” ; “Venue” ; ReceivingSites ; 2)

or

@If(ReceivingSites = “”;0;@DbLookup(“Notes”:“NoCache”;“”:“”;“Venue”;ReceivingSitest;2))

I’ve tried many variations - but always get the error:

Entry not found in index or view’s index not built

Any idea what may be causing this? I am chosing use formula for choices in the field properties and entering the formula there.

Any help much appreciated,

Sarah

2

Subject: Entry not found in index or view’s index not built

Hi Sarah,

The first column will need to be categorised. Also, watch for the value you are looking up - seems there might be a typo in one of those formulas. If you’re stil having problems, hard-code the site value to one you know that is there to make sure it is not a problem with the site field on your form.

HTH

Andrew

3

Subject: Entry not found in index or view’s index not built

First, there’s a typo in your code. Don’t know if it’s in your real code or just here, but might be worth looking into:

@If(ReceivingSites = “”;0;@DbLookup(“Notes”:“NoCache”;“”:“”;“Venue”;ReceivingSitest;2))

In the DBLookup you added an extra T after ReceivingSites.

Also, make sure your ReceivingSites field properties are set to Refresh Fields on Keyword Change and Refresh Choices on Document Refresh. If you don’t have those set, then your DBLookup isn’t actually getting the value of ReceivingSites.

4

Subject: RE: Entry not found in index or view’s index not built

Thanks both - yeah the typo was just here. Need to hop over to my other computer to test these out - will post back here once I’ve tried them!

5

Subject: Entry not found in index (uncheck create full text index)

Hey Gang!

Glad I checked here I was able to figure out my own issue reading these posts. If you make copies of a database and check the ‘Create full text index for searching’ in the pop up that may also result in the error ‘Entry not found in index’, at least that was my case.

I grabbed a different copy and did not check that and loaded the form into the App, and all is well.

Just in case someone else has the same issue.

L8ter!

6

Subject: Thank You!!

Amazing, all I needed to do all day was make the view categorized. I didn’t see that anywhere in help, or in the tutorial I was following. So, I finish at 8pm, but I finish knowing it works - really appreciate your help :slight_smile:

7

Subject: RE: Thank You!!

You actually shouldn’t have to make it categorized; you just need to make sure the first column is sorted.

8

Subject: Entry not found in index or view’s index not built

well, the most obvious thing (if this is a copy-paste of your code) is the key in your lookup is wrong - ReceivingSitest

HTH