DateTime Control is not working properly
It is observed that when setting a date property using the out of the box (OOTB) pxDateTime control that after a section refresh the DateTime continually goes back four hours at a time.
The time format of the date is also not seen with the GMT timezone information as is typically the case for DateTime properties.
Steps to Reproduce
- Define a DateTime property on a section.
- Launch a portal containing that section and select a DateTime value and click on the search button(a button configured to do a section refresh).
- Check the clipboard for the property of interest ( 5/2/2016 10:05:15 ). The user interface (UI) displays the time as 06:05:15.
- Click the search button again and observe the DateTime value on the clipboard is now ( 5/2/2016 6:05:15 ) and on the UI 02:05:15.
An issue in the custom application code or rules. The page the property of interest is referenced on is classless and not properly instantiated. This causes the value to not be properly stored as a DateTime value.
Perform the following local-change:
Create the page of interest prior to performing actions on it's associated properties.
Published June 6, 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.