Inconsistent Link Field Filter Behavior in List View (like, not like, in, not in)

[thanathip]

There is inconsistent behavior when using List View filters on Link fields with operators like, not like, in, and not in.

The input becomes plain text without autocomplete, so users enter the Title value (e.g. customer name), but the filter actually works on the document name, causing incorrect results.

For example, if Customer name is CUS-0001 and title is John, then customer like "John" or customer in ["John"] will not work because the system expects CUS-0001.

This is confusing because other Link field inputs allow searching by Title.

Is this intended, or can it be improved to support autocomplete or Title-based filtering?

[umair]

@Dipen.Gala can you validate please?

[Dipen.Gala]

Did you try searching with ID and Customer Name? Please share screenshots/GIF

[thanathip]

@Dipen.Gala

Example

This is my Custom App Doctype Customer that have field customer_group link to Doctype Customer Group

In Customer Group Doctype. I set field description as Title Field

Also check “Show Title in Link Fields”

Example data that i created for Customer Group

Now In Doctype Customer field customer_group display like this (display description field instead of name)

Also in Listview when user filter with “Equal” condition they can search with name or title

but if they “Like”, “In” or “Not in” condition now they need to type in “name” of Customer Group only

I expect that if a DocType has a Title Field set, filters like Like, In, and Not In should work when the user enters a value matching that Title Field.

[Dipen.Gala]

Can you replicate this with any core field and share the GIF?

[kamransuleymanli]

Interesting, hadn’t notice this.
You can use github for raising an issue

Issues · frappe/frappe