Oshyan
April 9, 2021, 5:11pm
27
Much of this has been discussed previously and I believe many aspects you mention are planned in some form. Overall I am interested in similar capabilities long-term.
Show/hide fields in the entity view shouldn’t be too hard to implement.
Depending upon what you mean, I disagree that it shouldn’t be global. In other words, I think it is reasonable that all entities of a specific type share the same settings for show/hide fields (but the choice should ideally be personalised to the user).
Airtable have a ‘hidden fields’ section that is expandable, and I reckon fibery could just mimic that.
[image]
https://community.fibery.io/t/some-customizations-of-entity-view-hiding-unused-fields/452
Hey my Fibery peeps! Been watching this product with increasing interest and I’m convinced that it (and team) are destined for great things. Enough fanboi, lets get to it…
In a workflow i’m creating, one area of interest is the ability to add Fields to a Type as it moves through the different States of the workflow. I don’t see how this is possible in the current state but can you good folks think of another way to do this? An example would be building a website. First state is “Research” so yo…
I came across an interesting app today called Ninox. Has anyone heard of or used it? It reminds me a lot of Fibery in many ways. It has been around a lot longer, since 2014 at least, and in some ways is more capable than Fibery (more on that in a moment), while in other ways less so. The UI/UX is a bit outdated and clunky, but the set of capabilities is actually fairly impressive and broad in its core database area.
Ninox focuses entirely on databases, there are no “documents” at all, and no w…
1 Like