Open
Description
Hi team,
I’m encountering an issue with ElasticSuite related to a dropdown attribute that uses a custom source model.
Problem:
The attribute renders and works fine in product edit and on the frontend, and filtering works perfectly with Magento’s core Elasticsearch and OpenSearch search engines.
However, when using ElasticSuite, the filter bucket appears blank in layered navigation — no options are shown in the filter even though products are assigned to them and indexing is complete.
Attribute Details:
- Input Type: Dropdown
- Source Model: Custom PHP class implementing Magento\Eav\Model\Entity\Attribute\Source\SourceInterface
- Values: Returned from getAllOptions()
- Used in Layered Navigation: Yes
- Indexed by Magento and Core ES: Yes
Steps to Reproduce:
- Create a dropdown attribute using a custom source model.
- Assign values to products.
- Ensure the attribute is filterable and visible in layered navigation.
- Reindex and flush cache.
- Navigate to a category page with ElasticSuite as the search engine.
- Observe the filter options — the bucket is blank.
Expected Behavior:
Filter should display all assigned options just like it does with Magento’s core Elasticsearch or OpenSearch.
Actual Behavior:
Filter shows a blank bucket — no values displayed.
Questions:
- Does ElasticSuite support custom source models for dropdown attributes?
- Is there an additional configuration or plugin required to make custom source models work with filters?
- Any suggested workaround?
Thanks in advance!