You are viewing limited content. For full access, please sign in.

Question

Posted to Laserfiche Lounge

Search Repository error messages #9084 and #9085

asked on October 13, 2017

I am getting error messages when using the Searching Repository action. The field parameter being used is called “Purchase Order Number” which is a Text field.

In the workflow, I retrieve the “Purchase Order Number” field value. The Search Repository action follows further down in the workflow. The search syntax is as follows:

 {[]:[Purchase Order Number]=%(RetrieveFieldValues_Purchase Order Number)} & ({LF:LOOKIN="lf-lf\Purchase Orders\Electric\02 - Waiting for all Quotes"} | {LF:LOOKIN="lf-lf\Purchase Orders\Electric\03 - Quotes waiting for approval"})

Since a Purchase Order Number has not been assigned at this point of our process, we are using a Temporary Purchase Order Number. During our testing, the operator has tried a variety of different temporary numbers.

If a number is used like 08231, the search does not fault.

If a number with dashes are used like 8-23-1. I get the following error: An unrecognized character was encountered. [9085] and Search result comes back saying “No entry was found” even though there are results available.

If words are used like ASR SPARROW. I get the following error: A syntax error was encountered while processing the search or query statement. [9084] and Search result comes back saying “No entry was found” even though there are results available.

If I take out the space like SPARROW, the search does not fault.

Do I have something wrong where the operator cannot use “spaces” or “-“? Or is this a limitation? And if it is a limitation, is there a list of characters that should not be used?

Thank you

1 0

Answer

SELECTED ANSWER
replied on October 13, 2017

Your field value needs to be in double quotes:  {[]:[Purchase Order Number]="%(RetrieveFieldValues_Purchase Order Number)"}

1 0

Replies

replied on October 19, 2017

That worked. Thank you.

0 0
You are not allowed to follow up in this post.

Sign in to reply to this post.