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

Question

Question

Search Syntax Error

asked on February 15, 2019

I use the Search URLs token from Generate Laserfiche Web Client URLs activity to embed in the email.

Below is the syntax I currently use trying to locate/list the documents with the Expiration Date equals to or less than a year.  But it results in error "An unrecognized character was encountered. [9085].

Can anyone please point out what needs to be corrected? 

 

{[Vendor Data]:[Document Type]="W-9"} & {LF:Name="*", Type="DB"} & {LF:LOOKIN="Path"}, [Insurance Expiration] <= "%(DateTokenCalculator_Current Date Plus 1 Year)"}

 

Thanks in advance.

0 0

Replies

replied on February 15, 2019 Show version history

A few things stand out. First, you have one more closing curly brace than you have opening curly braces. The one at the end should be paired with an opening one. It would probably go before [Insurance Expiration]. Second, it appears that the comma isn't the right operator here. Third, You need the []: prefix on standalone fields.

{[Vendor Data]:[Document Type Type]="W-9"} & 
{[]:[Insurance Expiration] 
<="%(DateTokenCalculator_Current Date Plus 1 Year"} & 
{LF:Name="*", Type="DB"} & {LF:LOOKIN="Path"}

I generated the structure of the above query in the client, and then customized it to your field names. Sometimes that's much less frustrating than trying to write a whole query by hand.

3 0
replied on February 18, 2019

I was able to find the solution with this post. I applied the "Encode URI" function to the Generate Laserfiche URL token, which kept the email link from breaking and in tact when clicked.

The link now opens the site with the expected search results.

3 0
replied on February 15, 2019

Thank you.  This syntax works in the "Search Repository" activity.

However, in "Generate Laserfiche Web Client URLs- activity, I used the exact same syntax to create the Search URLs token, and embedded the link in Email, ran the workflow and clicked on the link on the email I received, the Weblink page opens but still the same error shows and fails to display the result entries in Repository.

0 0
replied on February 15, 2019

Can you share the URL? Often times the issue is incorrect URL encoding, but I cannot tell without seeing the URL itself.

Another potential issue could be with the token that is being substituted in, which again I need to see the URL to determine. If the URL still has the token in it when it is emailed out, then the link will not work.

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

Sign in to reply to this post.