Question

Advanced Search for empty [NULL] string values inconsistent

Search and Retrieval

Updated May 29, 2019

asked on August 21, 2015

After migrating our Laserfiche, which started with version 6 and is now on 9.2, we have both older files and more recent files and I am wondering if maybe the handling of empty has changed over the years or versions of Laserfiche. If I search (advanced search) for Value = "" the results will include only recent documents that have the empty value, but not older ones. If I select all of the ones that SHOULD be returned and assign a value and then select them again and clear that value, then they will all be included in the results of a VALUE = "" search.

Has anyone encountered (resolved) this issue? I wonder if this type of thing also might occur if a new field is added to a template, since any existing documents on that template would never have had a value assigned?

0 0

Replies

replied on August 21, 2015

There is supposed to be a row for every field assigned to a template, for each entry that has that template assigned, in the "propval" table in SQL. Fields that are blank are supposed to have a NULL value in the column for that row. If you know how to query SQL you can query the propval table for a document by getting all the rows where propval.tocid = the entry ID of the document, and checking if the number of rows is equal to the number of fields in the assigned template. If not, we can provide some SQL which will correct this problem.

I am not certain why the migration utility didn't handle this automatically for you if that is what is going on in your case. If you are able to follow up, please do. Thank you.

1 0

replied on August 24, 2015

Michael,

Thank you for your feedback. It was very helpful. I have some testing to do, but I think that I know where our problem lies and I need to test. We had a vendor supplied importation tool that preceded the Import Agent and the earliest version was written before Integrators Toolkit, so it talked directly to the SQL database. I suspect that it created blank strings in our database where there should have been NULLs. All instances of blank string entries that I see are from 2005 - 2009. I will confirm and advise.

0 0

replied on May 29, 2019

Dredging up an old thread...I seem to have this same issue in https://answers.laserfiche.com/questions/159805/Searching-for-Nulls

Would a change between rio 10.2 and rio 10.3 cause this issue?

0 0

You are not allowed to follow up in this post.

Question

Question

Advanced Search for empty [NULL] string values inconsistent

Replies

Sign in to reply to this post.