# Calendar Component Issue, Events are not in Synced for Different Devices / Browsers?

**URL:** <https://community.glideapps.com/t/calendar-component-issue-events-are-not-in-synced-for-different-devices-browsers/79196>\
**Category:** Report a Bug\
**Created:** [January 14, 2025, 4:07pm UTC](https://community.glideapps.com/t/calendar-component-issue-events-are-not-in-synced-for-different-devices-browsers/79196 "2025-01-14T16:07:06Z")\
**Posts on this page:** 12\
**Page:** 1

<div class="post-metadata">

**Author:** ![reimonade](https://sea2.discourse-cdn.com/flex002/user_avatar/community.glideapps.com/reimonade/32/82885_2.png) [@reimonade](https://community.glideapps.com/u/reimonade)\
**Post date:** [January 14, 2025, 4:07pm UTC](https://community.glideapps.com/t/calendar-component-issue-events-are-not-in-synced-for-different-devices-browsers/79196/1 "2025-01-14T16:07:06Z")

</div>

* * *

**Team ID:** 4mBqdW5tw1HAVJJIJJBE

**App ID:** CKshwEWRSRZFrp0eZWAt

**Description**  
Hi there, I have built a published app for a school. It is a Room Booking System. Users will be able to view multiple rooms and upon clicking each room, view the a weekly calendar view of the room’s bookings.

I am using the calendar component :

- Default Mode = Week
- Deafault Date = Today

It works well until my users found out a mismatch between her calendar view for the same date VS another user’s calendar view.

For example, in the calendar view, on 5th of February, some users will see 4 events happening on that day (see screenshot below)

 ![WhatsApp Image 2025-01-14 at 15.15.09](https://us1.discourse-cdn.com/flex002/uploads/glideapps/original/3X/5/b/5b77d4aa4f0750490f16c60429f3975b25661183.jpeg)

However, other users will see only 1 event happening on 5th of February.

 ![WhatsApp Image 2025-01-14 at 15.16.21](https://us1.discourse-cdn.com/flex002/uploads/glideapps/original/3X/f/6/f6c4d87765c7260cf72ef05d17023bd8374a9ba5.jpeg)

What is strange is that, the same user account will have different Events showing when accessed in different laptops / browsers :

- I tried accessing User A in Laptop A - via Google Chrome : I can view 5 events
- When we tried to access the sam User A in another Laptop B - Google Chrome : Can only view 1 event.

We suspected that it might be either a device settings issue? or a browser issue? Because some views have Monday as the start date while others have Sunday as start date.

Regardless despite different device/browser date settings, I dont understand how is it possible that the Events not show correctly / synced? even though its being accessed by the same User account. 🤔

---

<div class="post-metadata">

**Author:** ![Darren\_Murphy](https://sea2.discourse-cdn.com/flex002/user_avatar/community.glideapps.com/darren_murphy/32/47326_2.png) [@Darren\_Murphy](https://community.glideapps.com/u/Darren_Murphy)\
**Post date:** [January 14, 2025, 5:08pm UTC](https://community.glideapps.com/t/calendar-component-issue-events-are-not-in-synced-for-different-devices-browsers/79196/2 "2025-01-14T17:08:43Z")

</div>

> [@reimonade](#):
>
> What is strange is that, the same user account will have different Events showing when accessed in different laptops / browsers

Whenever I see this, I immediately suspect that one or more of the Date plugins are to blame. So my first question would be - do your use any of those in your App? And in particular the Format Date column.

Here is a simple test you can do - ask your users to navigate to the 2nd May on the Calendar, and see if there are any events shown that should be on 5th Feb. If there are, then almost certainly a Date plugin is the culprit.

---

<div class="post-metadata">

**Author:** ![reimonade](https://sea2.discourse-cdn.com/flex002/user_avatar/community.glideapps.com/reimonade/32/82885_2.png) [@reimonade](https://community.glideapps.com/u/reimonade)\
**Post date:** [January 14, 2025, 5:28pm UTC](https://community.glideapps.com/t/calendar-component-issue-events-are-not-in-synced-for-different-devices-browsers/79196/3 "2025-01-14T17:28:54Z")

</div>

Hi @Darren_Murphy thanks for the quick reply! I’m not sure whether this is considered as a Date plugin, but I just simply used the Basic \> Date & Time column using Glide Table. I selected “Medium” Format & Time Format “without seconds”

 ![Screenshot 2025-01-15 at 1.26.00 AM](https://us1.discourse-cdn.com/flex002/uploads/glideapps/original/3X/d/3/d3491348d68a98f1242a224ed50c0c9364a5dcec.png)  
 ![Screenshot 2025-01-15 at 1.26.12 AM](https://us1.discourse-cdn.com/flex002/uploads/glideapps/original/3X/d/6/d6981fd0a744828de424f8fd54d47a998244851d.png)

And I will surely follow your tip and check in with my users first thing tomorrow - But can i just quickly check with you why “2nd May” in particular?

Edit : Oh I do use the Date Plugin “Date Difference” in another column of the same table, however this is not being used by the Calendar component

 ![Screenshot 2025-01-15 at 1.31.53 AM](https://us1.discourse-cdn.com/flex002/uploads/glideapps/original/3X/9/5/959b1b58b9d8ceb3b0fb09291fa30859338579c0.png)

---

<div class="post-metadata">

**Author:** ![Darren\_Murphy](https://sea2.discourse-cdn.com/flex002/user_avatar/community.glideapps.com/darren_murphy/32/47326_2.png) [@Darren\_Murphy](https://community.glideapps.com/u/Darren_Murphy)\
**Post date:** [January 14, 2025, 5:39pm UTC](https://community.glideapps.com/t/calendar-component-issue-events-are-not-in-synced-for-different-devices-browsers/79196/4 "2025-01-14T17:39:49Z")

</div>

> [@reimonade](#):
>
> but I just simply used the Basic \> Date & Time column using Glide Table. I selected “Medium” Format & Time Format “without seconds”

They are fine, they are just normal datetime columns.

> [@reimonade](#):
>
> And I will surely follow your tip and check in with my users first thing tomorrow - But can i just quickly check with you why “2nd May” in particular?

Because 5th Feb can be an ambiguous date, depending on how it is represented.  
For example, if you write it as 5/2/2025, is that 5th Feb or 2nd May?  
The answer is it could be either, depending on where in the world you are and how your particular device is setup to format dates. This is where the date plugins can sometimes fail, most often in Safari browsers.

---

<div class="post-metadata">

**Author:** ![Jeff\_Hager](https://sea2.discourse-cdn.com/flex002/user_avatar/community.glideapps.com/jeff_hager/32/43_2.png) [@Jeff\_Hager](https://community.glideapps.com/u/Jeff_Hager)\
**Post date:** [January 14, 2025, 6:02pm UTC](https://community.glideapps.com/t/calendar-component-issue-events-are-not-in-synced-for-different-devices-browsers/79196/5 "2025-01-14T18:02:21Z")

</div>

How do users enter dates into that date column? Do they use a date picker, or do they type in the date manually, or is it maybe imported from some external source?

---

<div class="post-metadata">

**Author:** ![reimonade](https://sea2.discourse-cdn.com/flex002/user_avatar/community.glideapps.com/reimonade/32/82885_2.png) [@reimonade](https://community.glideapps.com/u/reimonade)\
**Post date:** [January 16, 2025, 1:58pm UTC](https://community.glideapps.com/t/calendar-component-issue-events-are-not-in-synced-for-different-devices-browsers/79196/6 "2025-01-16T13:58:54Z")

</div>

Hi all, @Jeff_Hager These were events that were migrated from another booking platform, I exported the CSV template and adjusted to meet the columns in this Glide app.

I am attaching the CSV file I used to populate my Glide bookings table for reference, we are using the DD/MM/YYYY template. I used this format because it was the one that was used by

 ![Screenshot 2025-01-15 at 8.31.18 PM](https://us1.discourse-cdn.com/flex002/uploads/glideapps/original/3X/f/e/fe9b931c0407c03c3df0c48a5c97eaca4584c8be.png)

After troubleshooting , we finally found the root cause of the issue : It’s the Language Settings of the browser.

For browsers with Language set to English (UK), it will show the correct time, but for browsers set to English (US), it will show the correct time.

 ![Language Time Discrepancy](https://us1.discourse-cdn.com/flex002/uploads/glideapps/original/3X/2/b/2bc4fb3c76dd3752838818f93592592fefc81004.jpeg)

My question is, that what is the correct way to set DateTime column values to avoid this from happening? We should just use the value of the date in text e.g “7 January 2025 at xxx” ?

---

<div class="post-metadata">

**Author:** ![Darren\_Murphy](https://sea2.discourse-cdn.com/flex002/user_avatar/community.glideapps.com/darren_murphy/32/47326_2.png) [@Darren\_Murphy](https://community.glideapps.com/u/Darren_Murphy)\
**Post date:** [January 16, 2025, 3:27pm UTC](https://community.glideapps.com/t/calendar-component-issue-events-are-not-in-synced-for-different-devices-browsers/79196/7 "2025-01-16T15:27:28Z")

</div>

The best way to represent dates is to use the [ISO8601](https://en.wikipedia.org/wiki/ISO_8601) International standard: `YYYY-MM-DD`. With this, you will never get ambiguous dates.

---

<div class="post-metadata">

**Author:** ![ThinhDinh](https://sea2.discourse-cdn.com/flex002/user_avatar/community.glideapps.com/thinhdinh/32/49_2.png) [@ThinhDinh](https://community.glideapps.com/u/ThinhDinh)\
**Post date:** [January 17, 2025, 12:21am UTC](https://community.glideapps.com/t/calendar-component-issue-events-are-not-in-synced-for-different-devices-browsers/79196/8 "2025-01-17T00:21:52Z")

</div>

Based on your experience with importing data, is it better to convert to ODS before importing to deal with these date/time problems?

---

<div class="post-metadata">

**Author:** ![Darren\_Murphy](https://sea2.discourse-cdn.com/flex002/user_avatar/community.glideapps.com/darren_murphy/32/47326_2.png) [@Darren\_Murphy](https://community.glideapps.com/u/Darren_Murphy)\
**Post date:** [January 17, 2025, 12:41am UTC](https://community.glideapps.com/t/calendar-component-issue-events-are-not-in-synced-for-different-devices-browsers/79196/9 "2025-01-17T00:41:15Z")

</div>

CSV works fine so long as datetimes are ISO formatted with a timezone offset.  
eg. `2024-03-15T08:47:25.013+08:00`

Glide also made some changes recently which should improve things, although I’m yet to test these out.

---

<div class="post-metadata">

**Author:** ![reimonade](https://sea2.discourse-cdn.com/flex002/user_avatar/community.glideapps.com/reimonade/32/82885_2.png) [@reimonade](https://community.glideapps.com/u/reimonade)\
**Post date:** [January 17, 2025, 4:41pm UTC](https://community.glideapps.com/t/calendar-component-issue-events-are-not-in-synced-for-different-devices-browsers/79196/10 "2025-01-17T16:41:44Z")

</div>

Currently even for new data where users are saving a “Booking” using the DateTime component, the data is stored in ambiguous DD/MM/YYYY format.

What’s the best way to store data from Glide’s Date Time input component as ISO8601? Does it have to be handled in a workflow?

---

<div class="post-metadata">

**Author:** ![Darren\_Murphy](https://sea2.discourse-cdn.com/flex002/user_avatar/community.glideapps.com/darren_murphy/32/47326_2.png) [@Darren\_Murphy](https://community.glideapps.com/u/Darren_Murphy)\
**Post date:** [January 17, 2025, 4:48pm UTC](https://community.glideapps.com/t/calendar-component-issue-events-are-not-in-synced-for-different-devices-browsers/79196/11 "2025-01-17T16:48:24Z")

</div>

> [@reimonade](#):
>
> What’s the best way to store data from Glide’s Date Time input component as ISO8601? Does it have to be handled in a workflow?

If you’re using the Date Picker component, Glide will automatically store it correctly.  
It might appear differently in the Data Editor, but that’s just a function of your display settings and browser locale/regional settings. If you double-click on a date value in the Data Editor, you will see how it’s stored.

---

<div class="post-metadata">

**Author:** ![system](https://sea2.discourse-cdn.com/flex002/user_avatar/community.glideapps.com/system/32/53398_2.png) [@system](https://community.glideapps.com/u/system)\
**Post date:** [July 16, 2025, 4:49pm UTC](https://community.glideapps.com/t/calendar-component-issue-events-are-not-in-synced-for-different-devices-browsers/79196/12 "2025-07-16T16:49:11Z")

</div>

This topic was automatically closed 180 days after the last reply. New replies are no longer allowed.
