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

Question

Question

Date token calculator support with dd/M/yyyy

asked on January 14, 2016

For AU region our dates are in dd/M/yyyy format

An AP account workflow needs to determine a future payment date by adding days to the invoice date.

Different vendors have different payment terms eg. 7 days, 15 days etc

 

using the invoice date as 20/12/2015 (20th December, 2015) and adding 15 days the token is empty and the workflow message "string was not recognised as valid Datetime" is returned.

 

Can a conversion or format option be applied to generate a valid date or does DateToken calculator only work in M/dd/yyyy format?

Thank you.

0 0

Answer

SELECTED ANSWER
replied on January 18, 2016

I don't work in Tech Support, so, no, I can't connect to your machine. You can open a case with Tech Support if you need more hands-on help.

The Windows regional settings are per Windows user, so depending on what user you use for the Workflow Server's service account, they may not be the same as the regional settings for the user you're logged in as.

0 0

Replies

replied on November 19, 2017

Hi,

The Date format works on the WF Server Date Settings, you can format the pattern and split the day / month /year as per your date format requirement

using Apply Regular Expression

Day = \d{2} 

Month  = /(\d{2})

Year = /(\d{4})

 

 

 

Concatenate the  Day // Month // Year as a Token and format the date pattern as dd/MMM/yyyy, now you will get the date as 20/Dec/2017. Use Token calculator for add the No. of Days.

 

Hope this will solve your issue.

1 0
replied on April 7, 2019

Thanks Ganesa

For a particular customer I was unable to confirm if the customer had set the workflow service user date format to dd/MM/yyy or the region to Australia.

So I used your Pattern Matching as you outlined above.  

0 0
replied on January 15, 2016

The date format used on the Workflow server follows the Windows date format. The Date Token Calculator works with both MM/dd/yyyy and dd/MM/yyyy dates based on said Windows date format.

If you are using mixed date formats, you can format the values to the Windows format before adding them.

0 0
replied on January 17, 2016

Hi Miruni,

Thank you for your reply.

The Windows date format has been set in Regional settings to dd/MM/yyyy.

The system clock and Windows Explorer 'modified' and 'created' date columns all display as dd/MM/yyyy

but the message as stated is occurring.

 

Could you please confirm the settings locations you mean to set set 'Windows date format'?

Are you able to connect to my workstation remotely to see the error?

 

many thanks

0 0
SELECTED ANSWER
replied on January 18, 2016

I don't work in Tech Support, so, no, I can't connect to your machine. You can open a case with Tech Support if you need more hands-on help.

The Windows regional settings are per Windows user, so depending on what user you use for the Workflow Server's service account, they may not be the same as the regional settings for the user you're logged in as.

0 0
replied on January 18, 2016

I am using Localsystem for the workflow service. I changed it my administrator account instead and now the date calculation is working.

This confirmed the Localsystem account was not in Australia region as you said.

The settings shown in the screenshot were changed and now it works with Localsystem also.

many thanks for your help

0 0
replied on November 8, 2017

Further to this issue I have just recently experienced this on Server 2016 and to get the date working correctly in workflow I had to;

1. Set language Australia as default.

2. Change date, time, or number formats>Administrative>Copy settings

3. Check both boxes to "Copy your current Settings to; (see image)

Once this is done it all works!

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

Sign in to reply to this post.