For a Dataverse forecast pull, measure the 50,000-record cap and 5,000-row default page from Microsoft, plus Calendly's booking examples and Google's 1080p recording opt-out.
Forecast pull published caps: the short answer
Dataverse aggregate calculations on a collection are limited to 50,000 records. Microsoft states this query option enables these specific calculations on collections of up to 50,000 records. This figure defines the boundary for aggregate data queries in the platform. Keep the claim tied to this named source, as one publisher's rule does not apply to every firm. Do not treat this specific limit as a universal standard across all sales tools. The scope is strictly limited to the documented query option for aggregate data.
Count the records your forecast aggregate would evaluate and write that count next to the 50,000 record line before you read the weekly total.
Key takeaways for what published caps should i measure on a dataverse forecast pull, a booking window, a recording, and a short replay?
- Plan paging: if you don't specify a number, each request might return up to 5,000 table rows, according to Microsoft.
- Check batch sizes: batch requests can contain up to 1,000 individual requests and can't contain other batch requests, as stated by Microsoft. The same source notes that a URL in the body of a batch message allows up to 64 KB (65,536 characters).
- Check filter length: In or NotIn query functions can use strings up to 850 characters, according to Microsoft.
- Set expectations: Calendly shows a 4-hour notice and a 60-day range as examples of the date-range settings, according to Calendly.
- Ask your administrator: admins can opt out of 1080p recordings for their organizations, according to Google.
What the Dataverse record and page figures measure
The aggregate functions work with a collection of up to 50,000 records, according to Microsoft. This limit applies specifically to the query interface described in the documentation. Dataverse supports only a subset of these aggregate methods, so you must verify which calculations are available before running your forecast pull. The product name in the source title is "Aggregate data using OData: Query Microsoft Dataverse - Power Apps | Microsoft Learn," and the rule stays tied to that specific context.
When you request data without specifying a count, each request might return up to 5,000 table rows, according to Microsoft. This figure describes the potential output size for a single request when no explicit number is set. The source page is titled "Page results using OData from Microsoft Dataverse Web API - Power Apps | Microsoft Learn." If your forecast query spans multiple pages, you must manage the pagination logic carefully. For every subsequent request for more pages, use the same odata.maxpagesize preference value used in the original request.
These two figures define the boundaries for your data extraction. The record cap limits the total volume the aggregate function can process, while the row limit defines the chunk size for each HTTP request. You should check if your pipeline data exceeds the 50,000 record threshold before relying on the aggregate total. If it does, the calculation may not reflect the full dataset. Similarly, if you are pulling raw rows to sum them manually, account for the 5,000 row potential for each request. Ensure your script or tool handles the next link correctly by keeping the page size constant.
What the booking, recording, and replay settings measure
The booking window settings appear as examples in the documentation. Under the Date-range section, the notice dropdown shows “4 hours” as an example for how much notice is required before a meeting, according to Calendly. The same source shows the range dropdown with “60 days” as an example for the booking range. These figures illustrate the available settings rather than stating a fixed requirement for every account.
Recording resolution is a separate setting. Admins can opt out of 1080p recordings for their organizations, as stated in the Google documentation. This option applies only to 1080p recordings.
Replay outline behavior depends on call content. Short calls or calls with limited dialogue may produce fewer outline sections, according to Gong. When reviewing a replay, the outline may vary with the dialogue in the recording.
Check your specific organization’s settings to see which values are currently active. Compare the notice and range dropdowns against the examples provided in the help documentation. Verify the recording resolution setting with your administrator if you need to confirm the current state. Review the outline sections on a recent call to see how the AI handles shorter conversations.
How to compare your own forecast pull
Microsoft states that this query option enables you to perform calculations like sum, count, average, and grouping operations on collections of up to 50,000 records. This limit applies specifically to aggregate calculations on a collection within the named product.
To check your own pull, identify the total number of records your query targets. If your count exceeds 50,000, the aggregate calculation will not process the full collection as described. Keep the claim tied to this named source; do not treat one publisher's rule as every firm's rule. The figure of 50,000 is the maximum supported for these specific operations.
Write the record count you have determined directly next to the 50,000 figure in your notes. This provides a clear visual check before you review the weekly total. The source defines the scope of supported operations as sum, count, average, and grouping. Ensure your query uses one of these supported methods when evaluating the collection size.
Do not assume this limit applies to other systems or different types of queries. The documentation specifies this cap for aggregate data queries on the named platform. If your pipeline data includes more than 50,000 records, you must adjust your approach to fit within this boundary. The limit is a static constraint on the collection size for these calculations.
Review your query parameters to confirm they align with the supported operations. The source mentions specific calculation types, so verify your request matches one of them. This check ensures you are working within the documented capabilities of the tool. The 50,000 record cap is the primary constraint to measure against your data volume.
Use this comparison to validate your forecast pull before the meeting. If your count is under the limit, the aggregate should function as described. If it is over, you need to segment your data or change your query strategy. The documentation provides the specific boundary for these operations. For dates that moved during the pull, see the close date change log.
Illustrative example: a small forecast pull
Suppose your pipeline holds 1,000 open deals. That is well under the 50,000-record aggregate cap, so one aggregate can cover all of them. If you request rows without a page size, a request may return up to 5,000 rows, so all 1,000 deals fit in one response. If you batch 10 requests together, that is far below the 1,000 request batch limit. Write the count of 1,000 next to the 50,000 record line before you read the total. This example is illustrative; your own counts will differ.
Limits of each figure
For the filter string length, the documentation states that you might be able to reduce the number of conditions by using the In or NotIn query functions that can be used with numbers, unique identifiers, and strings up to 850 characters Microsoft. This limit applies specifically to the string argument within those query functions. It does not imply a universal character limit for all filter types or other query parameters.
Regarding paging, the guidance notes that you can continue paging through the data until no @odata.nextLink annotation is included in the results Microsoft. This describes the termination condition for the paging sequence rather than a fixed total number of pages. The absence of the annotation signals the end of the available data for that specific query execution.
The documentation also advises that you should cache the results returned, or the @odata.nextLink URL value, and use it to return to previous pages Microsoft. This is a recommendation for handling navigation within the paged results.
Check any In or NotIn string argument against the 850-character limit before you run the aggregate.
Forecast caps reference table
The table below lists the eight published figures from the vendor documentation. For category context, read Pipeline, Best Case, Commit: Forecast Categories Explained.
| Publisher | Figure | Limit/Value | Context |
|---|---|---|---|
| Microsoft | Aggregate record cap | 50,000 records | Calculations on collections |
| Microsoft | Default page row cap | 5,000 rows | When no number is set |
| Microsoft | Batch request cap | 1,000 requests | Individual requests in one batch |
| Microsoft | Batch URL size cap | 64 KB (65,536 characters) | URL length in message body |
| Microsoft | Filter string length | 850 characters | In or NotIn query functions |
| Calendly | Booking notice example | 4 hours | Notice dropdown example |
| Calendly | Booking range example | 60 days | Range dropdown example |
| Recording resolution opt-out | 1080p | Admin opt-out option |
Next step today: open your forecast query and confirm it uses a calculation such as sum, count, average, or grouping before you run it.
FAQ: forecast pull published caps
What forecast pull published caps do these vendor lines state?
The eight figures are a 50,000 record cap, a 5,000 row page limit, a 1,000 request batch cap, a 64 KB URL size, an 850 character filter length, a 4 hour notice example, a 60 day range example, and a 1080p recording opt-out. Microsoft documents the 50,000 record cap, and Microsoft documents the 5,000 row default. Calendly provides the notice and range examples. Google states the recording resolution option.
Does the 50,000 record cap apply to every CRM I use?
No, this limit applies specifically to Microsoft Dataverse aggregate calculations and functions. Microsoft states that aggregate functions work with a collection of up to 50,000 records. Other platforms may have different limits or no such cap. Check your specific tool documentation for its own rules.
How large can a Dataverse batch URL be?
A batch URL can be up to 64 KB or 65,536 characters. Microsoft explains that you include the request URL in the message body where this size is allowed. This applies to batch operations using the Web API.
Is the 4-hour Calendly notice required for my team?
No, the 4-hour notice is an example of a setting, not a requirement. Calendly shows how to open the notice dropdown and set how much notice is required before a meeting. You can choose different notice periods based on your team's needs.
Who can opt out of 1080p meeting recordings?
Admins can opt out of 1080p recordings for their organizations. Google states this capability for video meeting recordings. The option applies only to 1080p recordings.