Subject: Entry Not Found In Index - With No @DBLookups!!
With the help of Ben Poole, i’ve got the above problem solved. The error was caused because I was setting my UNID field to Computed When Composed, which was actually giving me an incorrect UNID.
When I changed the field to Composed and re-saved the document, the link works fine. It seems that the doc gets one UNID when it’s composed, and it’s changed when it’s saved. I never knew this one…
Subject: Entry Not Found In Index - With No @DBLookups!!
The error has nothing to do with @DbLookup, and everything to do with Domino not being able to get a handle on the document in that view.
I think you’re saying that the full URL you provide does work, so this suggests that something is going awry with the “UNID” variable referenced by the Javascript. You might want to check that. Whilst it may contain a value that looks like a valid unique ID, are you positive that this is the value you’re expecting (“D0AE5F042413149280256DDB005132D1” in your example)?
I’m not 100% sure about this, but I think it’s the case with Domino that when you create a document, an initial UNID is generated, which may well change when the document is saved. Take a look at the UNID specified in document properties on the in the notes:// tab.