--- schema_version: "1" id: f83098853248fc183b95bc84c0cab948771b050cdb5076cea97c56690191da83 title: External OData Callout Event Type collection: legacydeveloper version: current locale: en-us portal_url: https://docs.salesforce.com/legacydeveloper/current/en-us/object_reference/sforce_api_objects_eventlogfile_externalodatacallout.md canonical_url: https://developer.salesforce.com/docs/atlas.en-us.object_reference.meta/object_reference/sforce_api_objects_eventlogfile_externalodatacallout.htm source_site: developer.salesforce.com content_type: documentation content_hash: 30646c00cfc593d1e089c5b7aacc90a26704c5466ca76b258388793dce275303 description: External OData Callout events represent external data callouts via the OData 2.0 and OData 4.0 adapters for Salesforce Connect. This event type is available in the EventLogFile object in API version 40.0 and later. --- # External OData Callout Event Type External OData Callout events represent external data callouts via the OData 2.0 and OData 4.0 adapters for Salesforce Connect. This event type is available in the EventLogFile object in API version 40.0 and later. For details about event monitoring, see the [Trailhead Event Monitoring module](https://trailhead.salesforce.com/en/modules/event_monitoring/units/event_monitoring_intro "HTML (New Window)") or [REST API Developer Guide](https://developer.salesforce.com/docs/atlas.en-us.264.0.api_rest.meta/api_rest/using_resources_event_log_files.htm "HTML (New Window)"). ## Fields | Field | Details | | --- | --- | | ACTION | Type String Description Action performed by the callout. Possible Values - query - upsert - delete | | BYTES | Type Number Description Size of the result set in bytes. | | ENTITY | Type String Description Name of the external object being accessed. Example Order | | EVENT\_TYPE | Type String Description Type of event. Value is always ExternalODataCallout. | | EXECUTE\_MS | Type Number Description How long it took (in milliseconds) for Salesforce to prepare and execute the query. Available in API version 42.0 and later. Example 21 | | EXPAND | Type String Description Reserved for future use. | | FETCH\_MS | Type Number Description How long it took (in milliseconds) to retrieve the query results from the external system. Available in API version 42.0 and later. Example 127 | | FILTER | Type Text Description Field expressions to filter which rows to return. Corresponds to WHERE in SOQL queries and $filter in OData queries. Example CustomerID eq 12345 | | LIBRARY | Type String Description Reserved for future use. | | LIMIT | Type Number Description Maximum number of rows to return for a query. Corresponds to LIMIT in SOQL queries and $top in OData queries. Example 200 | | MESSAGE | Type String Description Error or warning message associated with the failed call. Example The OData query result was too large, so the external data didn’t load. | | NEXT\_LINK | Type String Description OData next link that the callout used to request a subsequent page of rows. A next link is provided in a previous response from the OData producer when the response includes only part of the result set. Available in API version 42.0 and later. However, this field isn’t supported for the OData 2.0 adapter on orgs created before Spring ’18. Example http://services.example.org/Warehouse.svc/Orders?$count=true&​$select=CustomerID,OrderID,RequiredDate,ShippedDate&$top=301&​$skiptoken=10447 | | OFFSET | Type Number Description Number of rows to skip when paging through a result set. Corresponds to OFFSET in SOQL queries and $skip in OData queries. Example 10 | | ORDERBY | Type String Description Field or column to use for sorting query results, and whether to sort the results in ascending (default) or descending order. Corresponds to ORDER BY in SOQL queries and $orderby in OData queries. Examples - ShipName - ShipName desc | | ORGANIZATION\_ID | Type Id Description 15-character ID of the organization. Example 00D000000000123 | | PARENT\_CALLOUT | Type String Description If the callout requested a subsequent page of rows, this field identifies the initial callout whose request resulted in the multi-page result set. Available in API version 42.0 and later. However, this field isn’t supported for the OData 2.0 adapter on orgs created before Spring ’18. Example 4EoZtuBzzRIXSk-ysRdf1F-1 | | PROVIDER\_TYPE | Type String Description Whether the OData 2.0 or OData 4.0 adapter made the callout. Possible Values - OData—OData 2.0 adapter - OData4—OData 4.0 adapter | | RATE\_LIMIT\_USAGE\_PERCENT | Type Number Description Consumed percentage of the org’s limit of OData callouts per hour. Example 2.5—2.5% of the hourly callout limit has been consumed | | REQUEST\_ID | Type String Description Unique ID of a transaction. A transaction can contain one or more events. All events in a transaction have the same REQUEST\_ID. Example 4A13-HSKv3CKs-0FKfceaV | | REQUESTS | Type Number Description Reserved for future use. | | ROWS | Type Number Description Total number of records in the result set. Available in API version 42.0 and later. Example 830 | | ROWS\_FETCHED | Type Number Description Number of records fetched by the callout. The records fetched by a callout can be a subset of a large result set. Available in API version 42.0 and later. However, this field isn’t supported for the OData 2.0 adapter on orgs created before Spring ’18. Example 200 | | SEARCH | Type String Description Search query string. Corresponds to condition expressions in SOSL. Example contains(CustomerID,'10248') eq true or contains(ShipName,'10248') eq true | | SELECT | Type String Description Comma-separated list of fields being queried. Corresponds to SELECT in SOQL queries and $select in OData queries. Example CustomerID,OrderDate,OrderID,ShipCity,ShipCountry | | STATUS | Type Boolean Description Whether the query was successful. Possible Values - 1—Success - 0—Failed | | THROUGHPUT | Type Number Description Number of records retrieved in one second. Available in API version 42.0 and later. However, this field isn’t supported for the OData 2.0 adapter on orgs created before Spring ’18. Example 3025.67 | | TIMESTAMP | Type String Description The access time of Salesforce services in GMT. For example: 20130715233322.670. | | TIMESTAMP\_DERIVED | Type DateTime Description The access time of Salesforce services in ISO8601-compatible format (YYYY-MM-DDTHH:MM:SS.sssZ). For example: 2015-07-27T11:32:59.555Z. Timezone is GMT. | | TOTAL\_MS | Type Number Description How long it took (in milliseconds) to prepare and execute the query and to retrieve the query results. | | USER\_ID | Type Id Description 15-character ID of the user accessing the external system. Example 00530000009M943 | #### See Also - [EventLogFile Supported Event Types](https://developer.salesforce.com/docs/atlas.en-us.object_reference.meta/object_reference/sforce_api_objects_eventlogfile_supportedeventtypes.htm "The EventType field in the EventLogFile object supports these events. Some common fields, such as CPU_TIME and RUN_TIME, can have null or zero values depending on how the events are generated for a given feature. Sometimes, three quotation marks appear around event data containing special characters in the CSV file. The third quotation mark is necessary for tools and applications to parse the field data at the correct field value boundary.") - [EventLogFile](https://developer.salesforce.com/docs/atlas.en-us.object_reference.meta/object_reference/sforce_api_objects_eventlogfile.htm "Represents event log files generated by Event Monitoring. Use event log file data to analyze usage trends and user behavior in your Salesforce org. This object is available in API version 32.0 and later. The Interval and Sequence fields are available only in API version 37.0 and later.")