[Go to site: main page, start]
Scribd
Upload
6 views1 page

OData Binding Path Syntax Explained

You can access data from an OData service using binding paths that correspond to the structure defined in the service metadata. Binding paths can be absolute, starting with a slash, or relative. Relative paths require a context to be resolved to an absolute path. Navigation properties identify single entities or collections and use paths like "/Customers('ALFKI')/Orders" to represent relationships between entities.

Uploaded by

ekampreet
Copyright
© All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
6 views1 page

OData Binding Path Syntax Explained

You can access data from an OData service using binding paths that correspond to the structure defined in the service metadata. Binding paths can be absolute, starting with a slash, or relative. Relative paths require a context to be resolved to an absolute path. Navigation properties identify single entities or collections and use paths like "/Customers('ALFKI')/Orders" to represent relationships between entities.

Uploaded by

ekampreet
Copyright
© All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd

Addressing Entities: Binding Path Syntax

You access the data provided by the OData model according to the structure of the OData service as defined in the metadata of a service. URL parameters, such as filters, cannot be added to a binding path. A binding path can be
absolute or relative. Absolute binding paths are resolved immediately. A relative path can only be resolved if it can be automatically converted into an absolute binding path. If, for example, a property is bound to a relative path and
the parent control is then bound to an absolute path, the relative property path can e resolved to an absolute path.

The following binding samples within the ODataModel are taken from the Northwind demo service.

Absolute binding path (starting with a slash ('/')):

"/Customers"
"/Customers('ALFKI')/Address"

Relative binding paths that can be resolved with a context (for example "/Customer('ALFKI')"):

"CompanyName"
"Address"
"Orders"

Resolved to:

"/Customer('ALFKI')/CompanyName"
"/Customer('ALFKI')/Address"
"/Customer('ALFKI')/Orders"

Navigation properties, used to identify a single entity or a collection of entities:

"/Customers('ALFKI')/Orders"
"/Products(1)/Supplier"

For more information on addressing OData entries, see the URI conventions documentation on [Link] .
.

You might also like