---
title: Date facet range using custom date ranges returns no results
slug: n6l90064
canonical_url: https://docs.coveo.com/en/n6l90064/
collection: coveo-for-sitecore-v5
source_format: adoc
---
# Date facet range using custom date ranges returns no results


[.version.c4sc.c4sc-issue-resolved.5-0-1277-4.October-23&-2023]
[Issue resolved](https://docs.coveo.com/en/n5jd0437#release-notes)



[.version.c4sc.c4sc-issue-resolved.5-0-1277-4.October-23&-2023]
[Issue resolved](https://docs.coveo.com/en/n5jd0437#release-notes)


## Symptoms

Using a [**Coveo Date Facet Range**](https://docs.coveo.com/en/3024/) or [**Coveo Dynamic Date Facet Range**](https://docs.coveo.com/en/3211/) rendering with custom date ranges yields no results when filtering on a range (though the range shows a non-zero count).

## Cause

An issue was introduced in version 2.10107 of the JavaScript Search Framework which the affected Coveo for Sitecore renderings use.

## Resolution

The issue has been resolved in the October 23, 2023 Coveo for Sitecore release.

### Workaround

You can configure affected search pages to use version 2.10110 of the JavaScript Search Framework.

To use version 2.10110 of the JavaScript Search Framework in a search page

. Open the search page in the **Experience Editor**.

. Select the **Coveo Search Resources** rendering.
It should be located at the bottom of the page.

. In the floating toolbar, select **Edit the rendering's data source**.
It should be the leftmost option in the toolbar.

. In the **JavaScript Search Resources** section, clear the **Use local files for Coveo JavaScript Resources** checkbox, if necessary.

. In the **Coveo JavaScript Search Framework CDN Version** field, enter `2.10110` and click **OK**.

. Validate that your search page date facet ranges now work properly in the **Experience Editor**.

. Publish your changes.