Unclear or non-working where function for query with date field #350

Activity

1. sunil-lakshman commented on Apr 9, 2026

   

   sunil-lakshman

   on Apr 9, 2026

   Last edited by sunil-lakshman

   Contributor

   More actions

   @pandabrand Thanks for the detailed example. 🙌

   How dates are represented
   In the Content Delivery API, Date fields are returned and queried as ISO-8601 strings (for example, "2026-04-09T07:45:23.000Z"). They are not stored as a bare year and not as a numeric timestamp.

   Why QueryOperation.INCLUDES with years returns no rows
   INCLUDES maps to the $in operator, which only matches when the field value exactly equals one of the values in the array.
   So if an entry has "date": "2026-04-09T07:45:23.000Z", passing ["2025", "2026"] will not match. This is expected behavior and not an SDK issue.

   Recommended approach — use ISO date ranges

   Example using the TypeScript Delivery SDK:

   `import contentstack, { QueryOperator } from '@contentstack/delivery-sdk';
   
   const stack = contentstack.stack({
     apiKey: 'YOUR_API_KEY',
     deliveryToken: 'YOUR_DELIVERY_TOKEN',
     environment: 'YOUR_ENVIRONMENT',
   });
   
   // One year: date field must fall inside this ISO range
   const res = await stack
     .contentType('ct1')
     .entry()
     .query({
       date: {
         $gte: '2026-01-01T00:00:00.000Z',
         $lte: '2026-12-31T23:59:59.999Z',
       },
     })
     .find();`
   
   

   Multiple years — combine ranges using OR

   `const y2025 = stack.contentType('ct1').entry().query({
     date: {
       $gte: '2025-01-01T00:00:00.000Z',
       $lte: '2025-12-31T23:59:59.999Z',
     },
   });
   
   const y2026 = stack.contentType('ct1').entry().query({
     date: {
       $gte: '2026-01-01T00:00:00.000Z',
       $lte: '2026-12-31T23:59:59.999Z',
     },
   });
   
   const resOr = await stack
     .contentType('ct1')
     .entry()
     .query()
     .queryOperator(QueryOperator.OR, y2025, y2026)
     .find();`
   

   Alternatively, if you frequently need to filter by year, you may consider storing a separate year field (string or number) and using $in directly.
2. pandabrand

   closed this as completedon Apr 9, 2026