V17 Backoffice search results don't show most recent node first

When searching nodes for ContentPicker in back office, the results are not displaying the most recent nodes first, which is different from V13.
Is there any way to config it differently?

Thanks.

May

Hi @mzhang-asi

I’m not aware of a way to change this behaviour and from what I can tell, the current back office examine search sorts by relevance rather then by date. If this is a regression from v13, it is worth raising this on the issue tracker to see if it can get fixed.

Justin

Thanks @justin-nevitech!

May

Sounds also like a feature suggestion, include orderby

createdate, modifiedDate, alpha.. and ASC/DESC ??

as well as the new filtering by respository :slight_smile:

it would be FANTASTIC if we could sort Content Picker results by most relevant when editors start typing - defaulting to listview sort makes sense on paper but is a terrible user experience in the backoffice when the most relevant result shows up at the bottom of the list.