Hello group!! Today we have noticed that for some records in the table Person, the exitdate is different from its value (e.g) Using the ObjectBrowser and opening the record: ExitDate -> 9/16/2022 12:00:00 AM But if we dropdown the field the property "value" is 9/15/2022 10:00:00 PM We have a custom deactivation process that runs everyday at 2:00 AM, and checks the exitdate less than current date (UTC). So this ends with some employees being deactivated before they should. Any idea how we can solve this issue? Kind regards, David.

This sounds like VPR#35312, fixed in 8.2.1, would solve your issue. I think the behavioral change is coming from the new option to define the DateTime behavior (Date add-on) at the column definition (DialogColumn.DateTimeDetail). It controls the UTC-DateTime conversion behavior and might lead to that time difference. Please contact support and suggest that the HF VPR#35312 might solve your issue (if you don't want or are unable to update to 8.2.1).

ExitDate value issue

david alarcia over 2 years ago

Hello group!!

Today we have noticed that for some records in the table Person, the exitdate is different from its value (e.g)

Using the ObjectBrowser and opening the record:

ExitDate -> 9/16/2022 12:00:00 AM
But if we dropdown the field the property "value" is 9/15/2022 10:00:00 PM

We have a custom deactivation process that runs everyday at 2:00 AM, and checks the exitdate less than current date (UTC). So this ends with some employees being deactivated before they should.

Any idea how we can solve this issue?

Kind regards,

David.

Top Replies

Markus Weiss-Ehlers over 2 years ago in reply to david alarcia +2 verified

This sounds like VPR#35312, fixed in 8.2.1, would solve your issue. I think the behavioral change is coming from the new option to define the DateTime behavior (Date add-on) at the column definition (DialogColumn…

Parents

0 david alarcia over 2 years ago

Hello,

Just to clarify. We have recently updated from versión 8.1 to 8.2. It seems that this behavior appears in old records.

Kind regards,

David.
Cancel
Up 0 Down

Reply

Verify Answer

Cancel
+1 Markus Weiss-Ehlers over 2 years ago in reply to david alarcia

This sounds like VPR#35312, fixed in 8.2.1, would solve your issue. I think the behavioral change is coming from the new option to define the DateTime behavior (Date add-on) at the column definition (DialogColumn.DateTimeDetail). It controls the UTC-DateTime conversion behavior and might lead to that time difference.

Please contact support and suggest that the HF VPR#35312 might solve your issue (if you don't want or are unable to update to 8.2.1).
Cancel
Up +2 Down

Reply

Reject Answer

Cancel

Reply

+1 Markus Weiss-Ehlers over 2 years ago in reply to david alarcia

This sounds like VPR#35312, fixed in 8.2.1, would solve your issue. I think the behavioral change is coming from the new option to define the DateTime behavior (Date add-on) at the column definition (DialogColumn.DateTimeDetail). It controls the UTC-DateTime conversion behavior and might lead to that time difference.

Please contact support and suggest that the HF VPR#35312 might solve your issue (if you don't want or are unable to update to 8.2.1).
Cancel
Up +2 Down

Reply

Reject Answer

Cancel

Children

No Data