This release has several quality of life improvements for creators and users. Enjoy!
Duplicate Field
Imagine you setup a long and beautiful single-select field for Tasks database and suddenly realise that you need it in Bugs database as well. You had to re-create it from scratch⌠No more! Now you can quickly duplicate basic fields (including single- and multi-selects) into another database.
Improve Entity creation flow when entity name is generated via a formula
We have improved the entity creation flow when the entity name is generated using a formula. When creating a new entity, you will now see all the fields that are involved in the formula calculation. This allows you to set them immediately and have a proper entity name from the start. This functionality works in all views and in search.
Support multi-accounts in google calendar
Now you can sync several Google calendars accounts into the samedatabase. It is handy when you have many users that need to sync Events into Fibery.
NOTE: Pro or Enterprise plan is required for this feautre.
Setup new Google Calendar Sync and enable Allow users to add personal integrations option.
Views always comply to filters and do not show entities that are out of filters range
Sometimes newly added entities are not visible in views if they do not comply to some filters or âhide empty rows/lanesâ setting. Sometimes newly added entities are still visible even if they do not comply to some filters. It was a mess.
Now we removed this logic completely and entities will always comply to filters. After new entity creation you will see a toast in the right bottom corner, so you can quickly open an entity and change some fields if you need to do it, or copy a link to just added entity.
Google Calendar Integration:
â Event Id & Event UID fields added
â Now it is possible to specify future cut-off date for events. Just set some value in Do not sync events that start more than [X] month(s) from today field
Automations:
â AI-generated formulas in automations improved and work much better now
â Node.js in Script Action in Automations is updated to version 22, so you can enjoy new functions
Rich Text: Code block now supports Dart language formatting
Slack Integration: Channel ID field is added
Access templates now open in a page rather than expanding as a sidebar folder. No benefits for now, but stay tuned
Entity History: Entity history section was polluted with schema changes events: field added, field, removed, etc. No more. All such events are removed from entity history log
Action toast are not so contrast now and less visible, they are also moved to the right side of the screen. We are not sure it is good, so let us know if it is not
Fixed Bugs
Fields:
â Collection unit: its weird that the âadd buttonâ is before the +1
â Zero value is not displayed for required numeric field in edit mode
â Required value is asked when it can be auto-filled
Views: Search field blinks on switching between views
Calendar View: Itâs impossible to create entity on Calendar view if 2 separate dates are used in config
HubSpot Integration: memory leak fixed
Templates: Space imported from template get installed to Spaces section instead of the Default Space
Batch Actions: Plural form is expected to be used for âCopy to markdownâ when itâs selected for more then 1 entity
Automations: Relation does not get auto-linked when entity is created via Form on context view with many-to-many relation
Whiteboard: When duplicating a sticker in a section, they are automatically duplicated multiple times by clicking
Notifications: itâs easy to miss that filters are selected on empty Inbox
Reports: Action âMove to spaceâ is missing for report views
You can duplicate workflow field as well, but only if target database does not have any workflow so far. Note that it is not a sync fields, it is just duplicate
Good stuff!! Love the new behaviour on formula. Only thing that can be bad is if the field is meant to be set by automation and not by user. Maybe adding a place to set which field should be set by user on creation? Idk. Setting primary and secondary fields?
One easy fix is focus. On create, focus on first field for faster creation. And a small thing that could be nice is that if there is only one field to be set by user, just show that as the primary field without the text of âName will be generatedâ it could add confusion to the end user. Even if there is more than one field, I think the âName will be generatedâ isnât needed⌠Then we could just set the name as [Field], and a different field type could act as the primary field for the database.
Not sure if this was happening before now, or related to the new way filters work. When using a context filter, it forces to choose one that will obey the context filter rules and stay in view. I think I like that⌠(again, problems if should be filled with automations). Itâs just a bit weird that itâs only in context views and not in âorâ filters in all views. For example if I filter to show any that contains either of the three related items, I would expect it to have the same behaviour, but it doesnât. Iâm finding it a bit confusing. In any case, the dropdown to choose from in form and list create looks ugly and different from the normal single select dropdown. See photos and video below.
Edit:
1 more thing that I saw was removed from the spec but would be really nice:
When there are no required fields and no editable fields (or any set fields for input on creation) for input in Name Formula. Just create the entity without requiring an extra click. Right now it needs two clicks even though the second click adds nothing new.
And since it is possible to know which pane is in focus (by the fact that Shift+Esc) works. Iâm wondering if its possible for the âOpen Entityâ in the toast to open to right of the in focus pane instead of all the way on the right. This way keeps the context from where it was created. Especially if you have many many collapsed ones and going back and fourth.
The hidden treasure for me in this release. Was tough looking at the activity log for old entities and having to scroll forever. Great quality of life improvement.
This feels a bit like an extension of the ârequired fieldsâ UX. Very nice touch!
I like this change! Though it may be easy to miss the toast on larger screens. Perhaps some brief highlight or coloration of the toast will help with this.
Just out of curiosity, is this new from yesterdayâs update? It almost acts as dynamic filters in relation view, but then accessible without an already created entity. Solves many issues Iâve been having!
Any chance for it to act more like dynamic relations? Where by you can allow âshow othersâ, and set addition filters + sort?
Follow up: It picks one as default. How does it decide which is default? I thought it might be first in rank, but I tried changing the rank and it doesnât change. I think a simple way would be allowing custom sort and then default to the first one.
Yeah sorry, Iâll try to be clearer. Iâll share a videos as I think that will be easiest.
I realise they are not as similar as I thought, but still have overlap. Down side is that the context filter is in view and not in field settings. Like a lookup would be.
One more thing is how similar this is to a lookup. If I were to add a lookup field from the people to show the emails, I would get the same data as the context filter, but not editable or addable.
Duplicate Field
Improve Entity creation flow when entity name is generated via a formula
Support multi-accounts in google calendar
Views always comply to filters and do not show entities that are out of filters range
Improvements
Fixed Bugs
Thursday is my fav day now! 
Too many awesome improvements for me to detail to be honest.
