Explicitly disallow existing nested items in Deep Insert

    • Type: Bug
    • Resolution: Fixed
    • Priority: Major
    • V4.01_WD01
    • Affects Version/s: V4.0_ERRATA03
    • Component/s: Protocol
    • None
    • Environment:

      [Proposed]

      In OData-666 we deprecated @odata.bind in favor of just using references in the related collection. This allows us to create a new entity that either creates nested entities (if the entire resource is new) or relates to existing entities (by providing just the reference).

      We should be clear that it is an error to include the content of an existing resource (not just its reference) in a POST.

            Assignee:
            Unassigned
            Reporter:
            Michael Pizzo (Inactive)
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

              Created:
              Updated:
              Resolved: