Invalid UNID

I have an audit database containing some compliancy fields. The db owner wants a new audit to look back at the prior audit and determine whether a field was marked compliant (X) on the prior audit, and then fill in the corresponding field in the new audit with an X. I have:1. A view by Store, Audit Date, UNID

  1. A field named GetMe in the audit form that gets the UNID by doing a lookup to the view; temp:=@DbLookup(“Notes”:“”;“”;“vwPrior”;@Name([CN];Store);3);

@If(@IsError(temp);“”;@Subset(temp;1))

  1. The field that gets the “marked compliant” value from the other document; @GetDocField(GetMe; “R1”)

I’m getting an error UNID must be a 32-digit hex string. I’ve searched the forum and saw many references to this, but still can’t figure out what I’m doing wrong. Please help if you can. Thanks!

Subject: Invalid UNID

Are you sure that GETME contains a text value containing a UNID?

Subject: RE: Invalid UNID

The view formula is @Text(@DocumentUniqueID). All GetMe does on the form is the lookup to the view. How can I tell if the GetMe field in the form is text like the view?

Subject: RE: Invalid UNID

You need to do some debugging. Try putting something like this in a button on your form:

@Prompt( [OK]; “getme contains”; GetMe )

If that fails, then it must not be text – try adding @Text around Getme. Once you have confirmed that you have a valid UNID, then you can proceed to the next step.

Subject: RE: Invalid UNID

I added the prompt and the ID looks fine to me. I’m really at a loss here. I googled this problem as well and can’t find an answer.

Subject: RE: Invalid UNID

Other than these links, I don’t have other ideas.

http://www-10.lotus.com/ldd/nd6forum.nsf/0/4e70820fd99230b985257377002e53b1?Open

http://www-10.lotus.com/ldd/nd6forum.nsf/0/3b17da346d9ecd75852572bb004b8d75?Open

Subject: RE: Invalid UNID

Are you sure that GetMe contains a valid UNID when the error is encountered? Try changing the formula for the @GetDocField to include an @If that skips the lookup when GetMe contains “”.

Subject: RE: Invalid UNID

Is there a reason why you’re getting the UNID from the view and then using this to retrieve the R1 field from the document for UNID?

A better approach may be to add the R1 field to the view itself and get this directly.

Subject: RE: Invalid UNID

Finally got this working by using the GetDocField formula in the field. The reason I wasn’t getting R1 from a view is because I have 50 other “R” fields I’d need to add to the view so it was a lot easier to get the formula working. We think there was a problem with the field name I was referencing. Anyway, thanks to all for your suggestions!