Sales CRM
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 start
Sales → Forecast & targets → Submissions & review → View history or Export CSV
Fields and options
- Access needed
- Sales CRM viewing access to the relevant submissions
- Permission and scope
- Sales CRM viewing access to the relevant submissions
Before you begin
Open the correct company workspace and confirm Sales CRM viewing access to the relevant submissions. Review the original record before following these steps. Open the relevant entry under the native Sales menu; the workspace tabs use shorter labels such as Deals, Reports, Relationships and Sales setup.
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.
Check the result
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.
If something does not look right
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.
Fields, rules 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.
Related technical reference: Britixo's detailed product guide (opens in a new tab). The screens available to you depend on your configured modules, company and permissions.
Useful next steps
- Understand the Sales CRM workspace
- Open a forecast submission period
- Submit and revise your revenue forecast
Contact the Proplix team if you need help with your setup. Include the page or record reference and a description of the issue; leave passwords and private access tokens out of the message.