Export a custom date range
Pixie CRM guidance. Follow the route for your workspace, check your role and enabled modules, and verify the result before moving on.
Select Custom and complete Start Date and Stop Date.
Where to goAdmin Area → Utilities → CSV Export → Period → Custom
Before you start
- Use the exact navigation above and confirm the intended record, tenant, customer, property, document or date range.
- Verify module activation and the stated permission instead of using another staff member’s account.
- For public, email, provider, finance, signature or destructive actions, use a controlled test record before production use.
What this guide helps you do
Select Custom and complete Start Date and Stop Date. These instructions follow the supplied module’s live menus, controller actions, form fields, model validation and downstream effects.
Follow these steps
- Sign in to the staff admin area and open Admin Area → Utilities → CSV Export → Period → Custom.
- Verify that your account meets the access rule: Administrator.
- Go to the required record or configuration and review its current values before making a change.
- Complete the displayed fields or action exactly as described in this guide.
- Save, submit, download or confirm the action using the button presented by the module.
- Reopen the source record and verify the expected status, output, notification, file or linked record.
Fields and options
Requiredstart_date and stop_date
Filename{type}_{start}_-_{stop}.csv
Category/help-centre/category/csv-export-manager/
Topic/help-centre/topic/csv-export-manager-periods/
Rules and limits
- Client-side validation requires both custom dates.
- Check that start is not after stop; the supplied form does not show a separate server-side chronological rule.
Check it worked
- The export a custom date range workflow completes without bypassing the module’s permission and validation checks.
- The saved value, generated file, status, notification or linked CRM record is visible from the same workspace.
- Any validation message remains visible until the source data or setting is corrected.
Security, privacy and operational checks
- Use least-privilege staff access and do not use another person’s account to reach a hidden action.
- Check personal, financial, identity and compliance data before sending, exporting or exposing it through a public link.
- Test configuration, email, public forms, accounting effects and provider connections with controlled records before production-wide use.
Related guides
Was this guide useful?Your response is stored only in this browser.