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

Question

Question

Need to remove a multi value field

asked on May 10, 2013 Show version history

 

We have a field that was marked multi value by accident, when it should have been single value.  Then, someone added a two values to at least one of the documents.

 

Now when we try to revert the field back to single value, it issues a warning.

 

What is the best way to identify which documents have more than one entry in a multi value field?  Once we edit the extra values, I assume I'll be able to set the field back to single value -

2 0

Answer

APPROVED ANSWER
replied on May 29, 2013 Show version history

You can find these entries by doing the following advanced search:

 

{[]:[Field](2)="*"}

 

Where Field is the name of the field you’re working with. This will return all entries that have at least two values in that multi-value field.

 

Note that this will not return entries that are in the recycle bin. You may want to purge those first before trying to change the field back to a single-value field, or you might get the error again.

 

I hope this helps. Let us know if you have any other questions.

2 0

Replies

replied on May 29, 2013

I followed the advice on finding the additional values in an MV field. 

 

Now when I try to convert the MV to single Value, I get an error:

 

The field definition cannot be changed because one or more of the entries exist with values in the version history.

 

So I searched for documents with the correct template, with version information, and sorted the results by version history.

 

For the ones with a version history, I deleted the prior versions.  (the user had no need to version these items, not sure why she did.)

 

But, I still get this error -

 

Is there a way to remove a document from versioning altogether, once someone has started that?

1 0
replied on May 29, 2013

There is no way to remove a document from versioning. That said, it is possible that there are some entries in the recycle bin that are preventing the field from being converted to single-value. You can find them by using the methods Justin Pava explained on the last post onthis forum thread. Better yet, you can just straight-up purge those documents, if possible.

 

If that doesn’t fix the issue, you may want to upgrade to version 9.0.2. The Laserfiche Server handles this situation much more elegantly in that version.

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

Sign in to reply to this post.