Faceted Search Widget links to ?id=form instead of ?id=sc_cat_item

Paul Kunze
Kilo Sage

Hello community,

 

I am experiencing a strange behavior in the links of the "Faceted Search" widget and want to ask if someone knows a solution.

When I search for a Catalog Item (for example "Create Service Offering") in the OOTB Portal /esc then I can see the correct item in the search results.

PaulKunze_1-1684238311657.png

And when I click the button "Request" then it redirects to the correct page ?id=sc_cat_item.

PaulKunze_0-1684238164129.png

 

Now I cloned this Portal, named it /custom (instead of /esc), but configured it the same way as the OOTB Portal.

The search returns the same results as the /esc Portal.

PaulKunze_2-1684238433689.png

But when I click the button "Request" then it redirects to the wrong page ?id=form&table=sc_cat_item.

PaulKunze_3-1684238534657.png

 

How can I correct this routing so that it shows the right Catalog Item page?

2 ACCEPTED SOLUTIONS

Not applicable

@Paul Kunze , Oh! If not, then create one as per your needs. Try this workaround; maybe it helps.

Thanks.

View solution in original post

Paul Kunze
Kilo Sage

I finally found the reason (the root cause) for the behavior and want to share it.

It occurred because we have a custom Portal and activated AI search but with some wrong configurations.

The entries in table "AI Search Results Action Configurations" (sp_ai_search_results_action_config) need to be set up so that the correct Service Portals, Search Sources and Portal pages are connected.

 

PaulKunze_1-1702379278604.png

 

View solution in original post

10 REPLIES 10

OscarD
Tera Contributor

After alot of reading and trying to find this problem i found a solution, which SN gives us hidden deep. The problem is AI Search, so either disable it, or if you want to have it you can deactivate another feature. The Search Application is ESC Portal Default Search Application which is in the sys_search_context_config. Click on ESC Portal Default Search Application and remove the Enable Exact Match choice. This worked out for me!

 

SN gives us alittle pop up which says Portals do not support exact match. If you enable the exact match option in a portal's search application configuration, users may experience navigation issues when searching in that portal.