Search on portal not working after the clone

poojitha bn · ‎07-22-2019

Hi team,

We have cloned Test instance today, post cloning Typeahead search are not working on portal but Its working in DEV and PROD instance.

I have checked below things but didn't get find any solution

Search sources are available in related list of portal as same as dev
Global text search setting is same as dev
Typeahead search widget is OOB widget which is read only as same as dev
Text search groups are same as DEV
Search contexts are also same as dev
Search source : knowledge base and service catalog source code are same as Dev
There is no error in console log

Please do help me where to check

Test screenshot:

Dev screenshot:

finally I executed cache.do and checked but still same issue. Please do help me what needs to be setup after the cloning for typeahead search.

Poojitha10 · ‎04-29-2020

Hi Miguel,

I found a route cause for this issue, Its because of text indexing lag time:

I will run this below line in background script as post cloning activity

new GlideTextIndexEvent( ).indexUpdate('sc_cat_item', null);

This will index all your catalog items and you could able to search your catalog items.

View solution in original post

Allen Andreas · ‎07-22-2019

Hello,

Which way did you clone? Did you clone Production down to Test or Dev up to Test?

In your screenshots and everything you're talking about...you're mentioning Dev...

So did you clone Dev to Test?

Also...is this cloning just standard clone...or was this due to an upgrade to another version of ServiceNow?

Please mark reply as Helpful/Correct, if applicable. Thanks!

Please consider marking my reply as Helpful and/or Accept Solution, if applicable. Thanks!

poojitha bn · ‎07-22-2019

Hi Allen,

we cloned from PROD to Test. I just compared all the code to dev instance since DEV is working fine.

Typeahead search is working fine in Dev and PROD but post cloning all contextual search not working on portal.

Thanks,

Poojitha B Nagaraj

Allen Andreas · ‎07-23-2019

Right, but logically, you'd want to compare to Prod...which is where your clone came from.

I would double-check your production instance pieces to your Test instance and see if everything still matches. Be advised that the code can look the same...but they'd need to be active as well.

We are unsure what excluded tables you have in your clone...so providing that information would help, but I'd also recommend checking your Knowledge Base settings for your Test portal to ensure it's searching appropriately.

Please mark reply as Helpful/Correct, if applicable. Thanks!

Please consider marking my reply as Helpful and/or Accept Solution, if applicable. Thanks!

SatheeshKumar · ‎07-22-2019

HI Poojitha,

Did you verified text re-indexing is completed, post cloning text re-indexing will happen, this will take some hours to complete , searches will not work properly untill the indexing is completed.

check the below link for morre details:

https://hi.service-now.com/kb_view.do?sysparm_article=KB0552002

verify test indexing is completed or not:

https://hi.service-now.com/kb_view.do?sysparm_article=KB0694751

to make the text indexing faster follow below link:

https://hi.service-now.com/kb_view.do?sysparm_article=KB0687779

-satheesh