OData Features Supported by Mock Server
List of OData version 2.0 features supported by mock server
Mock server only supports the JSON format for representing the resources it exposes, such as collections, entries, and links.
|
Feature |
Status |
|---|---|
| CRUD calls |
Supported |
|
Navigations |
Supported |
|
Query String options: |
|
|
- Orderby System Query Option ($orderby) |
Supported |
|
- Top System Query Option ($top) |
Supported |
|
- Skip System Query Option ($skip) |
Supported |
|
- Filter System Query Option ($filter) |
Supported; eq, ne, gt, lt, ge, le, substringof, startswith, endswith, and, or |
|
- Expand System Query Option ($expand) |
Supported |
|
- Select System Query Option ($select) |
Supported |
|
- Inlinecount System Query Option ($inlinecount) |
Supported |
|
- Format System Query Option ($format) |
Supported; only JSON format is allowed |
|
Service operations (function imports) |
Unsupported, but can be extended |
|
Batch processing |
Supported |
|
Multiple services |
Supported; we recommend to create one Mock Server instance per service |
|
Update via MERGE/PATCH |
Supported |
|
ETag handling |
Supported |
|
Annotations |
Unsupported |
|
Getting individual properties of an entity ($value) |
Unsupported |
|
Date/time values |
All dates have to be either before 2017 or after; you cannot use mixed values |