Skip to main content

Considerations for specific field types

  • The DATE_TIME operator: When using a DATE_TIME operator, you can opt to provide the time offset for your timezone or use UTC. For example, searching for records that were created after a DATE_TIME of 2022-04-25T13:00:00+02:00 should give you the same results as using the UTC equivalent date time of 2022-04-25T11:00:00+00:00. When using just the date, the local time zone will always be used.

  • The BEFORE operator: When using a BEFORE operator for dates, the date provided will not be included. If you wish to include the date provided, use the BEFORE_INCLUSIVE operator.

  • The BETWEEN operator: When using the BETWEEN operator with two dates, the start date (value parameter) will be inclusive while the end date (secondValue parameter) will be exclusive. This means that if you wish to include a record in your results that, for example, took place at 12:00pm on the 22nd July 2023, you should use 22023-07-22T12:01:00 as your end timestamp.

  • The EQUALS and EQUALS_CASE_SENSITIVE operators: If using EQUALS as the operator, true or false values are cast to boolean so true, "true", and "TRUE" should all yield the same results. This includes checkbox type custom field definitions where the value is returned as an uppercase string of either "TRUE" or "FALSE". This is not the case when using EQUALS_CASE_SENSITIVE as the operator, so, if searching based on a checkbox type custom field definition with the EQUALS_CASE_SENSITIVE operator, you will need to provide the value as an uppercase string.