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

Question

Question

Forms date format for Lookup

asked on July 27, 2016

Hi all,

Just been having some difficulty this morning on a form which uses a client's Surname and Date of Birth to lookup the client's unique reference. On further inspection the lookup didn't seem to work because we had the date field set to the English date format (dd/mm/yyyy) however changing this to the American format (mm/dd/yyyy) seems to work fine. Does Forms 10.1 currently support lookups using the English date format?

Any input would be greatly appreciated! laugh

Cheers, Dan

0 0

Answer

SELECTED ANSWER
replied on July 27, 2016

This is bug for Forms 10.1, we will address it for next release.

0 0
replied on January 12, 2017

The issue "match date field with dd/MM/yyyy can't get lookup result" has been fixed with Forms 10.2

0 0

Replies

replied on November 4, 2016

It may be unrelated but I have a form that collects a date in UK (dd/mm/yyyy) format before passing that to workflow which inserts it into a database. In doing so the day and month are flipped so 4th November becomes 11th April. I've checked the regional setting and everything looks in order.

If I store the data in a template field as part of the save to repository task then the date is transferred correctly so not sure if it Forms or Workflow where the error is being introduced.

 

0 0
replied on November 6, 2016

Hi Nigel, your issue is unrelated to the original issue which is for lookup. In Workflow, the format of the date should follow the regional settings for the account that run Workflow Service no matter what format of the field set in Forms.  For your issue, please check whether you have used For Each Row activity in Workflow to retrieve the data, if do, then the issue is related to For Each Row activity doesn't follow the Workflow Service's regional settings(This is a known issue for Workflow, will be addressed in next release). You can use For Each Value activity as workaround.

1 0
replied on December 19, 2016

This came up again for another client - is there any other workaround other than switching to US date format or using the For Each Value activity? The latter doesn't really help here as we're retrieving data from a table within the form which as far as I know is the only way to retrieve such data?

We've tried using various date formats, and formatting the date tokens before inserting but it appears that the For Each Row activity discards any date not valid according to the US format.

0 0
replied on December 20, 2016

You still use Retrieve Business Process Variables to get the date from Forms, but after that activity, just need to replace the For Each Row Activity with the For Each Value activity and set this activity to get the value for the date token get from retrieve business process variables(some token like this "%(RetrieveBusinessProcessVariables_Table\Date)"). This activity will respect the reginal settings for the account that run the workflow service.

Following are the steps I tested with:

1. Login the workflow server with a windows user, go to regional and language settings from control panel and change the format to English(United Kingdom).

2. open Services, and change the "Laserfiche Workflow x.x" to log on as the windows user and restart it

3. create a workflow as following to retrieve a date field in a table from forms and send the value for the date via email

 

The value got from email is "20/12/2016" which is in dd/MM/yyyy format.

0 0
replied on February 8, 2017

Hi Xiang,

My customer has a similar issue with the For Each Row activity retrieving the incorrect region format.  You previously stated:

"For your issue, please check whether you have used For Each Row activity in Workflow to retrieve the data, if do, then the issue is related to For Each Row activity doesn't follow the Workflow Service's regional settings(This is a known issue for Workflow, will be addressed in next release). "

My customer is using 10.1.0.642.  Could you please tell me what next release you are referring to?

0 0
replied on February 9, 2017

This was resolved in Forms 10.2. It does seem that you still need to use a formatting mask like #yyyy-MM-dd#  when inserting the date values though.

0 0
replied on February 12, 2017

Hi Xiang,

As this is a warranty issue for our customer, I need a confirmation from Laserfiche that this issue has been fixed and what Workflow version is required.

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

Sign in to reply to this post.