Every record has record lists. “+ Link or create” is confusing when you want to create a new record with a formula name. This ONE button does TWO actions: link or create.
For instance, we have a parent record. The child object has the name field as a formula. When we want to add a new record, the system shows “Start typing to create a new record”. Why? After that we have to do several unnecessary clicks:
Guys, please add (or provide a setting) to just open a new record pop-up. As an idea: split “+ Link or create” button into two buttons: “Link” and “Create”.
We’re actually working on new UI representations for collection fields right now, so we have not done anything on the existing mechanism, since it will be deprecated. Can’t guarantee that the new UI will be different/better to begin with, but just mentioning why this issue has not got any attention yet, sorry.
I feel like this is close enough that my linked idea is a duplicate. @Chr1sG is there a proper way to merge this idea? If not, @cannibalflea - I think we should migrate our votes here to centralize our support for this feature.
Additional thoughts:
The create button should have the option to act like a mini version of the new form view, with all the necessary fields you want the user to fill out (including required options). This would solve the issue with filling our the necessary fields for formula names but would also help with database data hygiene (making sure the proper fields are filled out for each entity created).
If link and create actions are separated, there should be an admin option to hide one or both action buttons. I have to-many entity relation blocks that I want people to only view or interact with in a specific way.
This is a beyond the scope of this idea, but adjacent to this second bullet point - I have the same problem with Views. There are Views that I do not want to give anyone the option to create or link items - view only.
Example: We have a ‘Project Priorities’ board that pulls priority tasks from all projects that a user is on. If anyone can add new tasks to this board, it defeats the purpose of reviewing full active task logs and deciding on what the current priorities are.
They are certainly very similar, but I would say that one is perhaps a subset of the other. Namely, prompting a user to provide info when the name is built from a formula is a specific version of the general need to ask a user when a new item is created.
As it happens, the work on form view has raised questions internally about whether it could be possible to allow admins/creators to mandate form UI during the general entity creation process…
For the second bullet point, I think it’s a separate topic for discussion. It may even already exist in the community, I haven’t checked.
