Lab briefing · Read, write and break an integration

Create a record by REST, update it, then reproduce THREE failures deliberately and write the handling each one needs. Start with the GET, then the POST, then a PATCH — and on the PATCH, touch a child collection and count the children before and after. That is Lesson 6, and doing it once with your own eyes is worth more than the paragraph. The three failures, and each has a specific handling to write. ONE: authorisation. Remove a role from the service account, or call an object it cannot reach, and see whether you get a refusal or an empty result. The handling is an alert, because an empty result that should have had rows is indistinguishable from a quiet day. TWO: a duplicate. Run your create twice. Write the reference-and-check handling from Lesson 9, then run it twice again and confirm the second is a no-op. THREE: a timeout.…

In this module: Module 10 · REST and SOAP: calling Fusion, and being called

1. 1What Fusion exposes, and what it does not
2. 2REST vs SOAP: choosing without arguingFree preview
3. 3Authentication and the service account
4. 4Reading the REST API catalogue
5. 5Your first call, and its error
6. 6Payloads, child resources and partial updates
7. 7Bulk operations and rate limits
8. 8Fusion calling out: business events
9. 9Idempotency and retries
10. 10Versioning and surviving a quarterly update
11. 11What breaks: five integration failures
12. 12Lab briefing · Read, write and break an integration