--- schema_version: "1" id: ed3fb234797cb69ba7f45614871ba2d2365368dd422d49d31ac6b66aba4be1e3 title: External Cross-Org 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_externalcrossorgcallout.md canonical_url: https://developer.salesforce.com/docs/atlas.en-us.object_reference.meta/object_reference/sforce_api_objects_eventlogfile_externalcrossorgcallout.htm source_site: developer.salesforce.com content_type: documentation content_hash: a5d22beab1bff1f92e21976b952105e82c81e6e4f13e2ed0a9485bf19bf0c2c9 description: External Cross-Org Callout events represent external data callouts via the cross-org adapter for Salesforce Connect. This event type is available in the EventLogFile object in API version 40.0 and later. --- # External Cross-Org Callout Event Type External Cross-Org Callout events represent external data callouts via the cross-org adapter 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)"). ![Note](https://developer.salesforce.com/docs/atlas.en-us.object_reference.meta/object_reference/images/icon_note.png) #### Note For the cross-org adapter for Salesforce Connect, event monitoring currently doesn’t track search callouts. ## Fields | Field | Details | | --- | --- | | ACTION | Type String Description Action performed by the callout. Possible Values - query - upsert - delete | | ENTITY | Type String Description Name of the external object being accessed. Example Order | | EVENT\_TYPE | Type String Description Type of event. Value is always ExternalCrossOrgCallout. | | 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 1 | | 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 452 | | FILTER | Type Text Description Field expressions to filter which rows to return. Corresponds to WHERE in SOQL queries. Example WHERE CustomerId='123456' | | HAVING | Type Text Description Reserved for future use. | | LIMIT | Type Number Description Maximum number of rows to return for a query. Corresponds to LIMIT in SOQL queries. Example 200 | | MESSAGE | Type String Description Error or warning message associated with the failed query callout. Value is always empty for upsert and delete callouts. Example System.UnexpectedException: Query is either selecting too many fields or the filter conditions are too complicated | | OFFSET | Type Number Description Number of rows to skip when paging through a result set. Corresponds to OFFSET in SOQL queries. If a SOQL query doesn’t define an OFFSET, the value is -1. Example 0 (default) | | 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. Examples - ORDER BY ShipName - ORDER BY ShipName DESC | | ORGANIZATION\_ID | Type Id Description 15-character ID of the organization. Example 00D000000000123 | | 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 | | ROWS | Type Number Description Total number of records in the result set. Value is always 0 for upsert and delete callouts. Example 200 | | ROWS\_FETCHED | Type Number Description Reserved for future use. | | SELECT | Type String Description Comma-separated list of fields being queried. Corresponds to SELECT in SOQL queries. Example SELECT Id,Name,CustomerID,OrderDate | | STATUS | Type Boolean Description Whether the query was successful. Value is always empty for upsert and delete callouts. Possible Values - 1—Success - 0—Failed | | SUBQUERIES | Type Number Description The number of subqueries that the query is split into. | | THROUGHPUT | Type Number Description Reserved for future use. | | 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. Example 453 | | USER\_ID | Type Id Description 15-character ID of the user accessing the external system. Example 00530000009M943 | | USING\_MRU | Type Boolean Description Reserved for future use. | #### 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.")