Question

Quick Fields Document Naming

Quick Fields

Updated March 26, 2015

asked on March 25, 2015

I have a session where I want to name the document and at times some of the fields maybe blank - which is okay if they are I want it to only use the fields that are not blank.

Here is my format:

%(Fields.Week) - %(Fields.Tax Code) - %(Fields.Company Name) - %(Fields.Filename)

Week and Tax Code will always be available, but Company Name and Filename may be blank. Is there something I need to change in my format or is there a setting to allow for this to happen?

I do not have QF Classify at this time (we are purchasing QF Complete soon).

Thanks, Robin

0 0

Replies

replied on March 25, 2015

maybe you can have a workflow pick up any new documents coming in from that session and evaluate if those fields are filled or not and rename the document.

That is just one way to accomplish the task though. Can you clarify the situation with more information so a solution best fitting your situation may be more evident than this suggestion?

1 0

replied on March 26, 2015

Ok, I have been modifying Tokens and Pattern Matching and when I finally get it to look the way I want it to, but now it won't send to the repository. I keep getting "Invalid object name", what does this mean? And I am getting no explanation as to WHAT object it is talking about.

Attached are what my tokens look like as well as my fields:

Refund Images - Token Capture for fields.JPG

Refunds - Fields captured with tokens.JPG

Refunds - Weekly Coversheet.JPG (20.09 KB)

| Download

Refund Images - Token Capture for fields.JPG (48.28 KB)

| Download

Refunds - Fields captured with tokens.JPG (49.69 KB)

| Download

0 0

View 7 previous replies

replied on March 26, 2015

I think your FILENAME pattern is including the newline character (because of the .*), which makes for an invalid document name. Try changing it to FILENAME\s*([^\n]+)

1 0

replied on March 26, 2015

That fixed the Filename issue, but I am still getting the "Invalid Object Name" when sending the documents to the repository.

0 0

replied on March 26, 2015

pretty sure its because of the comma in the name. Might be something else but try removing that.

0 0

replied on March 26, 2015

Well, I've tried it with and without and it still sends the "Invalid Object Name".

Thanks!

0 0

replied on March 26, 2015

Commas are fine.

TXCODE and CONAME also include a newline character. Data read by Zone OCR ends lines with \n\n. Change the \n in those 2 patterns to \n\n. Or change the .* to a [^\n]* (ie, from "any character" to "any character except for the newline character").

1 0

replied on March 26, 2015

Miruna,

Here is what I have after making your changes:

Refunds-Token Capture after changes.JPG (43 KB)

| Download

Invalid object name(after changes).JPG (41.1 KB)

| Download

0 0

replied on March 26, 2015

Filename works great, did I change the TAXCODE and COMPANY right? Still getting errors when sending.

0 0

replied on March 26, 2015

Just to double-check, these are newly scanned documents after you made the changes, not the same ones from earlier, right?

0 0

replied on March 26, 2015

Correct!

0 0

replied on March 26, 2015

I got it working by taking the TAXCODE and COMPANY out of the Data Zone (Multi line OCR Zone) and creating separate OCR zones for each of them as Single Line, not multi.

Thank you so much Miruna for your help! I learned a lot with your help!

Robin

1 0

You are not allowed to follow up in this post.

Question

Question

Quick Fields Document Naming

Replies

Sign in to reply to this post.