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

Question

Question

WebLink Providing Different Results?

asked on June 5

Anyone have experience with WebLink providing different search results, when compared to the full clients?

I did a test, seeded an entry with a very random string "EF38468Y" using the desktop client, I searched for :
({LF:Basic~="EF38468Y", option="LTDFNA"}) and received one result, the correct one.

 

In the weblink, created a new search form, with a field for date range and a text field with token "MeetingTopic"

My search query was built with

Search for entries that meet all constraints
      Field:[Date of Meeting] Matches User Input
      Custom {[Agenda & Minutes]} | {[Agenda & Minutes- Pre-2024]}
      Custom ({LF:Basic~="%(MeetingTopic)", option="LTDFNA"})


When I search with the custom search, I get 140+ results, with the targeted entry being the first on the list. I'm confused on why the client search gives me the one result, but the same search, made more refined by specifying a date range and templates in WebLink come up with so many extra results, and how they can be valid, since I doubt that term is used anywhere else?

0 0

Answer

SELECTED ANSWER
replied on June 10

I found a solution that worked for me, so I wanted to share it in case it will help others. Since the only difference between the searches was the template name, I created a few groups. With the main group being "meet any constraint" and two sub groups that were "meet all constraints" both sub groups had the same filters, except different templates. One thing I learned when adding these groups, you have to work top down, once you add a second sub group, you can't move anything to the first sub group (at least I couldn't figure out how).

 

Hope this helps

1 0

Replies

replied on June 8

Can you help confirm if the 140+ results match the {[Agenda & Minutes]} template condition?

It seemed that the | in {[Agenda & Minutes]} | {[Agenda & Minutes- Pre-2024]} would make the whole query as "{[Agenda & Minutes]} or other conditions".

0 0
replied on June 9

Hi Rui,

I just did a test search, and noticed all of the results were the second template, Agenda & Minutes- Pre-2024.

Is there a better way to setup this search?

0 0
replied on June 9

WebLink should be putting parentheses around your clause to prevent this - it should be interpreted in the end as "A & (B | C) & C". I'll let the team know to investigate and file a bug. In the meantime, I think you should be able achieve the same effect by adding parentheses in the middle clause itself.

0 0
replied on June 9

So, add paranthesis to the first custom line, to be ({[Agenda & Minutes]} | {[Agenda & Minutes- Pre-2024]})

0 0
replied on June 9

One more question, can field names be used like tokens (in this case "Date of Meeting"? If so, I may try one long search syntax, calling on the date field and text

0 0
replied on June 9

Right, that's where I was suggesting the parentheses go. I think you can use a token the way you are describing, but I don't have a copy right now to test with.

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

Sign in to reply to this post.