Skip to main content

This content has been archived and is no longer being updated. Links may not function; however, this content may be relevant to outdated versions of the product.

Support Article

Inconsistent date time format in proposition data for date time



Summary of the behavior when date time values are updated through proposition bulk edit option.
  1. Displayed in local format (9/16/2016 11:00 PM)
  2. Stored in database in GMT format (20160917T030000.000 GMT).
  3. Upon every access it is converted into local format and stores again in GMT format.

Summary of the behavior of date time values through individual propositions edit option.

  1. Displayed in local format(9/16/2016 11:00 PM)
  2. Stored in database in local format(9/16/2016 11:00 PM)
  3. Upon reopening it is adding GMT offset and showing it in local format (9/17/2016 03:00 AM).
  4. Upon every update of the record, it is adding up GMT offset. So the date changes for every update (9/17/2016 03:00 AM ->9/17/2016 07:00 AM->9/17/2016 11:00 AM etc.)

Every update of the proposition through proposition page result in change of the date time values as it adds up GMT offset.

Error Messages

Not Applicable

Steps to Reproduce

  1. Create a proposition.
  2. Enter the value for the date time attribute as "9/16/2016 11:00 PM".
  3. Refresh and reopen the proposition. It shows as "9/17/2016 03:00 AM" (based on time zone).

Root Cause

The Date values entered in the Proposition landing page (unversioned propositions) are not rendered per the user's time zone. It is always rendered in GMT timezone.


Apply HFix-29926


Published October 28, 2016 - Updated October 8, 2020

Was this useful?

0% found this useful

Have a question? Get answers now.

Visit the Collaboration Center to ask questions, engage in discussions, share ideas, and help others.

Did you find this content helpful?

Want to help us improve this content?

We'd prefer it if you saw us at our best.

Pega Community has detected you are using a browser which may prevent you from experiencing the site as intended. To improve your experience, please update your browser.

Close Deprecation Notice
Contact us