Entry Not Routing based on Date Field

asked on January 19, 2018 • Show version history

I'm attempting to route an entry to a folder path partly based on a date field, using the year and month as part of the folder structure (e.g. FolderX\YYYY\Month\Last, First-DOB). While this is a MV field, I'm only looking at the first value and will route based on that value.

The folder appears to be routing but skipping the date-based folders entirely, so instead of FolderX\2018\January\Test, AppA-01/01/2000 I'm just getting FolderX\Test, AppA-01/01/2000. I've attempted to create/route the entry with various users that have different access rights/permissions and I can't lock it down to any of those things.

20180119_TAP_Routing.JPG (26.59 KB)

| Download

0 0

replied on January 19, 2018

Since you are manipulating the date in the token creation section, are you marking the new token as a date in token tags?

0 0

View 4 previous replies

replied on January 19, 2018

Yes

0 0

replied on January 19, 2018

Odd. What if you use the token from the retrieve field values activity, but locked down to the first value?

0 0

replied on January 19, 2018

I tried that too...same result, which is why I tried the token route. Is it possible it's a field issue? I reference the same field in another workflow to route a shortcut and it does the same thing (doesn't reference the date for the folder structure).

0 0

replied on January 19, 2018 • Show version history

Can you show the set up of your tokens? If you look at the workflow instance are you tracking tokens so you can go back and see how the token is reading? The problem might be that the token value stays blank.

0 0

replied on January 19, 2018

the Serial count is a string and the Date is a date

20180119_TAP_Routing_Tokens.JPG (20.64 KB)

| Download

0 0

replied on January 19, 2018

What does the history show on a workflow that you have run? Have you ruled out the possibility that the token is blank (and therefore can't use it in the folder path)?

Have you tried doing two tokens and pulling the sections there instead of 1 token and manipulating it in the path construction?

Checktokens.jpg (86.21 KB)

| Download

DateTokens.jpg (15.65 KB)

| Download

0 0

replied on January 19, 2018

Jennifer - you're right, the token was blank. But what I don't understand is why. I replicated the Date Issued field as "Date Issued2" and re-ran the workflow using that field. The Date Issued2 token was filled just fine. I guess I'll just update my workflow with the new field.

I still don't understand what happened to the original field. It was also working just fine a couple weeks ago.

0 0

Question

Question

Entry Not Routing based on Date Field

Replies

Sign in to reply to this post.