Hello Experts,
I created a new Indexed source for Order guide and mapped Search source. The new tab is visible in the Employee center but the Order guide short description and description is not visible. Attached the screenshot below;
Am i missing any configuration?
Thanks,
Arun
You will need to create Field Settings on the Indexed Source to map the fields to the AI Search Index Fields. This is where some get creative and map custom fields to invalid AIS Index Fields, which will throw warnings during indexing.
There are only two AI Search Index Fields, "text" and "title" for which the map_to attribute can be used to map to fields on the table. Typically, the short_description field is mapped to "title" and the description field is mapped to "text", but for Indexed Sources on tables such as [incident], you would map the number field to the "title" and the short_description field to "text". Here is an example of these two map_to attributes on the Indexed Source for [sc_cat_item], and are automatically applied to all child tables in the Indexed Source, as they inherit these fields from the parent table -
Out-of-box, table [sc_cat_item_guide] is a child table on the Indexed Source for table [sc_cat_item], and not a separate Indexed Source. If your business requirement is to only allow users to search for Order Guides, then having a separate Indexed Source on table [sc_cat_item_guide] is a valid configuration. However, please note that you cannot create multiple Indexed Sources on a single table.
Please also ensure you add the "no_text_index" attribute on fields that should not be indexed. You should also add this attribute "no_text_index" on fields that are frequently updated and generate too many [sysevent] records in the ais_index queue that can impact incremental indexing performance. This usually occurs with integrations that are triggered daily to bulk update records without any meaningful updates on fields that are not searched on, such as custom datetime fields.
I hope this helps.
Regards,
Brian
You will need to create Field Settings on the Indexed Source to map the fields to the AI Search Index Fields. This is where some get creative and map custom fields to invalid AIS Index Fields, which will throw warnings during indexing.
There are only two AI Search Index Fields, "text" and "title" for which the map_to attribute can be used to map to fields on the table. Typically, the short_description field is mapped to "title" and the description field is mapped to "text", but for Indexed Sources on tables such as [incident], you would map the number field to the "title" and the short_description field to "text". Here is an example of these two map_to attributes on the Indexed Source for [sc_cat_item], and are automatically applied to all child tables in the Indexed Source, as they inherit these fields from the parent table -
Out-of-box, table [sc_cat_item_guide] is a child table on the Indexed Source for table [sc_cat_item], and not a separate Indexed Source. If your business requirement is to only allow users to search for Order Guides, then having a separate Indexed Source on table [sc_cat_item_guide] is a valid configuration. However, please note that you cannot create multiple Indexed Sources on a single table.
Please also ensure you add the "no_text_index" attribute on fields that should not be indexed. You should also add this attribute "no_text_index" on fields that are frequently updated and generate too many [sysevent] records in the ais_index queue that can impact incremental indexing performance. This usually occurs with integrations that are triggered daily to bulk update records without any meaningful updates on fields that are not searched on, such as custom datetime fields.
I hope this helps.
Regards,
Brian
Hi @Brian Bakker, we are currently encountering kind of same issue for Record Producers, we already have the Field Settings and Mappings like what you have on your example and the short_description is showing on the Search Result however the text is cutoff.
This is how it looks like, and I check Catalog Item and the short_description is showing properly I have observed that it is only happening to record producers.
Record Producer
Catalog Item
