Uploaded image for project: 'OASIS Open Data Protocol (OData) TC'
  1. OASIS Open Data Protocol (OData) TC
  2. ODATA-376

Navigation link representation for navigation properties of complex type instances

    XMLWordPrintable

    Details

    • Type: Bug
    • Status: Closed
    • Priority: Major
    • Resolution: Fixed
    • Affects Version/s: V4.0_CSD01
    • Fix Version/s: V4.0_CSD02
    • Component/s: JSON Format
    • Labels:
      None
    • Environment:

      [Applied]

      Description

      Currently the JSON spec requires that the navigation link for a navigation property is only represented if the client requests odata.metadata=full or if the client explicitly selects the navigation property in $select.

      It would be more accurate to state that it also gets represented if it cannot be "computed"

      While "computing" works for navigation properties of an entity type (http://host/service/Set(key)/NavProp), and even for navigation properties of single-valued complex properties ((http://host/service/Set(key)/ComplexProp/NavProp), it breaks down for navigation properties of complex-valued properties.

        Attachments

          Activity

            People

            • Assignee:
              handl Ralf Handl
              Reporter:
              handl Ralf Handl
            • Watchers:
              0 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved: