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

Question

Question

default for datetime type Fields not filling up

asked on April 13, 2022

when setting up a default value for any datetime fields, the default values are not being applied, via workflow or direct LF web view.

The workflow adds the field via a template ("Assign Field Values" activity) and it remains blank.  In the LF web view, I manually add the field and it also remains empty.

I tried using a literal date (1901-01-01 12:00:00 a.m.) and %(Datetime) token and both react the same.

In the same environment, I tried using a string with a default value and that worked as expected.

using LF 11.0.2102.175

 

is there a trick? or is this a bug?

 

0 0

Answer

SELECTED ANSWER
replied on April 14, 2022

There's no delay, Once you save the changes to the field in the admin console, they should be reflected immediately when applying the field to a document.

1901-01-01 12:00:00 a.m. works for me as well (even though my SQL Server and LFServer are running with US date formats where, technically, "a.m." is not the expected AM/PM indicator).

It's probably best that you open a case with Tech Support so we can take a closer look.

0 0

Replies

replied on April 13, 2022

Are you setting the value in Assign Field Values? Workflow does not use the default value specified in the template. Do you see any warnings or errors in your Workflow instance details?

0 0
replied on April 14, 2022 Show version history

well today, I redid tests and it automagically started to work in all use cases. surprise

This is very strange, yesterday I did tests for at least 30 minutes and the following two panels, which I created in the same work session, behaved differently, based on their type.

With today's sudden magic, it seems like there is a delay between the changes in the Admin console and their activation in the server.

 

can you confirm that it is expected for a long delay  (possibly an hour, or more?) between setup and activation?

 

Setup was done in the desktop LF Admin Console under Metadata Management / Fields

This worked immediately:

This didn't:

When I looked under the template manager, the default value was setup and reflected the value I placed in fields.

0 0
SELECTED ANSWER
replied on April 14, 2022

There's no delay, Once you save the changes to the field in the admin console, they should be reflected immediately when applying the field to a document.

1901-01-01 12:00:00 a.m. works for me as well (even though my SQL Server and LFServer are running with US date formats where, technically, "a.m." is not the expected AM/PM indicator).

It's probably best that you open a case with Tech Support so we can take a closer look.

0 0
replied on April 14, 2022

ok thanks for the answer, if I have the behavior again, I'll be sure to open a support ticket.

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

Sign in to reply to this post.