When using a grouped top level table the creation of new entity defaults to the grouped property. (bottom left) I tried different orders/workarounds, and hiding empty group entities and there seems to be no way of controlling desired behaviour.
Creating the desired entity type is only possible at the top right corner. Which is probably not the most intuitive behaviour for new fibery users. Also accidentally creating new “PropVsFixed” entry leads to further confusion. As it shouldn’t even be possible when it comes to specifically disabled “Allow anyone to add new options” in Advanced Field Proprties of said Single-Select Field in first place.
→ It would be great to enable admin control to lock or IF entities can be created by users to fully enable an otherwise excellent capability/functionality of this feature.
→ I haven’t pondered much but if there are no otherwise practical/needed use-cases disabling entity creation for “hidden empty groups” and/or “disabled user-added advanced option”.
EDIT: nvm. should have checked editor/user view. at least some of the issue is alleviated. however bottom/default entity-creation would still be nice to have from usability/newcomer perspective or maybe in general. leaving the post for reference.
I think all entity creation options (new button, end of table) should default to the child entity not the group. The current way is counterintuitive and leads to creation of many quickly deleted entities.
Would love for this to be fixed as well. Table grouping is quite sub-par in Fibery at the moment, and with general ease of use improvements coming at the moment, I hope this can be on the roadmap sometime soon!
Fibery can get more complex with deeply nested levels, and I think there it can be left as it is. But there’s opportunity to treat grouping and levels as different behaviors.
Levels = each level is important
Group = the grouping is less important than the items. Ie, people want to create items, see items open be default (open groups)
The grouping in board view and gallery view looks and works great, bringing that design into lists, and tables would be fantastic.
There was a roadmap item on this at some point with the consolidation of grouping design in Fibery, but it was removed. Not sure why.