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

Question

Question

Workflow Could not phrase as date

asked on June 19, 2018 Show version history

Hi Everyone

 

I have this problem with a workflow where it does not want to pass my Date values to a Forms Process. I am passing them using set bp variables. All fields are the same format as the server dd/MM/yyyy. It will pass all values up to 12 for the dd Field and push the rest back as could not be phrased. 

 

Below Screenshot of field and Workflow message.

Anyone had this before?

 

Thanks, Guys

ice_screenshot_20180620-062536.png
ice_screenshot_20180620-063221.png
ice_screenshot_20180620-064044.png
0 0

Replies

replied on June 20, 2018

Take a look at this related Answers post, it may be a similar issue.

https://answers.laserfiche.com/questions/143579/Workflow-dates-from-forms-cannot-be-parsed-back-into-forms

0 0
replied on June 20, 2018

Date format settings are per Windows user. Please check what your Forms and Workflow services are running as and double-check the Windows date format for those users. It looks like the Workflow Service is running with MM/dd/yyyy format in this case (though the currently logged in user is using dd/MM/yyyy so the Designer has the same format).

0 0
replied on July 9, 2018

Hi, I have pushed the Date format to all the users, with no luck. 


WF keeps telling me that it could not be phrased as a date I have redone the workflow services to be on the local account I am using and no different.

This is really a frustrating problem that no one seems to be able to solve for me.

Have done token formatting broken up into dd, MM yyyy.  and pass the value as an MM/dd/yyyy string to forms in a dd/MM/yyyy format.

Still the same could not phrase as a date.

Please, I need some help with this as its keeping me from going live with a project.

Regards

0 0
replied on July 9, 2018

The warning refers to the Workflow side. What user is the Workflow Server service running under? That's the one whose settings need to be updated.

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

Sign in to reply to this post.