I have a standard walk setup with custom data fields "Company", "Location"...in the xml file. When I go to do a Meta Search on this standard search these fields are not returned with the rest of the xml. How do I make sure these custom fields are accessible in the meta search?
Definitely looking forward to that patch. In the meantime can you think of anyways I might be able to access this data from the meta search? Is there a way I can store it in one of the designated fields and then extract it in the meta search into its own field...
I don't know if you can think of anything please get back to me. If not I'll wait for the patch. Thanks for your help!
I see now that Additional Fields boxes are shown in the crawl definition of Meta Searches (obviously updated from 1 year ago). However, they apparently do not work -
I have a Meta Search with 2 sub-profiles - one has the additional fields defined while the other does not. The Meta Search has the same Additional Fields defined as the sub-profile that does. However, no additional fields are exported in the results (and yes, both are set to be searchable, sortable, and exported). Ideas?
When you say "no additional fields are exported in the results", I'm assuming you're talking about the XML output, correct?
That situation shouldn't be a problem, and I'm not able to duplicate the problem here. The results from the profile that doesn't have the additional field will simply have empty elements.
Are the additional fields included in the XML output of the sub-profile that contains the field?
We found the cause - a metasearch profile that was created before scripts with Additional Fields in place will not properly output additional fields, despite having the settings for them present in its All Walk Settings.
Delete & re-create the metasearch profile, and it should be good.
