Hi Shobhit
I'm afraid that the entity-based APIs are very much single-entity oriented. Dealing with multiple entities in a single API operation can be done, but would require crafting a special entity (e.g. a task entity). And you would have to deal with things like partial failure.
Hope it helps
------------------------------
Jonathan Goldberg
Amdocs Management Limited
Any opinions and statements made by me on this forum are purely personal, and do not necessarily reflect the position of the TM Forum or my employer.
------------------------------
Original Message:
Sent: Apr 01, 2024 08:22
From: Shobhit Srivastava
Subject: TMF639 for Mutiple Resources in a single payload
Hello All,
I am working on a use case where we have to share the Network Device Data from a server in TMF639 format. The API product exposes is that it gives output of multiple devices in a single JSON. I wanted to understand that if in TMF639 can we send multiple resources in the same payload. Something like below: -
{
"eventType": "ResourceCreateNotification",
"eventId": "UNIQUE ID",
"eventTime": "2022-08-04T07:43:34Z",
"event": {
"resource1": {}
"resource2": {}
"resource3": {}
}
}
Will this be still TMF639 complaint payload?
Also, is there any link on how to handle multiple resources in the one payload.
#CustomerExperience
#DigitalEcosystems
#OpenDigitalArchitecture
#General
------------------------------
Regards,
Shobhit
------------------------------