{"section":"known-issues","requestedLocale":"en","requestedSlug":"conflict-between-specifications-with-the-same-name-at-the-intelligent-search","locale":"en","slug":"conflict-between-specifications-with-the-same-name-at-the-intelligent-search","path":"docs/en/known-issues/Intelligent Search/conflict-between-specifications-with-the-same-name-at-the-intelligent-search.md","branch":"main","content":"## Summary\n\n\nMultiple specifications with the same name are grouped into the same _\"facet\"_ by the Intelligent Search, which can be a problem if they have different settings.\n\nSome attributes that may be affected are the filter, hidden and indexed/searchable toggles, field type, and value position. There's no difference between being a product or SKU specification.\n\nIt is not possible to know which property will take precedence on top of the other.\n\n\n##\n\n## Simulation\n\n\nFor a store with:\n- specification named \"foo\" (ID 1) set as a filter (to appear in the storefront) and with the value \"bar\" for a product;\n- another specification named \"foo\" (but ID 2), which is not a filter, and with value \"baz\" for the same or another product.\n\nThe storefront may render a search filter for the facet/specification \"foo\" with both values \"bar\" and \"baz\" or even hide the whole filter.\n\n\n##\n\n## Workaround\n\n\nAlthough the Catalog module does not block repeated specification names, this usage should be considered wrong."}