Developer forum

I Am not sure how to do that. Should it then tick it if just one value in the array is matched...? And I am not sure I understand why it differs when searching and not.

Hi Nicolai,

The expectation is that the option shows up, because there's at least 1 of the values that fits that option.

Example:

• Product A
  • ​PropertyX = 1
• Product B
  • PropertyX = 2
• Product C
  • ​PropertyX = 3
• Facet List Options (for PropertyX)
  • Odd numbers = 1, 3
  • Even numbers = 2

Currently the facet would only list the option "Even numbers", but it should list "Odd numbers", picking up 2 products.

Does that make sense?

Best Regards,

Nuno Aguiar

This would mean 

I get it, maybe...

I am not sure I can get Lucene to do that. That would require that the ​PropertyX field is also an array with the in statement to the value.....

I understand what you are trying to achieve - but if above does not work, I do not know how I should make it work. Not even by refactoring our code.

Hi Nicolai,

I'll keep my fingers crossed. Let me know when you have something (yay or ney) because I need to get back to the customer about it and figured out how to workaround this(not even sure if we can either).

Best Regards,

Nuno Aguiar

I am not doing more.

You could try what I wrote: "That would require that the ​PropertyX field is also an array with the in statement to the value"

You can maybe change how that is setup. Facets and how they are calculated is out of our hands to change in this context.

And come to think of it - you should not do your data wash using the facet options. Instead of just having mess, you now have mess with mess on top, and thats a mess....!

Hi Nicolai,

Yep, I hate messes... I will see what I can come up with.

Thanks,

Nuno