I want to specify a table other than kb_knowledge in the “knowledge Field Facet[kb-field-facet]”.

hkriwk1
Tera Contributor

yesterday

I want to specify a table other than kb_knowledge in the “knowledge Field Facet[kb-field-facet]”.

Specifically, I want to search the “u_kb_tag” field (reference type) in the custom-created “u_knowledge” table.

Since the out-of-the-box widget cannot be edited, I cloned the “kb-field-facet” widget and added ‘u_knowledge’ as an option to the “table” picklist in the option schema.
I also set the field name to “u_kb_tag” and tested it, but it doesn't work on the portal.
(It displays “Field Type Not Supported”.)

Has anyone else tried to do something similar?
If you have any good ideas, please let me know.

# Japanese Original text

「knowledge Field Facet[kb-field-facet]」でkb_knowledge以外のテーブルを指定したいです。


具体的には、カスタムして作成した「u_knowledge」テーブルの「u_kb_tag」フィールド（reference Type）への検索を行いたいと考えています。

OOTBのウィジェットは編集することができないため、ウィジェット「kb-field-facet」をクローンして、オプションスキーマの「table」選択肢リストに「u_knowledge」の選択肢を追加しました。
フィールド名も「u_kb_tag」で設定して動作確認をしましたが、ポータル上で動作を確認できません。
（「Field Type Not Supported」の表示が出たりしてます。 ）

同じようなことをやろうとした人はいませんか？
何か良いアイデアがあれば教えてください。

Labels:
0 Helpfuls
  • 83 Views
1 REPLY 1

vaishali231
Tera Expert

yesterday

hii @hkriwk1 

 

Root Cause

 

The kb-field-facet widget is tightly coupled with the Knowledge Search framework.
It only supports indexed fields from the kb_knowledge table or tables that extend it.

Even if you clone the widget and update the option schema, the backend validation still checks:

Whether the table is part of the Knowledge search index

Whether the field type is supported for faceting

Custom tables and reference fields are not supported by the out of the box knowledge facet logic.

 

Why This Happens--

Knowledge facets work only on fields indexed by the Knowledge Search Index

That index is built specifically for kb_knowledge

Reference fields require special handling and are not supported for faceting

UI changes alone cannot override backend search limitations


Solutions

1: Extend kb_knowledge
If feasible, extend kb_knowledge instead of creating a standalone table.
Use a supported, indexed field type (string or choice) for faceting.
Avoid reference fields for facets.

2: Custom Search Source + Custom Facet Widget
Create a custom search source for u_knowledge
Index the required fields
Build a custom facet widget using the Search API
This gives full control and is the cleanest solution for custom tables

3: Custom Filter Widget
Replace the facet with a simple custom filter widget
Filter results based on u_kb_tag using GlideRecord or Search API
Not a true facet, but works reliably on Service Portal


*************************************************************************************************************
If this response helps, please mark it as Accept as Solution and Helpful.
Doing so helps others in the community and encourages me to keep contributing.

Regards
Vaishali Singh

0 Helpfuls