Use Hierarchical Facets

Coveo JavaScript Search Framework (January 2019)

If some items in your index follow a logical hierarchical structure, you may want to display a facet that allows end users to navigate your item hierarchy accordingly. This article explains how to use the DynamicHierarchicalFacet (or the CategoryFacet) component to do so.

The DynamicHierarchicalFacet component is available since the January 2020 Release (v2.7968).

This component works in a similar fashion to the older CategoryFacet component. However, we recommend that you use the DynamicHierarchicalFacet, because this newer component supports the Coveo Machine Learning (Coveo ML) Dynamic Navigation Experience (DNE) feature.

To use the DynamicHierarchicalFacet (or CategoryFacet) component in a search interface

  1. Ensure that your index contains a multi-value field representing the item hierarchy (see Manage Fields). The field values must have the following form the; the|path; the|path|to; the|path|to|given; the|path|to|given|item;, where the delimiting character is |.

  2. Include the component in your HTML page.

    You have indexed the following file system:


    The @parentfolders contains values representing the path to each of those items in the file system hierarchy.

    Item @parentfolders field value
    text1.txt c; c|user1; c|user1|folder1;
    text2.txt c; c|user1; c|user1|folder2;
    text3.txt c; c|user1; c|user1|folder2; c|user1|folder2|folder3;

    In your search page, you include the CoveoDynamicHierarchicalFacet component.

    <div class="CoveoDynamicHierarchicalFacet" data-title="Folder"


You can only select one value at a time in a hierarchical facet. This is because those facets are meant to ease navigation through hierarchically organized content (e.g., exploring product categories), as opposed to applying multiple hierarchical filters.

You have a search page for your store, where you sell electronics and office supplies. You use a hierarchical facet titled Product Category on the @productcategory multi-value field. This allows your end users to navigate the product hierarchy.


To refine result filtering, create dependent facets on the target hierarchical facet values.

You want the Brand facet to show when users select paper in your hierarchical facet, and you want the Pen Type facet to show when users select pen in your hierarchical facet.

<div id="search" class="CoveoSearchInterface">
  <!-- ... -->
  <div class="coveo-facet-column">
      <div class="CoveoDynamicHierarchicalFacet" 
         data-title="Product Category"
      <div id="brand_facet" 
      <div id="pentype_facet" 
         data-title="Pen Type" 
  <!-- ... -->
   // ...
   document.addEventListener('DOMContentLoaded', function () {
      // ...
      const root = document.getElementById("search");
      function isSelectedInParent(value) {
         return (parentFacet) => {
            const id =;
            const selected = parentFacet.queryStateModel.get(`f:${id}`);
            return selected.includes(value);
      Coveo.init(root, {
         brand_facet: {
            dependsOn: "@productcategory",
            dependsOnCondition: isSelectedInParent("paper")
         pentype_facet: {
            dependsOn: "@productcategory",
            dependsOnCondition: isSelectedInParent("pen")


Setting the Base Path

The DynamicHierarchicalFacet supports the basePath option since the April 2020 Release (v2.8864).

When all items in a hierarchical relationship resolve to a unique common ancestor, you may want to use the basePath option of the CategoryFacet component to eliminate this redundancy.

<div class="CoveoCategoryFacet" data-title="Folder"
     data-field="@parentfolders" data-base-path="c,user1"></div>


Pro and Enterprise editions only

When using Data Categories in Coveo for Salesforce, you can add the basePath option in the CoveoCategoryFacet element to start counting your fields at the second level, which is the folder field.

Recommended Articles