Odata Cheat Sheet



How to construct an annotation from a term definition, or re-engineer a term definition from an annotation example?

  1. Odata Query And
  2. Odata Source Editor
  3. Odata Query Cheat Sheet
  1. The OData standard is in many ways the most flexible and easiest integration option for WEM, you can expose all your data from your WEM project and have any other application supporting the OData standard interact with that data, where reading, updating and writing are all possible. WEM can also consume OData exposed services.
  2. I think I found a bug: works perfectly at sharepoint list (get items) (however at odata cheat sheet title and value are in opposite site I'm not sure it's correct). When I tried to use the same ODATA filter at excel list (list a rows) it stopped working. Also I came to the p.

Odata netweaver gateway web api client references feedback Previous module: client. Introduction GitHub Cheatsheet Markdown Cheatsheet Glossary Course template.

Cheat

Here’s how.

Vocabularies

Terms are defined within a “vocabulary”, which is just an EDMX document.

To use a term in an annotation, the vocabulary of the term needs to be referenced and included.

Primitive Terms

If the term has a primitive type

A constant annotation value can be provided in a corresponding attribute.

See Constant Annotation Values for a list of all attributes and example values for them.

A dynamic annotation value can be provided for the same term using a value path expression.

The property referenced via the value path expression, here SomeStringProperty needs to have the same type as the term. A value path expression can always be used instead of a constant value, also in the more complicated cases below.

Collections

If the term has a collection type

the annotation value is provided as a collection expression

Structures

If the term has a structured type

the annotation value is provided as a record expression

Constant annotation values for primitive properties are provided in the same way as for primitive terms.

Collection of Structures

Terms can also be typed as a collection of a structured type.

The annotation value is provided as a collection of records.

Properties that are nullable or have a default value can be omitted.

Nested Structures and Collections

Properties of a structured type can themselves be structured or collections.

The property value is provided as a record or collection.

Constant Annotation Values

Odata Query And

The name of the attribute to provide a constant annotation value depends on the type of the term or term property.

Odata Source Editor

Type of Term or Term PropertyAttribute with Example Value
Edm.BinaryBinary='T0RhdGE'
Edm.BooleanBool='true'
Edm.DateDate='2000-01-01'
Edm.DateTimeOffsetDateTimeOffset='2000-01-01T16:00:00.000Z'
Edm.DecimalDecimal='3.14'
Edm.DurationDuration='P7D'
Enumeration TypeEnumMember='org.example.Pattern/Red'
Edm.Double or Edm.SingleFloat='3.14'
Edm.GuidGuid='21EC2020-3AEA-1069-A2DD-08002B30309D'
Edm.Int16, Edm.Int32, Edm.64, Edm.Byte, Edm.SByteInt='42'
Edm.StringString='annotation value'
Edm.TimeOfDayTimeOfDay='21:45:00'
Edm.AnnotationPathAnnotationPath='Product/Supplier/@UI.LineItem'
Edm.NavigationPropertyPathNavigationPropertyPath='Supplier'
Edm.PropertyPathPropertyPath='Details/ChangedAt'

Odata Query Cheat Sheet

This site is open source. Improve this page.