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

Question

Question

'Reset' button (in the Search window) doesn't wipe out Template Field values

asked on May 18, 2015

A customer just reported this behavior in version 9.0.2.685, and I have verified the behavior in 9.2.1.  If you do a Template search in the LF Client, populate some of the fields with search criteria, perform your search, and then click the 'Reset' button, the search criteria returns back to the 'default' search, which is a combination of the Basic and Within Folder searches (see Figure 1.png).  However, if you close out of both of these searches and select the Field search again, all of the template fields are still populated with the search criteria from your prior search (see Figure 2.png).  Shouldn't the 'Reset' button wipe out these field values?  That's the way that it works in both WebLink and Web Access...but not in the client.  

 

This is causing a problem for the customer, as their template has many fields, and they are having to manually clear out each of these fields every time they want to perform another field search.  They were recently upgraded from v7, and claim that the Reset button DID clear out the field values in v7, but it has stopped working since the v9 upgrade (I don't have a v7 system that I can test it on at this time).

 

Is there any way to automatically clear all of the search criteria from the template fields?

 

Thanks,

Mike Rizzo

General Code

Figure 1.PNG
Figure 2.PNG
Figure 1.PNG (17.21 KB)
Figure 2.PNG (27.65 KB)
0 0

Answer

SELECTED ANSWER
replied on May 18, 2015

Yes, this would be considered a bug. I don't have a timeframe for it at this time. 

1 0

Replies

replied on May 18, 2015 Show version history

Yes it is a bug. We can easily reproduce it based on your description.

It is however a new bug so there is no timeframe for when it will be resolved. The SCR for your reference is 127957

1 0
replied on May 18, 2015 Show version history

If you close the client and go back into it, the fields should be empty.  You can do that as a workaround.

I am opening a case for your for this issue. 

0 0
replied on May 18, 2015

Thanks Raymond.  I understand that closing and re-opening the client will wipe out those values.  Would this be considered a bug?  If so, is there any estimated time as to when we can expect a fix?

0 0
replied on May 18, 2015

Great, thanks guys!

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

Sign in to reply to this post.