Question

Quick Fields Date token tomorrow

Quick Fields

Updated November 9, 2017

asked on October 17, 2017

We are scanning in items to Quick Fields, and we hard code the date every time we run a session for tomorrows date.

Is there a way to use a token to use tomorrows date? I can pull today, and if i use today+1 it actually pulls yesterday's date. -1 pulls yesterday's date as well.

0 0

Replies

replied on October 17, 2017

Huh, this is an interesting one

What you're seeing isn't actually any built-in behavior to increment the date in Quick Fields - I think it's actually getting interpreted as a time zone adjustment. This is definitely a bit of a "hack", but if you want it to show the next day then I think you can do that by starting with the %(Date Time) token and subtracting the sum of 24 and your time zone's UTC offset .

For example, here in California my computer is set to the PDT timezone where the UTC offset is -7, and 7+24 = 31, so when I configure the date field like this:

It puts tomorrow's date in the field, as shown below.

Out of curiosity, why do you want to run a session for tomorrow's date?

1 0

replied on October 19, 2017

OK, so a bit of a trouble with this. Maybe you have an idea how to fix this.

So the formula worked and completed the metadata field properly.

However, i have the file named with a tokens from Quickfields, of field date and name. The metadata field is right, but the naming convention was not.

metadata.jpg (33.67 KB)

| Download

Label.jpg (61.35 KB)

| Download

0 0

replied on October 17, 2017

This worked perfectly.

We use the date field to name the file, and as a token in a workflow email. We scan in payroll bundles to be emailed to the employees with details of their payroll. We scan them the day before they get paid, so all of the details show tomorrow as their pay-date.

0 0

replied on November 9, 2017

Anyone have thoughts?

0 0

You are not allowed to follow up in this post.

Question

Question

Quick Fields Date token tomorrow

Replies

Sign in to reply to this post.