Question

Weblink Search String URL Encoding Issue

WebLink Search and Retrieval

Updated May 2, 2019

asked on May 1, 2019

I was able to build a custom advance search that can search multiple templates using either weblink advance search or laserfiche client. But when i converted the search to URL enconding to create a link I'm not able to make it work. I noticed I have 1 element that added that there is no character for which is the pipe "|"

({[Permit Docs]}|{[CDD Docs]})&{[]:[Street Name]="Tustin Ave",[Street #]="546"}

http://ecms.newportbeachca.gov/Web/Search.aspx?dbid=0&searchcommand=%2B%7B%5BPermit%20Docs%5D%7D|%7B%5BCDD%20Docs%5D%7D%29&%7B%5B%5D%3A%5BStreet%20Name%5D%3D%22Tustin Ave%22%2C%5BStreet%20#%5D%3D%22546%22%7D

Use that URL I get "An unrecognized Character was encountered"

weblink.png (63.38 KB)

| Download

0 0

Answer

SELECTED ANSWER

replied on May 1, 2019

How did you encode the search syntax in the querystring? I found a helpful website that encoded the search syntax. I then pasted the encoded search string into the searchcommand portion of the querystring and it worked fine. The website I used was https://www.urlencoder.org/.

The complete encoded url that I used was...

http://ecms.newportbeachca.gov/Web/Search.aspx?dbid=0&searchcommand=%28%7B%5BPermit%20Docs%5D%7D%7C%7B%5BCDD%20Docs%5D%7D%29%26%7B%5B%5D%3A%5BStreet%20Name%5D%3D%22Tustin%20Ave%22%2C%5BStreet%20%23%5D%3D%22546%22%7D

1 0

Replies

replied on May 1, 2019 • Show version history

Awesome! that solved the issue. Website does all the work for you.

I manually changed the characters based on laserfiche weblink whitepaper.

0 0

replied on May 2, 2019

The Laserfiche WebLink instructions (Directly Linking to WebLink) do not list the hash sign "#" encoding. I have run into this myself and took me about 15 minutes to figure out the issue.

0 0

replied on May 2, 2019

Like Keith Hay mentioned below. I took my advanced search syntax that I got from doing search using laserfiche client and add that code into there website and gave me the correct conversion I needed.

0 0

replied on May 2, 2019

While looking at your querystring, I noticed there were several characters that were missed during the encoding. There was the | symbol, an &, and the # sign. That website made it easy to encode everything all at once. I'm glad that worked for you!

0 0

You are not allowed to follow up in this post.

Question

Question

Weblink Search String URL Encoding Issue

Answer

Replies

Sign in to reply to this post.