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

Question

Question

Weblink quick search command parameter

asked on July 31, 2019

I am currently working on Weblink Search.aspx page and I'm looking to change how the search command is constructed with quick search. 
The public will use a link to access weblink which already includes the following URL parameter included(Using 191 as an example):

search.aspx?dbid=0&searchcommand={LF:Name~="191", Type="D"} & {LF:AssociatedPages="Y"}

 

When the user uses the quick search bar at the top it is using the following search command:

search.aspx?dbid=0&searchcommand={[]:[]="191"}

 

This is returning documents that are not relevant for the user.

Anyone able to help me with how to customize so that the quick search bar uses the more strict search command (searchcommand={LF:Name~="191", Type="D"} & {LF:AssociatedPages="Y"})?

 

Any help is much appreciated!

0 0

Replies

replied on July 31, 2019

I might be wrong, but I don't think you can customize the search syntax for quick searches in WebLink the same as you can in the other clients. If it's causing an issue, you might be better off disabling the search completely and building your own custom search form.

Here's the documentation on the available options for the quick search box.

1 0
replied on May 20, 2022

Hello Dean, I recommend that the search string be encoded with UTF-8 as the target string set, I had a similar issue and it was solved by applying the encoding.
Here an example:

- Original string:   http://weblinksrv/Weblink/Search.aspx?dbid=0&searchcommand={LF:Modified="2022/05/20"} & {LF:LOOKIN="\CON - Contenedor\GESCON\REGISTRO CONTABLE DIARIO"} & {LF:Ext="pdf"}

- Encoded string:  http://weblinksrv/Weblink/Search.aspx?dbid=0&searchcommand=%7BLF%3AModified%3D%222022%2F05%2F20%22%7D%20%26%20%7BLF%3ALOOKIN%3D%22%5CCON%20-%20Contenedor%5CGESCON%5CREGISTRO%20CONTABLE%20DIARIO%22%7D%20%26%20%7BLF%3AExt%3D%22pdf%22%7D

 

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

Sign in to reply to this post.