Instant Search problem
I have the same map service in three different sites. I'm using HTML5 2.2 and GCE 4.1.3. I set Instant search to work on one of the sites, and I notice that the other sites recognize that I've created an index on the service already, which it didn't do in prior versions. I set the two new sites to use instant search, and on one it works fine. On the other, the hints work as expected, but selecting a hint or hitting return to do the search, no results will come up. On the one that is not working, I was using a different web adapter, so the service connection string was different. After noticing that it did not recognize that the index already existed, I switched it to use the same web adapter, and that fixed the problem about not seeing the existing index, but is somehow still causing a problem... Any ideas what to do to fix?
-
I am seeing this same issue.
I have another problem as well (logged a support ticket for it), where the status of the index has been stuck at 6% for days.
Does you search index show 100% complete for the service you are searching?
0 -
Bret,
When I enabled instant search, the search index started from zero and did not show any graduate progress until it finished and reached 100%.
I tried indexing many test services to check this behavior, but the same thing happened each time (the progress indicator was only showing the zero and the hundred percent status)
0 -
Thanks Hami, I just wanted to check your indexes had completed.
I am seeing 6% on one web service, it has been like that for a couple of weeks. I am currently working with support on this issue.
0 -
Hi Hani,
I think that the instant search in G.E 4.2.1is not working due to a bug, this needs a confirmation form LG side.
Regards,
Ahmad
0 -
Thank you Ahmed for your interest,
Actually, the instant search works and return results (please refer to the screenshots below). The problem I am facing with it, is when searching for a value that does not exist, its progress indicator keeps running (the screenshot in the first post above) which causes confusion to the end user who will wait for the result that will never appear
/customer/servlet/servlet.FileDownload?file=00P6000000eluJGEAY
/customer/servlet/servlet.FileDownload?file=00P6000000em1TrEAI
0
Bitte melden Sie sich an, um einen Kommentar zu hinterlassen.
Kommentare
5 Kommentare