Oracle Fusion Technical: Reports, Data, Integrations and Extensions · Module 10 · REST and SOAP: calling Fusion, and being called
Payloads, child resources and partial updates
Lesson 103 of 177 · 2 min
PATCH SEMANTICS ARE WHERE THE DAMAGE IS, and the damage is silent. Nested objects first. Most business objects are a parent with child collections — an invoice with lines, a supplier with sites and contacts. Creating the parent does not create the children, and whether you may post them together or must post them separately differs by resource and is stated in the catalogue. THE UPDATE THAT SILENTLY REPLACED A COLLECTION YOU MEANT TO ADD TO is the failure to memorise. You PATCH a supplier with a sites array containing one new site, intending to add it. Depending on the resource, that array REPLACES the collection — and the supplier now has one site where it had four. The call returns 200. The payload was valid. Three sites are gone. So before any update touching a collection: read the catalogue on whether the operation merges or replaces, and TEST IT…
The full lesson is part of the course
The video, the complete written lesson and the module quiz are included in Oracle Fusion Technical: Reports, Data, Integrations and Extensions, with a certificate on completion and a fourteen-day refund window.
In this module: Module 10 · REST and SOAP: calling Fusion, and being called
- 1What Fusion exposes, and what it does not
- 2REST vs SOAP: choosing without arguingFree preview
- 3Authentication and the service account
- 4Reading the REST API catalogue
- 5Your first call, and its error
- 6Payloads, child resources and partial updates
- 7Bulk operations and rate limits
- 8Fusion calling out: business events
- 9Idempotency and retries
- 10Versioning and surviving a quarterly update
- 11What breaks: five integration failures
- 12Lab briefing · Read, write and break an integration