Forms are unintuitive and silly in more ways than one

[RonMakesSystems]

I agree about the “Name will be generated by formula message”. I think most people don’t need to know that. Maybe let the architect decide if to show it as the “Name” field or not.

But the Fibery team disagreed with this back in 2025:

@mdubakov

@RonMakesSystems

And a small thing that could be nice is that if there is only one field to be set by user, just show that as the primary field without the text of “Name will be generated” it could add confusion to the end user.

Here I tend to disagree. Without this message it can be unclear what is happening.

@AdVhPkgKad

However, I do want to make a note that the form could check whether a user is logged-in and navigate them to the created entity on save, if it was set up that way.

This is great idea!! I have a link to a view which shows on submission “See your submission here” which takes them to a table view which then they need to find the thing they just submitted. A “Create and open” in standalone form views would indeed be nice.

@AdVhPkgKad

• The standard ‘Default’ form is effectively required fields only, which is almost never correct due to automations, validation rules, and values populated from different entry points.

Note: you as the architect can change this. But indeed it is not clear that it changes for everyone and not just for you. This still doesn’t change the

@AdVhPkgKad

• it doesn’t help if there is a level of polymorphism which requires more nuance than a blanket solution.

problem you state, but I am not sure what solution would make sense here… how can the system know which form you need when you press “C”.

@AdVhPkgKad

• Forms open in ‘Compact’ mode, always

100%! I also don’t like the fact this is set per view and not per form. This should be form settings, not view settings. The number of fields and the form type usually indicates if it should be full or compact, not the view in which it is in. So it doesnt make sense to have it a per view setting.

---

I am wondering what you think of this: Open new entity in side panel for data input instead of form or in-line I think it’s somewhat related. Basically opening it directly in entity view, and you can then set rules on the entity view on which to open (solving the polymorphic issue). Then it’s not set per view, but as a filter on the data of the entity itself. What do you think?