Search Results
| Search type | Search syntax |
|---|---|
| Tags | [tag] |
| Exact | "words here" |
| Author |
user:1234 user:me (yours) |
| Score |
score:3 (3+) score:0 (none) |
| Answers |
answers:3 (3+) answers:0 (none) isaccepted:yes hasaccepted:no inquestion:1234 |
| Views | views:250 |
| Code | code:"if (foo != bar)" |
| Sections |
title:apples body:"apples oranges" |
| URL | url:"*.example.com" |
| Saves | in:saves |
| Status |
closed:yes duplicate:no migrated:no wiki:no |
| Types |
is:question is:answer |
| Exclude |
-[tag] -apples |
| For more details on advanced search visit our help page | |
Results tagged with odata
Search options questions only
not deleted
user 3334
Open Data Protocol, is an open protocol to allow the creation and consumption of queryable and interoperable RESTful APIs in a simple and standard way. All question related to OData in reference with Sitecore should use this tag.
5
votes
1
answer
346
views
Component is an OData Entity and thus a NavigationProperty
, for example:
<NavigationProperty Name="Components" Type="Collection(CustomComponent)" />
Navigation properties are by default not handled by the OData server. … Any good reasons why a Component is not an OData complex type (this could be achieved by not having the [Key] annotation on the Component class)? …
- 1,917