# CHANGELOG: Aug 18 / Airtable integration, Timezones improvement, dozen bug fixes **URL:** https://community.fibery.io/t/changelog-aug-18-airtable-integration-timezones-improvement-dozen-bug-fixes/1923 **Category:** Changelog **Created:** [August 18, 2021, 11:00am UTC](https://community.fibery.io/t/changelog-aug-18-airtable-integration-timezones-improvement-dozen-bug-fixes/1923 "2021-08-18T11:00:33Z") **Posts on this page:** 10 **Page:** 1
### Author: ![Polina\_Zenevich](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/polina_zenevich/32/480_2.png) [@Polina\_Zenevich](https://community.fibery.io/u/Polina_Zenevich) #### Post date: [August 18, 2021, 11:00am UTC](https://community.fibery.io/t/changelog-aug-18-airtable-integration-timezones-improvement-dozen-bug-fixes/1923/1 "2021-08-18T11:00:33Z")
### Airtable integration One-way sync for your tables with Fibery Check our full guide and feel free to discuss it [here](https://community.fibery.io/t/airtable-integration/1920) ![image](https://us1.discourse-cdn.com/flex020/uploads/fibery/original/2X/7/7b40f10480d2e22be1a79bf709572f401bb922b7.png) ### Timezones: use UTC on the backend everywhere Timezones in programming are hard. Fibery is no exception here. How it works now: 1. At the moment Fibery does not allow the timezone to be defined for a workspace or for a particular user. 2. Fibery stores all date-time fields in **UTC** on the server. 3. UTC date-times are converted to the appropriate local time **in the UI**. 4. The timezone conversion applies only for date fields with time. Read more details [here](https://the.fibery.io/@public/User_Guide/Guide/Timezones-41) šŸŒø **Improvement** - Support file attachments in integrations: Intercom - Reorder Color Coding in the Toolbar - Document History: show/hide diffs toggle is added ### šŸ¦ Fixed bugs - User Profile Field Name does not get renamed in the collection title - Get rid of the ā€œCollectionā€ word in collections in User Profile - A new option appears in States only after page refresh - Error in the editor if open any boolean formula - Formulas and Lookups are not imported in auto-linked relations - User is unable to access integration settings after sync failure - Timeline auto scrolls down on adding a new entity and there is no way to return back to the top - Context filter disabled after app import - Itā€™s impossible to rename relation when during the creation - Auto-link to User relation is not exported - Automations: Issue with clearing value for State field ---
### Author: ![HighInFiber](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/highinfiber/32/1671_2.png) [@HighInFiber](https://community.fibery.io/u/HighInFiber) #### Post date: [August 18, 2021, 3:26pm UTC](https://community.fibery.io/t/changelog-aug-18-airtable-integration-timezones-improvement-dozen-bug-fixes/1923/2 "2021-08-18T15:26:11Z")
> [@Polina\_Zenevich](#): > > Timezones in programming are hard. Nah, theyā€™re totally [easy](https://youtu.be/-5wpm-gesOY). šŸ˜ ---
### Author: ![helloitse](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/helloitse/32/498_2.png) [@helloitse](https://community.fibery.io/u/helloitse) #### Post date: [August 18, 2021, 7:18pm UTC](https://community.fibery.io/t/changelog-aug-18-airtable-integration-timezones-improvement-dozen-bug-fixes/1923/3 "2021-08-18T19:18:28Z")
@Polina_Zenevich whatā€™s the best post to upvote to see timezones implemented sooner? I find this part of the documentation rather concerning: > We will implement support for user timezones. Maybe. Some day. If you want to speed that up, feel free to ping us anywhere and share your pains/feedback about it! as it makes Fibery a cumbersome choice for teams working in more than one timezone, which is many remote teams ---
### Author: ![Polina\_Zenevich](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/polina_zenevich/32/480_2.png) [@Polina\_Zenevich](https://community.fibery.io/u/Polina_Zenevich) #### Post date: [August 19, 2021, 8:41am UTC](https://community.fibery.io/t/changelog-aug-18-airtable-integration-timezones-improvement-dozen-bug-fixes/1923/4 "2021-08-19T08:41:16Z")
Yes, thatā€™s it. But for now, we donā€™t have a nice solution in mind. And development looks very complicated and will take a very long time in any case. So weā€™re collecting cases and after all the ā€œmust-haveā€ features will be done - maybe that is smth weā€™ll work on. Feel free to initiate discussion in the Ideas&Features category - will be glad to hear more about current pains and see votes šŸ’– ---
### Author: ![rothnic](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/rothnic/32/1850_2.png) [@rothnic](https://community.fibery.io/u/rothnic) #### Post date: [August 19, 2021, 2:08pm UTC](https://community.fibery.io/t/changelog-aug-18-airtable-integration-timezones-improvement-dozen-bug-fixes/1923/5 "2021-08-19T14:08:46Z")
Iā€™m curious what your team is trying to do that isnā€™t supported by how timezones currently work? I read through it and it seemed to generally make sense, but maybe Iā€™m not realizing what we are missing at the moment. ---
### Author: ![B\_Sp](https://avatars.discourse-cdn.com/v4/letter/b/e8c25b/32.png) [@B\_Sp](https://community.fibery.io/u/B_Sp) #### Post date: [August 24, 2021, 4:49pm UTC](https://community.fibery.io/t/changelog-aug-18-airtable-integration-timezones-improvement-dozen-bug-fixes/1923/6 "2021-08-24T16:49:16Z")
> [@Polina\_Zenevich](#): > > Reorder Color Coding in the Toolbar You guys also tweeted about this, but I canā€™t really figure out what you are referring to. Could you explain what this improvement is in detail? Thanks! ---
### Author: ![Chr1sG](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/chr1sg/32/3941_2.png) [@Chr1sG](https://community.fibery.io/u/Chr1sG) #### Post date: [August 24, 2021, 5:26pm UTC](https://community.fibery.io/t/changelog-aug-18-airtable-integration-timezones-improvement-dozen-bug-fixes/1923/7 "2021-08-24T17:26:42Z")
I think itā€™s referring to the ability to change the priority of the colour coding (relevant in the case where an item matches more than one criterion): ![image](https://us1.discourse-cdn.com/flex020/uploads/fibery/original/2X/b/b82bd01145a950560e00cda623a64ee5f60484c7.png) ![image](https://us1.discourse-cdn.com/flex020/uploads/fibery/original/2X/6/63a0afce6e0adf4c4066f7df22ef59edbc3ae71b.png) ---
### Author: ![Mother\_Bones](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/mother_bones/32/6927_2.png) [@Mother\_Bones](https://community.fibery.io/u/Mother_Bones) #### Post date: [July 6, 2023, 10:54pm UTC](https://community.fibery.io/t/changelog-aug-18-airtable-integration-timezones-improvement-dozen-bug-fixes/1923/8 "2023-07-06T22:54:14Z")
Timezone cannot be defined per user, and yet importing CSV times converts them to UTC (regardless of what timezone is specified in the CSV time fields) in a recursively buggy way. I currently have items reading 18 hours skewed. Iā€™ve been the only person in this workspace. I have always been UTC -6. I imported datasets in UTC after reading that Fibery only does UTC (actually I thought Fibery was THE ultimate remote teams solution because it only operated in UTC, but as I found I am mistaken in the way ā€œonly operates in UTCā€ actually functions in practice) ā€¦ ā€¦and unbenknownst to me, I proceeded to make a bunch of relations and formulas and 3 weeks and 18 datasets into developing this, I find no matter what I do I canā€™t get visually identical dates to return true on filters. I have zero idea how to import things now so that they will work, because from what I can tell -every- single time I use a date in a formula, it skews the time another 6 hours. šŸ˜­ ---
### Author: ![Chr1sG](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/chr1sg/32/3941_2.png) [@Chr1sG](https://community.fibery.io/u/Chr1sG) #### Post date: [July 7, 2023, 7:15am UTC](https://community.fibery.io/t/changelog-aug-18-airtable-integration-timezones-improvement-dozen-bug-fixes/1923/9 "2023-07-07T07:15:12Z")
If you are the only user in the workspace, you shouldnā€™t need to overthink date-time fields. On the UI (and when importing) Fibery will treat them as local time, so just forget about UTC. > [@Mother\_Bones](#): > > importing CSV times converts them to UTC Yes, it converts the date-time you provide into a date in UTC which it stores in the backend, but when youā€™re looking at data on the UI, it converts the data stored in the backend back into local time. The problem comes with formulas that result in numbers or strings instead of date-time. These will always be based on the backend, since Fibery is designed as a multi-user platform, and it cannot always be guaranteed that all users are in the same timezone. See [this reply](https://community.fibery.io/t/relate-entities-based-on-dates-and-make-more-entities/4728/7). ---
### Author: ![Mother\_Bones](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/mother_bones/32/6927_2.png) [@Mother\_Bones](https://community.fibery.io/u/Mother_Bones) #### Post date: [July 7, 2023, 8:08pm UTC](https://community.fibery.io/t/changelog-aug-18-airtable-integration-timezones-improvement-dozen-bug-fixes/1923/10 "2023-07-07T20:08:41Z")
This is functionally 3 problems for me. I originally imported my datasets in UTC, so my initial imports are 6 hours skewed. Then in that dataset, I use a formula to create DateRanges ā€“ which recalculates skews the times. Then in another dataset, I use a formula to extract the relevant Dates of each in the DateRange ā€“ which recalculates and skews the times. By the time Iā€™m comparing one dataset to another, the original time is 18 hours changed.