I have two servers, one running 8.1.27 which is not affected, and another server running 8.1.50 which displays this error. I have a perspective view with time picker components on it. I noticed yesterday that I can set the time picker to, say, 6:00 am and when I would check the database, the value recorded would be 6:33. No matter what value I set the time to on the view, the value written would be 33 minutes greater. There are several time pickers on the view and they all acted the same. The time pickers on the working server did not display this behavior and worked as expected. The project on the non working server was copied, database and all, from the working server. Nothing was changed. I finally noticed that in the designer, the props.value of the component was off by 33 minutes. I can put the designer in run mode, enter a time of 6:00 in the picker, and see the value say 6:33 even though the formattedValue is 6:00! I decided to place a new time picker on the form and check that. The new time picker behaved as expected. The difference was the DATE value. On the newly placed time picker, the date was today followed by the time. (2026-1-28) On the original time picker, the date was 1900-1-1. Changing the date on the time picker to today’s date eliminates the 33 minutes being added to the value. However, on the working server that this project is copied from, the date is still 1900-1-1 and it works fine. Changing the date back to 1900-1-1 reintroduces the error, so it’s repeatable. I’m going to guess that somewhere between these two versions something was changed, but I didn’t see any mention of a 33 minute error in the forum. I’ll also assume since I don’t remember that when I placed the original components on the view, they had a default date of 1900-1-1 and that behavior has been changed as well because it defaults to today’s date now when placing the new component. I have no idea what is going on, so I’m reporting it here. Thanks!
Tip: edit your post to break it into logical sections with paragraph breaks. It's a very difficult read. I'll delete this later.
1 Like
Doesn’t ring any bells. Try enabling trace logging or adding a change script to see where those extra 33 minutes are coming from. In addition, timezone differences might be something to look into. Review our release notes starting with 8.1.28 to determine if something changed. Good luck. Let us know what you find.