Small release today with some quality of life improvements.
Embed View
Now you can embed external links into Fibery as Views via Embed View. Create Embed View in any Space, set a link and enjoy the result. It can be handy for HTML reports generated by Fibery AI or your custom internal informational pages you host somewhere.
Files. Now you can sort Files on Entity View by name, by size, by creation date, or manually.
Fibery AI:
Now you can set Space into the context, it will help AI to answer better and faster and do things better in some cases
When you are on some entity/view/etc and click Fibery AI, it loads the latest chat with this entity/view/etc in the context
Fibery AI should work faster for some cases now, since we added cache to some places and optimized how it loads database schema.
Natural theme colours. Fibery now adapts colours to your theme much more smoothly across databases, rich-text backgrounds, whiteboards.
Convert Entity. Now Fibery does not delete original entity when you convert it to another database. Thus you will not lose any data and can manually transfer missing things and delete original entity when you really want to do it.
Fields of related Entities: Showing fields from related entities just got easier. In addition to Fields and Layout, you can now add nested fields directly from a fieldās (ā¦) menu (e.g., Bug ā Owner).
Reports. Now when you add some fields to the report manually, Fibery does not remove them in reports performance optimization step, so you will be able to use them in filters when needed.
Fixed Bugs
Documents / Rich Text:
Restore previous version doesnāt work as intended in some cases
Rich text columns look weird on mobile devices
āNot foundā page is expected instead of error in attempt to open deleted document
Fields:
Formula icon doesnāt display for relations and users used in Name formula
Formula icon near unit and tooltip on hover doesnāt display when create entity on view not via quick add form
Formula icon and tooltip on hover doesnāt display when create entity in Search
Fibery AI:
From the agent answer itās not clear how many entities are supposed to be deleted.
When agent queries views for large workspaces, it fails with timeout
If agent uses wrong naming convention, query fails
Removed findRecurringPatterns tool. It tries to find patterns in huge amounts of data usually and times out 90% of the time.
Table View: When adding a second level Database, the items from the 2nd Database donāt show up properly in the hierarchy.
Whiteboard:
Unable to store board into postgres as JSON has incomplete unicode surrogate
Copying notes keeps original author as owner
Whiteboard: comment preview should not appear when you drag shape
I thought that Fibery AI could create but not update HTML reports. Has this changed?
This feature will help with bringing external data/info into Fibery for workflow management. Iām glad to see it shipped!
I think I saw this in action this past week and thought it was a (pleasant) bug. Thanks for easing the conversion pains!
Love the Embed view. I can see how it can be useful for example in smart folders as mirrored view. This would require dynamic data for Embed. I think that it would be nice to define URL from a field. This way we could define specific url for entitty and use this url for Embed view dynamically.
I agree with the idea of dynamic views. If we could pass entity fields as parameters to the url (using formula syntax) that would open up great possibilities of integrating fibery with other systems.
Okay, this makes me nervous (thinking about data lifecycle and how these html pages might need to evolve overtime).
Do we have some kind of access of our own where we can revise the pages directly?
Just want to give a shoutout for the existing āconvertā feature in the case of an individual entity to another dbā¦just did one from something 5 yrs old and reveling that my 38 references stayed intact!..and I was able to work with the original, which had a much different schema, to edit the new one w/out the deletionā¦
I think there is still some work to be done, such as a menu that would map things like dates (talked a little about here) Add āconvertā option to automations so references, comments and files are kept and preservation of dates, in particular creation date - so the converted entity gets as much of the originalās metadata. This is something you can easily do in other tools like Notion, etc but they also make it so easy that I usually wind up with way too many unwanted side effects - so Fiberyās structure a huge plus hereā¦hoping to get a bit more into this feature soon, but for now itās already great and wanted to let you guys know about that - in particular that I have stuff now over 6 yrs old and with times changing the need to convert things is a big theme these days!
I agree with you that a āmappingā tool is needed. When we started with Fibery, we used the Project Management template and then, a year later when we had more knowledge of Fibery, decided to re-build it from scratch taking in account our needs. One of the obstacles the team is facing is the inability to easily convert an entity (and its sub-entities at the same time) into a new structure. If you have a Project with 10 Tasks and 20 Subtasks, you need to convert one by one everything and it takes time.
So, having a manner to map the fields and the ability to convert everything linked to the converted entity would be a big step forward.