Search not working properly on an Employee Center portal clone

[Marion]

Hello everyone,

I have a problem regarding my Employee Center clone. I managed to clone/copy all the relevant pages in order to create a new Employee Center portal but the search is not working properly. AI search is not activated and the instance is not a DemoHub instance.

The OOTB EC portal does not have any search sources in its related list, but is still giving relevant results, whereas the clone EC portal gives me incomplete or empty results. I get the same stupid results when I add search sources to my cloned EC portal. My "old" (not EC) portals are all working nicely when I add the proper search sources.

Below are some examples :

OOTB EC search result on "leave" and "outlook":

Cloned EC search result on "leave" and "outlook":

I'm completely lost as to how the search function does work with this new Employee Center. From this doc I thought that adding search sources would be the answer but it doesn't make sense as the OOTB EC is working without them and my cloned EC is not working, even when I add search sources 😞

What am I missing here?

Thank you for your help!

[DiogoRamos · Accepted solution]

Hello Marion, 

Not sure if it's the same issue but it does sound familiar, check this one out: https://community.servicenow.com/community?id=community_question&sys_id=4db5b5e71bcbfc10fc3233bc1d4bcba3&anchor=answer_ac3b37e31b0b7818abbcece7624bcb16&view_source=searchResult

Cheers,
Diogo

[Marion]

Thank you for your help Diogo!

Emptying the taxonomy id is indeed helping as I now have catalog articles and knowledge articles in my cloned EC search results.

What bothers me is I still don't understand how this EC search works. Why is the OOTB EC search working properly without any code alteration, and why do I have to modify the taxonomy id lines within the search sources for it to have the same behaviour as the OOTB one? 😞

For people wondering what I mean by "emptying the taxonomy id" in the catalog and knowledge search sources:

[Rob Sestito]

Did you run the Fixed Scripts as well during all of this? I noticed this as well from the start of my implementation for the new portal. I found that you may need to (most likely will have to) run the scripts a couple of times for the script to capture and update the taxonomy needed.

Not sure if you came across the link I inserted there for the Fixed Scripts, but if you have not, it gives good info on what the scripts help with. Which includes the search.

Hope you are making good progress with this.

Cheers,

-Rob

[Marion]

Thank you Rob for this info!
It might be related to my initial issue, but from what I understand (I can't see the script so I am making assumptions here) the script only works on the OOTB Employee Center. The Employee Center portal, whose search was not working properly until I altered the search sources code, is a custom portal, so I guess whatever this script do, it won't work on my custom EC portal 😕