URL query parameter for displaying disabled refinements

The Ndr parameter of the Endeca Navigation URL query syntax lets you display disabled refinements.

The Ndr parameter links to:

Java: ENEQuery.setNavDisabledRefinementsConfig() method
.NET: ENEQuery.NavDisabledRefinementsConfig property

The Ndr parameter has a dependency on the N parameter, because a navigation query is being performed.

Configuration settings for the Ndr parameter include:

<basedimID> — an ID of a dimension that is to be included in the base navigation state.
<eqlfilterinbase> — a true or false value indicating whether the EQL filter is part of the base navigation state.
<textsearchesinbase> — a true or false value indicating whether text searches are part of the base navigation state.
<rangefiltersinbase> — a true or false value indicating whether range filters are part of the base navigation state.

When the Ndr parameter equals zero, no disabled refinement values are returned for any dimensions (which improves performance).

Examples of queries with the Ndr parameter

The first example illustrates a query that lets you return disabled refinements. In this example, the Ndr portion of the UrlENEQuery URL indicates that:

Text search should be included in the base navigation state.
The navigation selections from the dimension with ID 100000 should be included in the base navigation state.

/graph?N=110001+210001&Ne=400000&Ntk=All&Ntt=television&Ndr=textsearchesinbase+true+basedimid+100000

In the second example of a query, in addition to text searches, the EQL filters and range filters are also listed (they are set to false):

N=134711+135689&Ntk=All&Ntt=television&Ndr=basedimid+100000+textsearchesinbase+true+eqlfilterinbase+false+rangefiltersinbase+false