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

Question

Question

Weblink 10 - Not minding the parent field configurations

asked on February 1, 2018 Show version history

I have parent field configurations configured under dynamic fields so that the options are narrowed based on previous selections. It works correctly from the Laserfiche client, however in Weblink 10 it disregards it entirely.

0 0

Answer

APPROVED ANSWER
replied on February 2, 2018

This is an issue we're aware of (Bug 29981). As a workaround for now, you can do the following:

  1. Backup the Search.aspx file from C:\Program Files\Laserfiche\WebLink\WebLink\Web Files to a new folder or rename it to something like Search10.aspx.
  2. Rename the Search9.aspx files to Search.aspx

Now searching in WebLink 10 for templates with dynamic fields should respect the configuration.

1 0
replied on February 5, 2018

It is working here: http://localhost/weblink/Search.aspx

But not on the custom searches here: http://localhost/weblink//customsearch.aspx

0 0
replied on February 5, 2018

Custom searches in WebLink still don't support dynamic fields. This is still a pending feature request. (Enhancement Request 29994).

1 0
replied on February 5, 2018

Oh, ok. I was trying to see if there was any way to have sorted lists in Weblink.  When I select to sort the list in Administration Console, it sorts it one time, then automatically switches back to static. The solution provided was to use dynamic fields, but if they are not supported then I take it, there is no way to have sorted lists.

0 0
replied on November 28, 2018 Show version history

Having some troubles getting this to work. I have changed both Search.Aspx files to match what you suggested but now I get a .net error whenever any search is run; was this due to an update between now and February? Is this workaround still possible.

Edit: This workaround does not work for WebLink 10.1.0.60 but does in updated weblink 10 versions. 

0 0

Replies

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

Sign in to reply to this post.