Hi Mary Lou, good to hear from you!

I've reread your question a few times and if I understand correctly you're saying that the exact case of the Quickfields data is being stored in the actual entry in Laserfiche despite the list view showing a different case. The data capture and storage is working correctly, just in the wrong case.

If that's true then the first thing I can think of is to use an Assign Token values to create a new token which you can use the Function ability of tokens to modify the case. Again, this is just by memory right now but you might have to use a regular expression with function to make each possible value the correct case that you want and put them all into one token string. Since only one of them would contain a value you'd end up with the correct value in the correct case as a token and that's what you'd store to the list.

Using a Conditional would be even better but you don't own Document Classification I believe which is required for use of Conditionals.

Finally, you could store the case then at the end of the Quickfields session have it invoke a workflow that would read the field and use a token function to modify the case and store back to the field.

Give me a call next week if you need clarification or further assistance with this.

I actually tried this before asking the questions.  The problem arises because I have acronyms in the list filed that are preferred in all caps, and I also have standard words that have a preferred format of sentence case.  If I edit the token to sentence case, it changes the acronyms.  If I puts all caps, it goes against the traditional format.

Your right about the conditionals, it would help immensely; but we do not have Document Classification.

I think I will just hide the field and deal with it behind the scenes.  There are only a few people who use the actual metadata field.  I will just use  practices similar to Transparent Records Management and make a folder to separate the items for those who usually sort by this column of metadata when searching.  This seems to be when the issue is brought up due to the inconsistent lettering.