Loading
Feature Disruption - Service Cloud VoiceRead More
Feature degradation | Gmail Email delivery failureRead More
Extend Salesforce with Clicks, Not Code
Table of Contents
Filter by (0)Add
Select Filters

          No results
          No results
          Here are some search tips

          Check the spelling of your keywords.
          Use more general search terms.
          Select fewer filters to broaden your search.

            Search all of Salesforce Help
            Search all of Salesforce Help
            Salesforce Connect Support for Reports

            You are here:

            1. Salesforce Help
            2. Docs
            3. Extend Salesforce with Clicks, Not Code

            Salesforce Connect Support for Reports

            Depending on network latency and the availability of the external system, reports that include an external object can take a long time to run.

            Required Editions

            Available in: both Salesforce Classic and Lightning Experience (not for high-data-volume external objects)

            Available in: Developer Edition

            Available for an extra cost in: Enterprise, Performance, and Unlimited Editions

            When you run a report that includes external objects, your org performs a request callout for each external object in the report. And if it’s a joined report, your org performs separate request callouts for each block. If the URL of a report callout approaches or exceeds 2 KB, the request is split into multiple HTTP calls, with each URL being less than 2 KB.

            A report that includes an external object fetches up to 20,000 records for the primary object. If the report is customized to include child objects, the total number of rows can be greater or less than 10,000, depending on how many child records are fetched. To obtain more relevant external object rows, try customizing the report.

            For custom reports that include external objects as the primary object:

            • If the deployment status of the external object changes, the custom report type’s Deployment Status changes similarly from Deployed to In Development. See Deployment Status for Custom Objects and External Objects.
            • If the external object is deleted, the custom report type and reports created from it are deleted.

            For large external data sources, report callouts typically access only a subset of the external data. If the report includes summary fields and formulas, those aggregate values likely reflect only a subset of your data. To improve the accuracy of the aggregate values and obtain more relevant data, try customizing the report.

            As is true for all callouts for external objects, report callouts are limited by the Salesforce Connect adapters in use.

            • Cross-org adapter: No callout limits. However, each callout counts toward the API usage limits of the provider org. See API Request Limits and Allocations.
            • OData 2.0 and OData 4.0 adapter
              • 20,000 OData callouts per hour for Enterprise, Performance, and Unlimited editions. If you require higher limits, create a support case.
              • 1,000 OData callouts per hour for Developer Edition.
            • OData 4.01 adapter: No callout limits.
            • Custom adapter: See Callout Limits and Limitations and Execution Governors and Limits in the Apex Developer Guide.

            Features Not Supported

            • Converted currency fields
            • Cross filters
            • Buckets and bucket fields
            • Historical trend reporting
            • Row-level formulas

            See Also

             
            Loading
            Salesforce Help | Article