I have a client that occasionally sends hundreds of text documents to quickfields with bad file names. Quick Fields populates a token for a company field based on the name of the file sent to it.

I have hundreds of documents piled up in the document manager that cannot be stored because the value that was put into a metadata field is not one of the items defined on the list of allowed entries for that list field.

The text files were supposed to be sent something like 01 - CompanyA, but they instead sent 01 - CompanyATXT, and the only values allowed for that list field are 01 - CompanyA and 02 - CompanyB.

I've tried the following with no success:

- Adding the bad value to the list in Laserfiche Admin Console, so it becomes allowable to store those documents.

- Creating Assign Token Value or Pattern Matching processes in the document classification, and then running the Assign Documents... from the document manager to try and run the process again.

- Replacing the token in that field under document classification with the correct value, and running Assign Documents...

I'm guessing that Assign Documents doesn't actually run the process again if it's already assigned that classification.

My predecessor set this up to happen in pre-classification, so I think my attempts to fix this in Classification will always fail.

There are hundreds of documents, and the only way to fix this that I've found is to fix the bad entry in the field one document at a time. Is there any way to change the values of a single field for all the documents stuck in document revision because they have a bad value.

I'd even take being able to force the documents to store despite the bad information, because then I can select all the documents in the Client and use 'Fields...' to fix them all at once.