Christopher B
5/21/24, 4:59:12 PM EDT
I am trying to change the default fields to be dataSearchers not lists. Make sure you define your beanname in the your xml files
Ian M
5/21/24, 5:00:33 PM EDT
I have <properties beanname="elasticCategorySearcher">
in a fields/questioncategory.xml file
Ian M
5/21/24, 5:00:53 PM EDT
trying to make that be a category searcher basically, it was working fine -
Christopher B
5/21/24, 5:01:29 PM EDT
Hmm your up to date? Should still work the same but I might have a typo or something
Ian M
5/21/24, 5:01:52 PM EDT
Looks like it is ignoring beanname from the fields definition file now
Ian M
5/21/24, 5:04:21 PM EDT
fixBeanNAme had this if( settings.getRoot().attributeValue("beanname") != null)
{
return;
}
Ian M
5/21/24, 5:08:16 PM EDT
I was getting an elasticCategorySearcher based on the beanname but now I'm getting an elasticListSearcher instead
Ian M
5/21/24, 5:28:00 PM EDT
I fixed it in that fixBeanName method but I will test your fix in case you have a better way
Christopher B
5/21/24, 6:06:00 PM EDT
FYI: I also added support for dataSearcher to load xml data as default data into a table. But it only does this when empty. Good for shipping defaults but not having to use an ListSearcher
Christopher B
5/21/24, 6:06:51 PM EDT
Only bad part is if you delete all the records then reindex the defaults will come back