Is there anyway to search "*" or "no value" in a field search using the regular search and not advanced? This is for production users.

Hi Ali, 

No there isn't, although you could create a custom quick search or saved search to make it simpler. 

Can you provide some information on what the scenario is where the users need to regularly make this search? It sounds like their just looking for all documents that have a specific field assigned to it in the first place - what's the business case for this? 

Hey Justin,

Basically, the users want to have (4) fields to search from -- ADDRESS, BLOCK, LOT and QUALIFIER. The ADDRESS field is always filled out (don't ask me why they don't just search on ADDRESS explicitly). So, if they search on "184 CUTTER AVE", they want all results shown even if some of the fields are empty -- which is the issue, because some are actually empty. See screenshot. 

Hrm, is the main goal specifically to have the other columns show up in the search results? The upcoming Web Access 10.1 allows users to specific a column profile as part of their search, as well as assigning one to a shared search. So you could have a column profile that includes all of these fields and then they always show, even if the user doesn't include them in the search. 

If the main goal is simply to be able to provide all 4 fields to the user, you could do that by displaying all 4 as a field search in the UI as a saved search - if the user doesn't care about a particular one, they can close it and then reload the saved search each time. 

Justin,

Bottom line is, they want the individual Field(s) search to produce the same results a Template search would. In their mind, its the same exact search, but produces two totally different results...   

Justin,

Are we correct in the way these searches function?

Also, were the multiple Field search restrictions the same in Laserfiche 9 (as our customer is using Laserfiche 10)? 

Please let me know ASAP.

Thanks,

Ali

This is unchanged between Laserfiche 9 and 10. I believe this has been the behavior of the field specific search since it was introduced in version 8. 

Thanks Justin... any chance this gets changed in future versions? 

Hi Ali,

We're always looking to be responsive to customer requests. That said, it'd help if we had more specifics as to why it has to be changed in this manner beyond 'the customer insists on doing that' especially when - as you noted - it doesn't seem like they necessarily have to. That's not intended to be sarcastic, we just need to always judge the possibility of changes to existing functionality adversly impacting other customers who are already relying on the current functoinality (that's certainly happened in the past) so I want to ensure such changes are neccessary. 

Justin,

I have confirmed that the FIELD search functions differently in WebAccess v9 than v10.  So it now seems that we have lost individual FIELD search functionality after upgrading our customer from WebAccess v9 to v10. Retaining this FIELD search functionally is imperative to all of our NJ municipality customers as they rely heavily on block/lot searches regardless if certain fields are left blank. Here are screenshots of an individual FIELD search in both WebAcess v9.2.1.673 and v10.0.0.994 with different results:

6 documents in the v10 repository with the following field info...

Searching for block "7" in a FIELD(s) search produces NO RESULTS...

Same 6 documents in a v9 repository with the same field info... 

Searching for block "7" in a FIELD(s) search produces 5 documents (as it should)...

Please let me know how we can resolve this issue ASAP.

Thanks,

Ali