Date-range field inconsistency between UI and API

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”}}}]

You might want to read this.
It explains why the backend and the UI are different.

1 Like