# Date-range field inconsistency between UI and API

**URL:** <https://community.fibery.io/t/date-range-field-inconsistency-between-ui-and-api/9498>\
**Category:** Bugs & Issues\
**Created:** [August 29, 2025, 1:46pm UTC](https://community.fibery.io/t/date-range-field-inconsistency-between-ui-and-api/9498 "2025-08-29T13:46:31Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![Mykhailo\_Molokov](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/mykhailo_molokov/32/12561_2.png) [@Mykhailo\_Molokov](https://community.fibery.io/u/Mykhailo_Molokov)\
**Post date:** [August 29, 2025, 1:46pm UTC](https://community.fibery.io/t/date-range-field-inconsistency-between-ui-and-api/9498/1 "2025-08-29T13:46:31Z")

</div>

When using a Fibery `fibery/date-range` field, the UI allows selecting the same date as both the `start` and `end`. However, when sending the same range via the API, Fibery rejects it with a parsing error.

`[{“success”:false,“result”:{“name”:“entity.error/parse-entity-field-failed”,“message”:“Cannot parse "Employee Management/Leave" entity "Employee Management/Planned" field.”,“data”:{“top”:{“error/name”:“entity.error/parse-entity-field-failed”,“type”:“Employee Management/Leave”,“field”:“Employee Management/Planned”,“entity”:{“Employee Management/BobID”:“42254322”,“Employee Management/Category”:{“fibery/id”:“d41f85b0-cf12-11ed-aebc-7f8a160b044e”},“Employee Management/Planned”:{“end”:“2025-09-01”,“start”:“2025-09-01”},“fibery/id”:“b406f133-93c7-4fcc-9356-c9aba1401ad6”}},“cause”:{“error/name”:“runtime.error/date-range-invalid”,“start”:“2025-09-01”,“end”:“2025-09-01”},“type”:“Employee Management/Leave”,“field”:“Employee Management/Planned”,“entity”:{“Employee Management/BobID”:“42254322”,“Employee Management/Category”:{“fibery/id”:“d41f85b0-cf12-11ed-aebc-7f8a160b044e”},“Employee Management/Planned”:{“end”:“2025-09-01”,“start”:“2025-09-01”},“fibery/id”:“b406f133-93c7-4fcc-9356-c9aba1401ad6”}},“cause-message”:“Range start must be strictly less than upper end. Value: "2025-09-01", "2025-09-01".”,“cause-data”:{“error/name”:“runtime.error/date-range-invalid”,“start”:“2025-09-01”,“end”:“2025-09-01”}}}]`

---

<div class="post-metadata">

**Author:** ![Chr1sG](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/chr1sg/32/3941_2.png) [@Chr1sG](https://community.fibery.io/u/Chr1sG)\
**Post date:** [August 29, 2025, 1:51pm UTC](https://community.fibery.io/t/date-range-field-inconsistency-between-ui-and-api/9498/2 "2025-08-29T13:51:11Z")

</div>

You might want to read [this](https://the.fibery.io/@public/User_Guide/Guide/Date-Ranges-in-Formulas-42).  
It explains why the backend and the UI are different.