In the case where a user can select an existing or add a new node it's more likely to be adding an existing node so it makes good UX sense to have this option displayed first in order.

screenshot

screenshot

CommentFileSizeAuthor
Screen Shot 2019-10-07 at 2.21.29 pm.png28.86 KBthe_glitch
Screen Shot 2019-10-07 at 2.23.24 pm.png111.09 KBthe_glitch

Comments

the_glitch created an issue. See original summary.

chandeepkhosa’s picture

chandeepkhosa commented

I also have this need for a project. We want to encourage users to check if the desired node already exists before they add the new node for it, for it would make perfect sense

dww’s picture

dww
we/he/they
commented
Status: Active » Closed (duplicate)
Parent issue: » #2673548: Prioritize 'add existing' in nested entity creation UX to prevent duplication.