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

Question

Question

How do I remove an extra field slot with multiple values?

asked on May 26, 2022

So at some point in the last week or two I somehow accidentally turned on "Allow multiple fields" on a date Field. I am in the process of building a Forms process that uses that field as part of a collection and I'm finding that it's applying all the data from that Field in the collection regardless of [ROW()] being applied and working everywhere else and I can only assume this is due to the field allowing multiple values.

I found out how to search for documents with multiple values in the metadata and I see clear as day

Date

xx/xx/xxxx     > X

   /   /             >

I can't turn off Allow for Multiple fields until I've removed every instance of it but I don't see a way to remove just the bottom empty field. 

I know I could make a workflow that would take all that info, move it to another field, then I can delete the field and remake it but this seems like a lot of work when there should just be an X to remove that second row.

0 0

Answer

SELECTED ANSWER
replied on May 27, 2022

I think your search is missing something because I just double checked and I was able to change a field back and forth without any issues as long as I didn't have more than one value in any instances of that field.

Try searching specifically for something with items in the second row

{[]:[Effective Date of Document](2)="*"}

The (#) is an index to target specific items in a multi-value field collection.

Tech Tip: Searching for Multi-Value Fields, Part Two (laserfiche.com)

0 0

Replies

replied on May 27, 2022

The bottom empty field you see in the client is not actually a stored value unless you see an X icon to the right of it; it's just a placeholder so you can add more values.

The UI for metadata doesn't have an "add item" kind of option, it just shows a placeholder for the next row so you can add more values.

If you retrieve the field in a workflow and loop through the values, it won't have a blank value as the last item unless you intentionally stored one.

For example, in the screenshot below, only the items with the X are stored values, so if I retrieve that field in workflow I'd only get 3 results not 4 ("Item 1", "", and "Item 3").

1 0
replied on May 27, 2022

How do I turn off the "Allow multiple values" option on the date field then? I can't find a single item that has anything in the second slot when using a search parameter of {[]:[Effective Date of Document]="*"} |{[]:[Effective Date of Document]="*"} 

I get 621 results and when I bring up their fields I see this

0 0
SELECTED ANSWER
replied on May 27, 2022

I think your search is missing something because I just double checked and I was able to change a field back and forth without any issues as long as I didn't have more than one value in any instances of that field.

Try searching specifically for something with items in the second row

{[]:[Effective Date of Document](2)="*"}

The (#) is an index to target specific items in a multi-value field collection.

Tech Tip: Searching for Multi-Value Fields, Part Two (laserfiche.com)

0 0
replied on May 27, 2022

Oh, yeah that looks better but still no dice. Both {[]:[Effective Date of Document]="*"}&{[]:[Effective Date of Document](2)="*"} and just {[]:[Effective Date of Document](2)="*"} come back with nothing. I wonder if it's on a deleted item. I'm going to check there.

0 0
replied on May 27, 2022

Yeah found them in the recyling bin, but I can't restore or purge them as an Ancestoral folder has been deleted, whatever that mean. I'm currently trying to restore deleted folders one by one to see if I can restore those files and remove the fields. This will take a bit but it should be solved.

0 0
replied on May 27, 2022 Show version history

A deleted item could very well be the culprit since it would still be in the database until it is purged.

Right-click the Recycle Bin, open the search, and you can use the Syntax there too as long as it says "Search Recycle Bin" at the top of the left pane.

The syntax I provided should work as-is; adding more is just going to slow it down.

{[]:[Effective Date of Document](2)="*"}

0 0
replied on May 27, 2022

Yeah it is, I can't purge them until I've restored their original folders, so I'm slowly restoring folders bit by bit but we should be set.

0 0
replied on May 27, 2022

Unless you know how to force a purge of the recycle bin.

0 0
replied on May 27, 2022

If you right-click the item(s) there would be a Purge option unless you don't have the necessary permissions.

0 0
replied on May 27, 2022

I didn't screen shot the error but when I tried to purge or restore I got a pop up telling me I couldn't do that do to the Ancestor folder no longer existing, even if I tried to restore to a new location. I had to start restoring folders from the top down, but once I figured out which folders needed to be restored first it all fell into place. I've restored everything, removed the field and made the change to the Field and it all works well, thanks for the help!

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

Sign in to reply to this post.