14.2: Explicitly allow annotations on deleted entities

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

      Proposed

    • Hide

      Support annotations in the following:
      -AddedLinks
      -DeletedLinks
      -Deleted Entries
      -References

      In JSON, clients should be prepared for annotations in any object and any name/value pair in a json payload. Clients should never error on an unexpected annotation.

      Show
      Support annotations in the following: -AddedLinks -DeletedLinks -Deleted Entries -References In JSON, clients should be prepared for annotations in any object and any name/value pair in a json payload. Clients should never error on an unexpected annotation.

      The delta format identifies deleted entities via their entity id.

      For legacy systems that don't store the entity id and only know the underlying key values it would be helpful if the sender would annotate the deleted entity JSON objects with the original key values, e.g.

      {
      "@odata.context":"#Customers/$deletedEntity",
      "id":"Customers('ANTON')",
      "@Legacy.entityKey":

      { "ID":"ANTON" }

      ,
      "reason":"deleted"
      }

            Assignee:
            Unassigned
            Reporter:
            handl
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

              Created:
              Updated:
              Resolved: