Check source scope, filters, paging, precision, and delivery limits before using the extract. When you retrieve more than 5,000 rows of data, you need to page the results according to Microsoft.
Forecast extract validation: checks before coverage review
Verify the five required checks before reviewing pipeline coverage. First, confirm the source scope includes the correct record types. Second, review report filters to ensure they match your criteria. Third, check paging continuity, as Dataverse requires paging for results exceeding 5,000 rows. Fourth, inspect numeric precision for values with fifteen or more digits. Fifth, review report delivery limits, including configurable record caps for emailed reports.
These checks identify missing rows and altered amounts before they impact your forecast. Use the Pipeline, Best Case, Commit: Forecast Categories Explained guide to align your extract with standard forecast categories. Record the record type, filters, paging behavior, numeric precision risks, and applicable delivery cap in your checklist. This preparation ensures your coverage review relies on accurate, complete data.
Key takeaways for how do i validate a forecast extract before reviewing pipeline coverage?
Check source scope, filters, paging, numeric precision and delivery limits before using the extract.
- Source scope: Identify if the data includes quotes. HubSpot documents quote exports, which should be identified as quote data in the coverage evidence file.
- Report filters: Verify the record set. EspoCRM states a list report displays records meeting specified criteria.
- Paging continuity: Check if results exceed limits. Microsoft notes you need to page results when returning more than 5,000 rows.
- Numeric precision: Inspect long values. Airtable warns that numbers with 15+ digits are automatically rounded up.
- Delivery limits: Note emailed caps. EspoCRM sets the max number of records sent in an email by default to 3000.
Take the source extract for your next coverage review and record its record type, filters, paging behavior, numeric precision risks and applicable delivery cap in the checklist.
Before extraction, identify the records and filters
Start by confirming which record types the source actually contains. According to Manage quotes, you can track quote status by monitoring activity and using reports, and you can export quotes to use in other tools. If your extract includes these items, label them clearly as quote data in your coverage evidence file. Do not assume they represent the full opportunity pipeline; they are a distinct record type with their own tracking and export path.
Next, verify the report criteria that define which records appear. According to Reports - EspoCRM Documentation, a List report displays the list of records that meet the specified criteria. This means your extract only includes rows that match your configured filters. If a deal is missing from the extract, check whether it failed to meet those criteria rather than assuming a data loss.
Review the specific filter expressions used to build the report. The documentation provides an example of a Grid report showing accounts grouped by industry where revenue is more than 1,000. It also details an opportunity amount filter expression defined as SUM / opportunities.amount / Greater Than / 1000. A SUM expression tests a total, so check whether your threshold applies to the whole group or to each individual opportunity before assuming which deals are left out. Confirm that your filter logic aligns with the scope of deals you intend to review for pipeline coverage.
Record the exact filter names and values in your validation notes. This allows you to cross-reference the extract against the source system later. If the filter criteria changed between extraction and review, the returned records or row count may differ. Keep the filter definition static for the duration of the coverage analysis to ensure consistency.
Take the source extract for your next coverage review and record its record type and filters in the checklist.
During retrieval, check paging options and row order
If your extract pulls from Microsoft Dataverse, you need to page the results when returning more than 5,000 rows of data, or 500 rows for elastic tables Microsoft. To control the number of records returned, use OData paging with the Prefer: odata.maxpagesize request header. This header manages the page size for the data retrieval process.
When a response includes another page, it provides a specific URL value to retrieve the next page. You must use that provided URL value to continue the sequence. Do not use the $top parameter with the Prefer: odata.maxpagesize request header, as these options are incompatible. Combining them can disrupt the paging mechanism described in the documentation.
Ordering is a critical factor in how data pages. How a page is ordered makes a big difference when paging data. If the information about how the results are ordered is ambiguous, Dataverse can't consistently or efficiently return paged data. This means your extract might miss rows or duplicate them if the sort order is not clearly defined. Check the sort criteria in your query to ensure the order is explicit and unambiguous.
Review the headers in your request to confirm you are using the correct paging method. If you are pulling large datasets, verify that the page size limit matches your extraction tool's capacity. If the ordering is unclear, the data returned across pages may not be stable. Ensure your query specifies a deterministic sort order so that each page contains a distinct set of records. This prevents gaps in your pipeline coverage evidence.
Use the next-page URL provided in the response to continue retrieval. If it is missing, the retrieval may have stopped early. Confirm that you are not mixing incompatible parameters like $top with the max page size header. These checks help ensure the extract captures the full dataset without relying on assumptions about record stability. For context on how record changes affect data, see Close date change log: why the date moved. Record the paging behavior and ordering rules in your validation notes.
After retrieval, inspect large numbers and delivery limits
Check numeric precision before trusting any total in the extract. According to Airtable, numbers with 15 or more digits are not recommended for storing in records because they are automatically rounded up. If your pipeline data includes long identifiers or precise currency values, verify that the source system does not alter these figures during export. Rounding can change the weighted deal amount, so inspect the raw values against the original system to catch discrepancies early.
Next, review the delivery limits for emailed reports. The Reports documentation states that the maximum number of records sent in an email is set to 3,000 by default. This cap applies to the report output, not the underlying database storage. If your coverage review requires more than 3,000 records, the standard email delivery will truncate the list. You can increase this limit by adding the parameter 'reportSendingListMaxCount' => 5000 to the data/config.php file, as described in the same documentation.
Consider how row ordering affects your validation. When using FetchXml queries, if you do not add order elements, the system adds an order based on the primary key of the table, according to Page results using OData from Microsoft Dataverse Web API - Power Apps | Microsoft Learn. This default ordering helps ensure consistent retrieval if you are paging through results. However, be aware that repeated requests may not return identical data. The same source notes that if your page size is 50 and you go back, you get 50 records, but they might not be the same 50 records. Repeated requests may reflect different source states, so keep the original extract and account for intervening changes when comparing it with a fresh pull.
For a deeper look at how these values affect your forecast, see Weighted deal amount: 5 fields to check HubSpot, Pipedrive. Record the applicable delivery cap and any observed rounding in your checklist before proceeding to the coverage review.
Publisher reference table for extract constraints
The table below lists documented constraints for each publisher to guide your validation checks.
| Publisher | Constraint Type | Documented Limit or Rule |
|---|---|---|
| Microsoft | Paging Threshold | Page results required for more than 5,000 rows (500 for elastic tables) |
| EspoCRM | Report Scope | List report displays records meeting specified criteria |
| EspoCRM | Delivery Cap | Default max records in email is 3000 |
| Airtable | Numeric Precision | Numbers with 15+ digits are automatically rounded up |
| HubSpot | Source Scope | Quotes can be exported for use in other tools. |
Record these specific limits in your checklist. Microsoft documents paging needs for large data sets. EspoCRM defines report scope and email caps. Airtable notes rounding for long numbers. HubSpot describes quote export capabilities.
Blank checklist for the coverage evidence file
Use this form to record validation details for your extract. Fill each row with the specific setting or limit you observed in your source system.
| Check Item | Extract Detail | Notes |
|---|---|---|
| Record Type | __ | __ |
| Filters Applied | __ | __ |
| Paging Behavior | __ | __ |
| Numeric Precision Risk | __ | __ |
| Delivery Cap | __ | __ |
Record the record type, filters, paging behavior, numeric precision risks, and applicable delivery cap in this checklist before the next coverage review.
FAQ: Missing rows and altered forecast amounts
What does forecast extract validation check?
Validation covers source scope, report filters, paging continuity, numeric precision, and delivery limits. These five areas identify where records might drop out or values might shift before the coverage review. Confirm each area against the specific system documentation for your extract source.
Does Dataverse paging apply to my elastic table extract?
Paging is required when returning more than 500 rows for elastic tables, according to Microsoft. If your extract pulls from an elastic table and exceeds that row count, you must page the results. Check your row count against this threshold to determine if paging is necessary.
Can I combine $top with the Dataverse paging header?
Do not use $top with the Prefer: odata.maxpagesize request header, according to Microsoft. These two options are incompatible for paging requests. Use the paging header alone to manage result sets without conflicting parameters.
What is the default EspoCRM emailed report record limit?
The maximum number of records sent in an email is set to 3000 by default, according to EspoCRM. This limit applies to emailed reports specifically. Verify if your report exceeds this count to ensure all records are included in the delivery.
How does Airtable handle numbers with fifteen or more digits?
Numbers with 15 or more digits are automatically rounded up when stored in records, according to Airtable. This rounding behavior affects long numeric values passing through the extract. Inspect any large numbers in your data to account for this precision loss.