The plainest request names an entity set and nothing else. It retrieves every row and every column of the table. ## Request ```text GET .../odata4/ExactOnlineREST.Financial.GLAccountsBulk@eol ``` ## Answer ```json { "@odata.context": ".../odata4/$metadata#ExactOnlineREST.Financial.GLAccountsBulk@eol", "value": [ { "ID": "ddcd50dc-1956-4307-8ef4-17933562f202", "Division": 920474, "DivisionName": "ACME BV", "Code": "0110" }, { "ID": "d1a70701-8c35-45cb-85a1-21e040ea566f", "Division": 920474, "DivisionName": "ACME BV", "Code": "0120" } ] } ``` The rows arrive in one answer. There is no page to walk to and no `@odata.nextLink`, however large the table is. ## When To Use It This request suits a small table and a first look at an unfamiliar one. It is the wrong request for anything else, because it retrieves from the platform every column of every row, and both count against the [[Invantive Bridge Online/Fair Use Limits|Fair Use Limits]]. The three requests which make a download smaller are [[Select Columns]], [[Filter Rows]] and [[Limit Rows]], and they combine freely. Where only totals are wanted, [[Group and Aggregate Rows]] retrieves no rows at all.