How to set a list search to "contains" without changing the property （リスト検索をプロパティを変更せず、次の値を含む にする方法

[nanamimakin]

リスト検索について、開発している環境プロパティを変更することができませんが、

「次の値を含む」で検索されるようにしたいです。
リンクのドキュメントに、「辞書プロパティを使用した当然の検索動作の設定」として、ディクショナリのプロパティに
「goto_use_starts_with=true」を設定することで、「次で始まる 」を適用することができる記述がありますが、同じように「次の値を含む」
プロパティの変更、「*」などのワイルドカードを利用した検索は行いたくありません。

Regarding list searches, I am unable to modify the environment properties of the system under development,

but I would like to configure the search to use a "contains" (includes the value) match.
The linked documentation describes a method for configuring default search behavior for dictionary properties—specifically by setting `goto_use_starts_with=true` to enable a "starts with" match—but I do not wish to modify properties or use wildcards (such as `*`) to achieve a "contains" match in a similar way.

[Tanushree Maiti]

Hi @nanamimakin 

(in English)

Enable contains auto-complete searches

By default, the reference auto-complete uses a starts with search. A user preference can be created to implement a contains search.

Before you begin

Role required: admin

Procedure

1. Disable the glide.ui.ref_ac.startswith system property.
   For more information, see Improve auto-complete queries.

   Note:

   Setting the glide.ui.ref_ac.startswith system property to true overrides any existing "autocomplete.contains" settings in both user and system level preferences. This property changes the auto-complete query method for all users regardless of preferences.
2. Navigate to User Administration > User Preferences.
3. Select the preference "'<referenced table>.autocomplete.contains"'.
4. Set the value field to true.
5. Select Update.

What to do next

Log out and log back in to display the updated search.

Refer : Auto-complete for reference fields 

Also check: Search a list 

[nanamimakin]

Thank you for your reply.
The method you suggested would require changing property settings.
I would like to avoid changing settings, so that approach is not feasible.
I want to limit the scope to specific columns in a custom table,
rather than affecting the entire environment.