Thank you @ScottWorld
I see…
Having played around with it (created fields), I see that importing basic/straightforward events (with a start and finish time) would be fine.
However I just imported a calendar .ics file that has a mixture of basic events, all day events and recurring events. The all day and recurring events don’t really work (all day defaults to 12am to 12am which makes it appear on the next day, recurring doesn’t seem to work at all). I’m assuming this is an Airtable limitation and it’s not really designed to import more complex calendars - but please let me know if I’m wrong!
That is how the .ics file format requires all-day events to be listed: from midnight on one day to midnight on the next day.
However, Airtable’s calendar doesn’t properly interpret those events as all day events. Your workaround in Airtable is to make the start date and the end date IDENTICAL — both the same date, and both the same time of midnight.
Alternatively, you can also choose to make the event a very small event that only takes up 15 minutes or 30 minutes.
Those 2 ideas will help you workaround this problem in Airtable.
However, you can’t have all day events that span multiple days in Airtable… Airtable doesn’t know how to correctly handle those. In those cases, you would need to break them up into several different records.
I would recommend sending an email to support@airtable.com and asking them to please support .ics file formats better within the program.
Hope this helps! If this answers your question, could you please mark this comment as the solution to your question? This will help other people who have a similar question. :slightly_smiling_face: