Skip to content

Importing OData metadata

File ▸ Import (Ctrl+I) then:

  • an .edmx file;
  • the URL of your service’s $metadata endpoint — the most convenient route;
  • a CSDL JSON document (OData 4.0 / 4.01).

All three EDMX variants — v2, v3 and v4 — are recognised.

The tree produced by an OData import: an environment folder at the root, one sub-folder per entity set, and the CRUD requests (List / Get by Id / Create / Update / Delete) generated inside each

ElementWhat Restorm makes of it
Each entity setA folder holding its CRUD requests
ActionsAn Actions folder
FunctionsA Functions folder
The entity type and its propertiesPre-filled on each OData request
Navigation propertiesPre-filled (they feed $expand)
Operation parametersTyped, with their qualified CSDL type
Query options$filter, $select, $top, $skip prepared in advance
ModelsThe API documentation

The environment folder produced is tagged with the OData version detected, which then drives the requests’ behaviour.

The imported metadata feeds the $filter field’s autocompletion: property names and operators are offered as you type.

OData is one of the re-syncable formats. See Updating from the source.