Restricting to a lower navigation level

Build filter combinations for deeper navigation levels with simple fields or category paths.

Deeper navigation, or navigation at a lower level, requires a combination of filters when you first call the FactFinder Navigation module.

Filtering for a simple data field

When you submit a deeper navigation call, pass the full filter combination in the correct order. If you filter with data fields, you need to know which FactFinder field contains each level. Assume the categories are stored in category0, category1, and category2, where category0 is the top navigation level.

For example, if navigation should go from the top-level category Clothing to the subcategory Trousers and then to Jeans, the REST call should look like this:

../rest/{apiversion}/navigation/{channel}?filter=category0:Clothing&filter=category1:Trousers&filter=category2:Jeans

Filtering for a category path field

By following the schema below, you can generate all filters required for deeper navigation from the field names and the selected navigation path.

Schema: FILTER_NAME:VALUE1/VALUE2/.../VALUEX.

Please note the suffix ROOT after the filter parameter.

In this example, the resulting filter has the name categoryROOT/Clothing and the value Trousers. Pass it in addition to the main category filter. For readability, the slashes in the example URLs are not URL-encoded.

../rest/{apiversion}/navigation/{channel}?filter=category:Clothing&filter=categoryROOT/Clothing:Trousers

../rest/{apiversion}/navigation/{channel}?filter=category:Clothing&filter=categoryROOT/Clothing:Trousers&filter=categoryROOT/Clothing/Trousers:Jeans