Dates are updated automatically without registering it

Hello,

I saw that when I change a “date”, it is sometimes automatically updated to another date by the system without me doing anything and also without automations or dependencies in place.

I am registering historic events and am using dates like “November 11, 0014”. The system is registering these, but it seems it mysteriously updates the dates to a seemingly random date. Does anyone know why this is. Maybe dates before 1900 are a problem? Or the date is simply not saving. Hopefully, someone can help me with this.

EDIT: It seems the system keeps turning the date back to December 31, but I do not know why.

How are you entering the dates? The date picker ‘interprets’ what you type, and certainly struggles with dates before the year 1000.
But I have found that you can type 0014-11-11 and it will be happy.

I am entering dates the same way as you proposed. And it is able to register some dates. However, some times it changes the date suddenly to something else, without me doing anything and without any automations or dependencies. I am thinking the system struggles with early dates, but then this should be the case for all the dates.

I saw that the dates are also different in the overview compared to the entity view. So, there might be a real bug here.

Are these definitely the same field in each case?

Yes, they are definitely the same field. The fields are called Start Date and End Date. And both are acting weird.

Yeah, OK, I was able to reproduce some weirdness. We’ll look into it.
Sorry

The date-picker itself gets super funky as well when trying to set dates from BCE. The date field wasn’t built for this, but it is an interesting use-case.

Thanks. I hope it is fixable. For me at the moment dates from January 1, 0001 are important to be able to register, as I am recording historic events. I saw that the Timeline and Gantt Chart are also acting a bit weir here, because the grid lines disappear at very early dates.

I do not need BCE at this moment, although it would be great if this was also possible.

I tried to let AI update the dates for me and it found this quirk with dates before 100:

Fibery does shift dates this early in history, and that is what you ran into. It treats the date you enter as being in the old Julian calendar and stores the Gregorian equivalent. For years 1 to 99 that is two days earlier. Typing 0001-01-01 gives 30 Dec of the year before, which Fibery then labels 0001. To make a date show as you want, enter it two days later. For 1 Jan AD 1, enter 0001-01-03.