Annotate a property as "cannot be specified on insert, can be updated later"

    • Type: New Feature
    • Resolution: Fixed
    • Priority: Major
    • V4.0_CSD02
    • Affects Version/s: V4.0_CSD01
    • Component/s: Vocabularies
    • None
    • Environment:

      Proposed

    • Hide

      Add a new property NonInsertableProperties to term InsertRestrictions that is a collection of property paths, similar to the existing NonInsertableNavigationProperties.

      Note: we do not need this yet for update as this is covered by term Core.Immutable on the property level.

      Show
      Add a new property NonInsertableProperties to term InsertRestrictions that is a collection of property paths, similar to the existing NonInsertableNavigationProperties . Note: we do not need this yet for update as this is covered by term Core.Immutable on the property level.
    • Show
      https://github.com/oasis-tcs/odata-vocabularies/pull/44/files  

      Business documents can contain fields that cannot be filled out when creating the document and can only be updated after successfully creating the business document.

      One example is "physical inventory":

      • A physical inventory document is created as a plan for performing a physical inventory, listing the materials to be inventoried.
      • The stocks are counted for the materials to be inventoried.
      • The count results are entered in the physical inventory document. The document is now "counted".
      • If the count revealed differences between book and reality, the warehouse manager checks the reason for the difference and enters it in the document.
      • The difference can then be posted by the manager.

      To accurately reflect this in the service metadata, the "count" and the “difference reason” properties need to be annotated as "do not provide on insert, only provide on update".

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

              Created:
              Updated:
              Resolved: