Hello! I am a prospective user, and before I dive in I’m wondering if Documents in fibery have buttons for creating records, changing values, sorts and filters.
Thank you!
1 Like
Documents don’t have buttons, but databases do.
So you could create a database (called Documents, or Pages, or whatever) and add buttons (plus other fields). All databases come with a default rich text field (called Description, but you can rename) which behaves just like a regular sidebar document.
OK, but I can add table or list views of databases TO a document right? Basically I want to make a page with buttons to interact with those views.
Yes, and anything you can do within a document, you can do within the rich text field of an entity, including adding tables and embedding views.
Not sure what ‘interactions’ you want to have, but anything you can do with a sidebar view (edit values, add new entities, reorder items, etc.) you can have with views embedded in rich text.
I understand the confusion!!!
Buttons are a column type in a database that exists on a record. I can’t have a button floating on a dashboard or document to perform actions on my database.
Do folks make a table just of buttons to do this type of task?
Correct, buttons are tied to entities and there’s no way to make ‘floating’ or ‘inline’ buttons within rich text.
I don’t really know what others do (or how often they face a need).
For some of the things you mentioned “changing … sorts and filters” it’s not something I have heard people wanting to use buttons for (and buttons in Fibery operate on the data, not on the views/presentation of the data).
So for changing … sorts and filters, you can add different filters that get clicked on and off (and are presented as buttons). These may do what you’re wanting?
Here’s a snapshot from a Document that includes views of multiple databases (Conflict Checks, Projects, Meeting Notes). I’ve added selectable filters to those database views, which present as buttons so I can choose what set of records I want to look at (active, potential, emergency, etc.)
In contrast, here’s another Document with a view of a database that holds offers. The database has a Button that causes actions to be taken (like changing the status of the offer) when the person clicks to “Accept the offer”. The database has other buttons, but those are not relevant to this view, so are not shown. In contrast to the view filter toggles (that are interacted with in button form) above, these sequence triggers (formally referred to in Fibery as “Buttons”) take an action on the database itself.
I hope that helps!
1 Like
Yes it is this one. How did you add those buttons to a document?
They are quick filters on an embedded view.
Understood, so they aren’t buttons that can run formulas to perform actions. Thank you!
Hi Nick! From what I can tell it sounds like you’re coming from Coda. Is that right?
Similar to the Coda/Notion divide, the Coda/Fibery workspaces have similar terms but they perform quite differently.
It’s probable that a database with a rich text field, relation fields, buttons, and scripts, can recreate the changes in data you’re thinking of but it will certainly be a different flow of work/ seeing the information and manipulating it than a Coda doc.
Do you have a specific example of your use case?
1 Like
Yes! I am a coda user and I’m investigating Fibery. I have a multi user task list with some specific functionality for an entertainment / broadway use case. Here’s a screenshot. Thank you for your help!
No, but the buttons on the right (the “Accept Offer”) are buttons on the entity. These buttons can be exposed in a view like any other field. They will also appear at the bottom when you select multiple entities. So, for example, you could have a quick filter that displays only entities with a certain status. Then you could select all the visible entities and click the Button at the bottom of the view that appears.