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

Question

Question

Changing the Date Format In a Quick Field Sessions

asked on August 21, 2014

Okay, I am still learning so any help would be much appreciated.  Okay, I have a session that I'm trying to change the "Pay Date" from Dec 1, 2013 to 12/01/2013.  I have inserted a snip it of my task pane and my configuration pane.  I am using a OCR zone to read date.  Then I'm using a token dialog, but not working. When test after apply formatting, it works.   Should I be using a substitution process or pattern matching?  The two get me a little confused and when and when not to use.  I thought I could "add" a token with Token Dialog.  I am running QF 9.

 

Thank you

Garnishment Task Pane.PNG
garnishment session confige.PNG
0 0

Replies

replied on August 21, 2014

From your screenshot, it looks like you're using the Zone OCR value to populate a date field. Quick Fields will automatically convert date values to the system's date format. So you shouldn't have to do any formatting. You can use the field token in the document name so it will use the same value too.

0 0
replied on August 22, 2014

Thank you for prompt response.  Yes, I'm using Zone OCR to read date on sample sheet (see attached Garnishment Pay Date Zone PNG.  It seems QF did not automatically convert my date format from Jul 17, 2014 to 7/17/2014.  Please see Garnishment Revision Pane.  Also attached my task pane again to show that I do have my field with Zone OCR %(Pay Date).  Any other suggestions would be most helpful.

Garnishment Pay Date Zone.PNG
Garnishment Task Pane.PNG
Garnishment Revision Pane.PNG
0 0
replied on August 22, 2014

Okay Miruna,  I just tried again.  Thought, "Hey it is going to work"  Please see attachments.  What happened?

Garnishment Revision Pane.PNG
Garnishment Task Pane.PNG
0 0
replied on August 22, 2014

Hm, the fact that the date gets converted to 1/4/2014 might indicate that Zone OCR is reading extra spaces or something else that's confusing date formatting. But it's hard to tell from screenshots. Could you have your reseller open a case with Tech Support and attach a sample image?

0 0
replied on August 22, 2014

can you show us the token in the document class before it's identified and used? maybe you should try applying some formatting to the token itself to make it how you wanted. if you are already formatting the token, i would recommend seeing what it was before, then using that value in the area to test the token and seeing if maybe you set that formatting up improperly.

0 0
replied on August 26, 2014

Kenneth, attached you will see how I tried to format token.  Test shows it is correct--worked.  Also attached is my token for Pay Date, unformatted.  When I left the token as %(Pay Date) it worked, but the date was reading wrong.  See my reply to Miruna.  I know it has to be something real simple I am overlooking.

My document in the revision pane comes back as untitled.

Formatted Token with Test Results.PNG
Token Before Format.PNG
0 0
replied on August 26, 2014

I wonder if maybe the title is taking it from the first time the token is filled and the token keeps changing while being processed causing the token to fail for the field. 

 

Or, maybe that field itself has some formatting assigned to it about how it shows the date. that could be taking out some information oddly

0 0
replied on August 28, 2014

Thanks Kenneth,  I will talk to our LF Admin.  You have me thinking that maybe the date format set up in LF isn't 00/00/0000.  I noticed when I open the LF client where these documents are being stored, even though I enter (manually) 00/00/0000, when stored it is 0 /00/0000.  Like the extra space in month is optional.  Does that make sense?  I know the OCR Zone itself is working because of the "test the process" after I format my token.  I will let you know.

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

Sign in to reply to this post.