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

Question

Question

10.2 Forms changed date format?

asked on March 17, 2017

Hi, I just upgraded to 10.2 Forms and have issues with dates. The date format changed from mm/dd/yyyy to m_d_yyyy

 

Any way to fix this instead of trying to fix all of my forms and all workflows? Thanks!

0 0

Replies

replied on April 29, 2017

This is  a big problem for me too.  I just upgraded to 10.2 and most of my forms save folders to the repository using a date field formatted at mm/dd/yyy.  So now none of my workflows are working because save to repository is changing the date format to m_d_yyy.  This is "big problem" if I have to change the logic in all of my workflows.

1 0
replied on March 19, 2017

Hi Lidija, I can reproduce this for date tokens used in file names and paths in a Save to Repository task, when the recent Update 1 to Forms 10.2 has been applied. So far as I can tell, when used in a metadata field or when displayed on a form during submission, the date format has not changed and respects settings. I'll pass this on to the team; for completeness, was there another implementation of this which you were encountering which is interfering with your process?

0 0
replied on March 20, 2017

The problem is with the Save to Repository task. We have a lot of forms and workflows that have dates in the file names. Unfortunately this is not a small adjustment to make, is there any ETA on a patch when this might be fixed?

0 0
replied on March 20, 2017

Thanks for confirming. SCR 155679 has been filed for this, but I don't have an ETA at this time.

0 0
replied on March 24, 2017

James, is there a workaround that I can use until this gets fixed? In the database the date format is correct so I am really puzzled why it is forcing the underscore date format. 

 

Thanks!

0 0
replied on March 24, 2017

The issue is specifically with the Save to Repository task, in particular overzealous sanitizing of file names (as '/' and ':' are invalid characters for Windows file system, but not for Laserfiche repository). I haven't tried implementing such a workaround yet, but perhaps a workflow monitoring the save locations could try renaming the files, since the names would be in a standard format?

0 0
replied on April 24, 2017

Hi James, any updates? Also where can I go to checkout the status of the SCR?

0 0
replied on May 30, 2017

James did this also impact Save to Repository tasks which use an *? Since upgrading, it appears to use an underscore instead.

*Processes

becomes

_Processes

 

Cheers,

Carl

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

Sign in to reply to this post.