I can’t seem to figure out why this started happening… It didn’t start until recently. I have a table that’s connected to a dataset to simply put what’s in the dataset into the table (nothing was coded).
Now, when the page loads, it shows the correct dates as I see them in the dataset. A couple seconds later, one day is subtracted from the dates in the table.
If I refresh the page, same thing… Correct dates, and in a couple seconds they change subtracting a day.
I tried turning on “Fetch after the page loads” in the dataset settings under Performance. This only made it so I didn’t see the date dynamically change, but still showed the date minus a day.
Here’s a video demonstrating the behavior, if it helps (sorry, it’s not very ‘Hollywood’, but should get the point across… Also, excuse the blurred columns, etc. - I didn’t want to post any sensitive information, just what’s relevant):
Can anyone explain this, or have a workaround?
Thank you!!
1 Like
Hi! It’s possible that the time zone for the data in your dataset is set to a different time zone than the time zone of your browser. If this is the case, the dates in the table will be displayed as if they are in the time zone of the dataset, which could result in them appearing to be one day behind. Another possibility is that the dates in your dataset are not being properly formatted when they are displayed in the table. When the dates are stored as text in the dataset and the table is expecting them to be in a different format, the dates might be interpreted incorrectly. You have check if there is a formula in the table that subtracts a day from the dates, this could cause them to appear one day behind.
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.
Did you ever get to the bottom of this? Just a few weeks ago I have a page with a table start doing a similar thing. The page allows me to select a row and open a view of just that record. This second page has the correct dates.
I have gone so far as to create a brand new page based on the same collection and have the same incorrect results. I now have 1000 records in the collection, but that shouldn’t have any impact on displaying the data correctly.