@tatetopggg93cb wrote:
When using Magento Live Search with a custom EAV attribute that relies on a custom source model, such as an "author" attribute stored in a separate table with labels like author_name, facet bucket titles may incorrectly display the option IDs instead of the intended labels. This happens because Live Search doesn't support custom source models for facets—it expects option labels to be stored in Magento's standard eav_attribute_option_value table. Since your custom attribute pulls labels from a dedicated table, Live Search cannot access them directly, resulting in IDs being shown as facet labels. To resolve this, you'll need to synchronize your custom labels into the eav_attribute_option_value table, either through a custom data sync, an indexer extension, or a plugin that populates these values alongside your custom source model. Alternatively, if using Live Search is not a strict requirement, sticking to Magento’s standard layered navigation will correctly display the custom labels, as it supports custom source models out of the box. Another workaround is to use frontend JavaScript to map the displayed IDs back to their labels at runtime, but this is more of a patch than a true fix. Ultimately, the cleanest solution is ensuring Live Search can access labels in the format it expects.
The problem with synchronizing custom labels into eav_attribute_option_value is that since a custom source model stores its label/options in a separate table, there will be overlap and conflict between the primary keys (option_ids) in eav_attribute_option_value and the primary keys in that separate table.
The Boundaries and Limits document clearly directs us to use the Product Listing Widget if we're using a custom source model, but in fact the Product Listing Widget does not appear to work with our custom source model, even though that model appears to implement all documented requirements.
