Thinks fast, acts slow. Tried adding 200 sample items it did it one by one. Tried then updateing those 200, but because only 50 were loaded on screen it only saw 50 and only updated thoseā¦ one by oneā¦
Fibery: Thought for longer, acted much faster.
While adding sample data is niche, I do have a client that throws in meeting notes, and it makes all the tasks, so this in general about working with data in bulk. Fibery AI > Notion AI.
Exciting! Maybe using formulasā¦? Or even just the lookup arrow like with other filters āThis PA > Assigneesā
So looking forward to this one!!
Would love it to be a files database in some future, but also sharing thoughts that Iām scared of the āGlobal Databasesā. Users and Files make sense as global as they are fundamentally different. But not all workspaces use Tasks or Documents, so having them as templates, and anyone can add or remove custom databases to global databases would be more ideal imo.
Also, maybe different workflows need files for different things, so youād then have separate files databases for different use cases and relationships. Lots to think about
If whiteboard were fields, you could have templating work in the same way as it does with entities. āTemplatesā database, and when entity linked to template, overwrite the the whiteboard field with the templateās whiteboard field data. Iām standing my ground on this one haha.
Whiteboards are getting more and more separate from the Fibery ecosystem and Iām worried itāll be harder to bring them in later. Not sure where the data for the whiteboard templates will liveā¦
Looking forward to this!! I think it will make it much easier to get buy in. Iāve heard it be a must-have a few times.