Pagination, properly

What the API RETURNS, what your table EXPECTS, and THE APPLICATION THAT WORKED ON TWENTY ROWS AND STOPPED AT TWO THOUSAND. This is the defect that is most certain to happen and least likely to be caught before production, because the difference between right and wrong is invisible on test data. A FUSION LIST ENDPOINT RETURNS A PAGE, NOT A LIST. A default number of rows, an offset, and a flag saying whether there are more. Your table is bound to whatever came back, so on twenty-five rows with a default of twenty-five, the page shows everything and is perfect. THE FAILURE IS THAT IT STAYS PERFECT-LOOKING WHEN IT IS WRONG. At two thousand rows the page shows twenty-five, with no message, no scrollbar hint, and no indication that anything is missing. Lesson 12's second failure, and it is reported as "the report is missing records" rather than as a…

In this module: Module 6 · Connecting to Fusion

1. 1What a service connection is
2. 2Creating one against a Fusion REST APIFree preview
3. 3Authentication, and whose identity is used
4. 4Why a shared service account is usually wrong
5. 5Query parameters, filtering and fields
6. 6Pagination, properly
7. 7Writing back to Fusion
8. 8When the shape changes underneath you
9. 9Calling an OIC integration instead
10. 10Handling a service that is down
11. 11CORS and the errors it produces
12. 12What breaks: four connection failures
13. 13Lab briefing · Connect, over-fetch, then fix it