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

[Paul Kunze]

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.

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

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.

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

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

[Community Alums · Accepted solution]

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

Thanks.

[ntera4sho1]

Hi Paul,

Here is what worked for me without using Page Route Maps. I created my AI Search Results Action Configuration and it works. I'm just sending this incase you are still using the Page Route Maps there.

[Jonathan Baker]

Go to AI Search > Service Portal > Search Results Actions and you can add the new portal in the "Service Portals" list collector on the AI Search Results Action Configuration

Repeat for all related action configurations 

[Wayne_Leonard]

I believe the most correct solution would be to configure the AI Search Results Action Configurations for the portal. If you go to AI Search Results Action Configurations. If you go to Service Portals => Properties => Search Results Actions you'll be able to see which actions are configured for the source portal that you copied, you can then add your new portal to the list of portals in that record. That should cause the copied portal to have the same behaviour for clicking through on search results.

[Paul Kunze · Accepted solution]

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.

[OscarD]

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.