@DbLookup not working - key too long?

HCL Domino Domino Forum
1

My lookup isn’t working and I’ve verified that the lookup key is found in the view manually.

Is it possible its not being found because there is a size limit to the key?

The key I’m using is 87 characters long and includes the UID of a form. Here is a sample key string:

*** Server not connect - ID will be assigned later~UID=429794F6FBD94D7285256FC800568462

When the ID is finally assigned overnight to a 9 character ID it seems to work fine. Hence my question about key size limits.

I have the same issue when using the key in the “Show single category” attribute of an embedded view.

Thanks in advance,

2

Subject: @DbLookup not working - key too long? - Here’s the workaround

I had the same problem. I was using the unid (computed when composed) as my lookup key. Sometimes it worked, sometimes it didn’t. I prefixed it with “key=”, and now the lookups always work. So, I have a DocID field which is the actual unid, and I have a lookupkey field which is computed to “key=”+DocID. I use the lookupkey field in all my lookups, and that is the value that is displayed in the lookup view. All is working fine with this scheme.

3

Subject: @DbLookup not working - key too long?

The “*” represents a wild card (all categories) entry in Show Single Category; it could be that starting the string with asterisks is causing the problem.

4

Subject: RE: @DbLookup not working - key too long?

Good theory.What about @DbLookup? Does it also support * wildcards?

5

Subject: @DbLookup not working - key too long?

I just tried a 100 character key, with not probs.

ST