{"revision":"c10276e953456835cdbb1f3a60d58ae1980be353","document":{"id":20773,"path":"integrate-applications/erp-integration-framework/erp-api-getrowcount.md","title":"API – getRowCount\\(\\)","bundle":null,"doc_type":null,"release":"australia","body":"\n# API – getRowCount\\(\\)\n\nReturns the total number of rows that a Zero Copy Connector for ERP model operation would return, without retrieving the records themselves.\n\nUse getRowCount\\(\\) as a terminal method in place of execute\\(\\) when you need only a count. You configure the query the same way you would for a normal run, then call getRowCount\\(\\) instead.\n\n## How the count is determined\n\nThe count is protocol-specific:\n\n|Protocol|Source of the count|\n|--------|-------------------|\n|Read table|Total record count reported in the connector response metadata.|\n|OData|The OData count endpoint. Supported for both direct execution and execution through a MID Server.|\n|BAPI|Uses the default fallback. SAP provides no native count capability for BAPI calls.|\n|REST|Uses the default fallback.|\n|Default fallback|Counts the items actually returned in the response, which is equivalent to counting the rows that would land in a remote table.|\n\n**Note:** Where the default fallback applies, the response is still retrieved to be counted. Only the read table and OData paths avoid fetching the records.\n\n## Related methods\n\nThe same count behavior is available at two lower levels. The query engine exposes a row count method alongside its execute method. The API handler provides count methods that accept either an encoded query or a JSON filter, parallel to its existing query and filter methods.\n\n## Limitations\n\nFor REST services, designating a specific response field as the count is not supported.\n\n"}}