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

Question

Question

Quick Fields - Field date format not working

Quick Fields
Updated July 7, 2016
asked on July 7, 2016

I used the Token Editor to set a format for the date in the Invoice Date field, but it is not bringing the result in as expected:  The result is still 16-06-08, even though it is being told to change the format.  This is happening only on this one QF session, not on the others.  (I just upgraded to QF10, and this is my 4th or 5th session I've run since them.)

 

0 0

Replies

replied on July 7, 2016

To clarify, are you saying that this exact same session used to work as expected for dates in the same format as "16-06-08"? What version of Quick Fields did you have previously?

0 0
View 3 previous replies
replied on July 7, 2016 • Show version history

I believe so, yes, these fields formatted properly before.  I've now worked on two other sessions, and found one more not formatting properly.  These sessions are all for invoices that we receive once a month.

0 0
replied on July 7, 2016

Where does the original date value come from? For example, is it captured from the document using Zone OCR? Or perhaps OCR and then pattern matching?

I assume it works correctly for a format like "2016-06-08" (instead of "16-06-08")?

0 0
replied on July 7, 2016 • Show version history

Actually, after looking into this a little further I noticed that the way that Quick Fields interprets the date in these situations is dependent on the formatting of the computer's date. 

Are your system date and time settings the same as they were before you upgraded to Quick Fields 10? For me, after I changed my computer's short date format from "M/d/yyyy" to "dd-MMM-yy", the example in your screenshot now works as expected. 

1 0
replied on July 7, 2016

Rats, I thought you were onto something there, Tessa, as our computers are all brand new as well.  But, I changed the format for dates in my computer to what I always had before and, no change.  It still comes up 16-6-22.

In answer to your question above, the original date value comes from a Zone OCR, which then is handled by a Substitution activity.  The original shows up as 6/22/16.  Then the substitution activity makes it 16-6-22 and my field should be able to convert that format just fine (and does so on most other saved sessions).  The field's token editor is supposed to change the 16 into 2016, but it isn't (see first post for the field token editor's programming).

0 0
replied on July 7, 2016

Did you reopen Quick Fields after changing your computer's date format?

1 0
replied on July 7, 2016

Tessa, that was it!  It is working now.  Thank you!!

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

Sign in to reply to this post.

Details
Related Posts
Loading ...