v2.0

This page lists and describes all the client facing features included in v2.0.

Feature	Description
$filter lambda support	Implement support for odata lambda operators OData Lambda docs. Examples: - `$filter=ConstructionMaterials/all(t:t eq 'Brick')` - `$filter=ConstructionMaterials/any(t:t eq 'Brick')` - `$filter=ConstructionMaterials/any(t:t eq 'Brick') and ConstructionMaterials/any(t:t eq 'Other')` - `$filter=ConstructionMaterials/all(t:t ne 'Brick')` - `$filter=ConstructionMaterials/all(t:(startswith(t, 'Bri')))`
support $filter operations and queries	Implement support for odata filter operations and queries OData Query docs. - Logical operators: `not` - Arithmetic operators: `add`, `sub`, `mul`, `div`, `mod` -String and Collection Functions: `endswith()`, `concat()`, `indexof()`, `length()`, `substring()` - Date and Time Functions: `now()`, `day()`, `hour()`, `minute()`, `month()`, `second()`, `year()`, `date()`, `time()`, `mindatetime()`, `maxdatetime()` - Arithmetic Functions: `round()`, `floor()`, `ceiling()` - Type Functions: `cast()` - Geo Functions: `geo.distance()`, `geo.intersects()`
support $expand	Implement support for odata expand OData Expand docs. OData $expand lets clients include related entities inline with a primary query. You can nest $filter and $select within each expanded part to retrieve only the relevant fields or rows, reducing extra requests and tailoring the response for your needs. Example: -`$expand=Media($select=MediaKey,MediaModificationTimestamp,MediaURL,MediaType;$filter=MediaType eq 'image/jpeg'),Rooms($select=RoomKey,RoomType,ListingKey;$filter=RoomType eq 'Kitchen')`
support odata batch	Implement support for odata batch OData Batch docs. OData batch support allows a client to send multiple requests in a single call to the `/$batch` endpoint. You can combine queries, data updates, or function calls into one request, reducing network round‑trips. Responses come back in the same order as the requests, and grouped updates (change sets) are applied together, making it easier to coordinate multiple operations from the client side.
implement queue resource	Implement `queue` resource entity as per the RESO Data Dictionary 2.0 spec
support @odata.nextLink paging feature	Implement support for @odata.nextLink OData NextLink docs. `@odata.nextLink` is returned when a query result is paginated. It provides a URL the client can call to retrieve the next page of results, enabling efficient handling of large datasets without fetching everything at once.