Developer Catches SAP OData API Silently Capping Data at 1,000 Rows
A developer querying SAP Internal Orders via an OData API received exactly 1,000 rows — a suspiciously round number that prompted further investigation. Standard OData pagination parameters such as $skip and $top were ignored by SAP's gateway, which continued returning the same first 1,000 records regardless. Even a $count request over the full date range returned 1,000, indicating the cap affected metadata as well as data. Splitting the query into two date-range halves revealed a true total of 1,589 rows, meaning 589 records had been silently dropped with no error or warning. The incident highlights the need for independent verification strategies — such as windowed queries and cross-checked partial counts — rather than relying solely on an API's built-in pagination mechanisms.
This is an AI-generated summary. ShortSingh links to the original source for the complete article.

Discussion (0)
Log in to join the discussion and vote.
Log in