Read forecast history, export results and resolve errors
Trace every submitted version and review, export the visible period and recover safely from stale or failed requests.
Where to goSales CRM → Forecast & targets → Submissions & review → View history or Export CSV
Before you start
Use your own authorised staff account in the intended Pixie CRM workspace. The Sales CRM module must be available and your role must include the permissions stated above. Existing leads, customers, communications and customer portal pages retain their normal access rules.
Follow these steps
- Open View history beside an owner to see their versions from newest to oldest.
- Compare original estimates, reasoning, review decisions, accepted amounts, review reasons and recorded pipeline evidence.
- Look for Currently effective accepted version to distinguish the approved amount still used in totals.
- Close history, refresh the period and select Export CSV to download the currently loaded visible rows.
- Compare the CSV period metadata and refresh time with the screen before using it in another report.
Behavior and limits
- History retains up to the supported 100 versions per person per period. It is not overwritten when later versions are submitted.
- The export includes latest submissions and any earlier version still effective, with explicit Latest submission and Currently effective flags. It does not export every historical version or the underlying opportunity list.
- The CSV includes period dates, currency, pipeline ID, fixed territory IDs, accepted and pending totals, submitted/reviewed timestamps and reasoning. All-pipeline scope is represented by pipeline ID 0; no territory IDs means All territories.
- The export reflects the loaded screen and its permission scope. It is not scheduled email delivery or an automatic accounting integration.
- Spreadsheet formula-like text is escaped as literal text. A protective apostrophe can be visible in a text editor.
- Creation and submission references protect identical retries. Review and state changes use revision checks; refresh after an uncertain response before repeating a decision.
Check it worked
- Check the exported currency, period and effective/latest flags before aggregating rows.
- Confirm a previously accepted version remains effective when its replacement is pending or rejected.
Troubleshooting
- A stale-version error means another action changed the period or submission. Refresh, review the current facts and retry only if still appropriate.
- A session or request-token error requires your normal sign-in and a page refresh. Do not share passwords or session cookies with support.
- If CSV columns are not separated, import the file as UTF-8 with comma delimiter and double-quote text qualifier.
- For support, provide the period ID, submission/version if relevant, intended action and exact error text. Avoid unnecessary customer information.