Gravatar for andrew.harbert@nttdata.com

Question by adharbert, Nov 20, 2014 4:28 PM

Search page using computed fields, returning blank items

I have a Search page that I created a computed field that returns only specified items that are marked with the computed field. I run indexing and everything appears to be fine. I ran the page and it appears everything comes back correctly. When I click on the facet filters on the left side, seems like everything is still returning correctly.

Now, if I add a filter field, so if the user searches on product name, I see correct responses, but there appear to be a bunch of blank items being returned after the list runs out. I have no idea as to why these are showing up.

This is what I'm adding for the search text. It appears to work but it's returning things that don't have data.

args.queryBuilder.expression.add(queryValue);

This condition is being added to the existing setup seems to be working, but not sure why blank items are showing up.

Any thoughts would be great.

1 Reply
Gravatar for eprovost@coveo.com

Answer by √Čtienne Provost, Nov 20, 2014 5:10 PM

The approach I would take in your case would be to reproduce the query in the Index Browser of the CES Admin Tool to identify the items that looks empty in your result list.

These items look like they are not exclude by your filter and in the same time, they don't have the data that you use in your template.

If you want to take a look to the query to use in the Index Browser, you can go to your search page. Open the browser console and go to the Network tab. Do your query with the empty item. You should see a /coveo/rest appearing in the network. The majority of your query is in the aq data of this network.

Hope this help.

Gravatar for andrew.harbert@nttdata.com

Comment by adharbert, Nov 26, 2014 1:59 PM

thanks, I went through the computed field and made sure there were no logic errors. I re-indexed a few times and finally it started to work. Really not sure why it took a while for the blank ones to stop showing up, but it seems fine now.

Thanks!

Ask a question