Open APIs

 View Only

  • 1.  ProductOrderItemRef schema in TMF622

    TM Forum Member
    Posted 9 days ago

    Hi Team,

    Here is the snippet of ProductOrderItemRef schema from TMF622. Trying to understand the reason for the below:
    1) Why ProductOrderHref and productOrderId are part of this schema?
    2) Why they id field is named as "productOrderItemId" instead of "id" ?

    My general understanding was that Ref would be made of all items Extensible, Addressable and EntityRef schema. 
    Can Ref have a field which is not in its referred type? in this eg: ProductOrderHref, productOrderId and productOrderItemId are not part of ProductOrderItem.



    ------------------------------
    Aneesh Da
    Infosys
    ------------------------------


  • 2.  RE: ProductOrderItemRef schema in TMF622

    TM Forum Member
    Posted 8 days ago
    Edited by Abel Ruiz Huerta 8 days ago
    Hi Aneesh,
     
    I'd say this object is meant to store a reference to an orderItem belonging to an external order - that is, not the order that contains this object itself.

    To answer your two questions:

    1) Because this is the information needed to retrieve the related product order - specifically, the URL for the GET request and the identifier of the target order.

    2) This is the identifier of the orderItem within the referenced order. Since this object is just a reference, it doesn't have its own ID.

    Hope this helps.
    Best regards,



    ------------------------------
    Abel Ruiz Huerta
    alvatross



  • 3.  RE: ProductOrderItemRef schema in TMF622

    TM Forum Member
    Posted 8 days ago

    it looks like a pattern when an entity that has an "id" attribute captures the reference to 1 or more entities , the naming scheme prefixes "id" with the entity name.
    for example, if ProductOrderJeopardyAlert is a database table, it will have "id" for the ProductOrderJeopardyAlert, and productOrderItemId referencing the Order Item.



    ------------------------------
    Barathan Venkateswaran
    Salesforce
    ------------------------------

    Original Message