Understand bulk-export period limitations
Pixie CRM guidance. Follow the route for your workspace, check your role and enabled modules, and verify the result before moving on.
Do not rely on the displayed period/custom-date UI in the supplied version without correction.
Where to goAdmin Area → Utilities → Bulk Export → Period
Before you start
- Use an authorised account and confirm the source CRM record or setting is correct.
- Follow the exact route shown above; do not force database values to imitate a completed action.
What this guide helps you do
Do not rely on the displayed period/custom-date UI in the supplied version without correction. These instructions follow the supplied module’s live hooks, controller, model, view and validation flow.
Follow these steps
- Check the period choices.
- For production evidence, test the resulting record set rather than assuming the period was applied.
- Use an approved corrected module release if date filtering is mandatory.
Fields and options
Action scopeDo not rely on the displayed period/custom-date UI in the supplied version without correction.
Module version1.0.0
NavigationAdmin Area → Utilities → Bulk Export → Period
EvidenceVerify the stored record, status, output, email, event or log produced by the code path.
Rules and limits
- The form names custom fields start_date and stop_date, while the controller reads date-from and date-to.
- The controller does not read the period selection.
- Therefore the supplied UI period/custom range is not reliably applied.
Check it worked
- The requested record, output or setting is created or updated through the supported module flow.
- Any related status, count, email, audit/event, PDF/file or queue evidence agrees with the source action.
- An error message is investigated rather than bypassed.
Security, privacy and operational checks
- Apply least privilege and verify the correct customer, lead, sales document or recipient before processing.
- Protect public tokens, recipient data, IP/browser evidence, templates and exported files according to organisational policy.
- Test configuration changes with controlled records before production-wide use.
- Retain or delete evidence only under an authorised retention process.
Important code-backed limitationVerify every exported record range. The displayed period selector is not wired correctly in version 1.0.0.
Related guides
Was this guide useful?Your response is stored only in this browser.