Thanks for the quick reply, @michaelstrauss307 .
I thought about the time zone possibility, as I was told it started happening in November. Since my location has a DST (daylight saving time) which we gain/lose an hour every March/Nov, it makes sense. And since it’s a date field in the dataset (no time), I would assume it defaults to 00:00, so offsetting an hour could take it to the previous day when the page renders.
With that, I tried changing the time zone in the Wix dashboard (Settings > Language & Region), although it was correct, to an hour before and an hour after. Exact same results. Also tried in a couple different browsers in case it was using local vs server-side and it was a browser setting, as you mentioned. Tried on 3 different computers with the correct time zone set in the OS. Same thing happens.
You mentioned ‘formatting’. It is stored in the dataset as a date. There are no text conversions or any code happening in-between entry to the dataset and the table. As mentioned, it just kind of started doing this with no changes to the dataset or page with the table. So it shouldn’t be interpreting anything incorrectly, given nothing is done with the formatting, and it’s date-in/date-out.
There are also no formulas in the table. To my understanding, this would be done within the developer console with Velo code, but this page has none.
Going back to your mention of the time zone possibility (as I’m still suspecting that), you mentioned the time zone for the dataset being different than the time zone of the browser… Outside of changing the time zone in the Wix dashboard, I don’t know of any way to adjust this specifically with the dataset (or the table). Is there something there that I’m missing?
I would assume a table, without any modifications/code/formulas, being connected to a dataset should simply mirror/extract 1:1 the data in the dataset table versus making adjustments on render… Seems odd.