Change the CSV export batch size through the filter
Pixie CRM guidance. Follow the route for your workspace, check your role and enabled modules, and verify the result before moving on.
Follow this guide to use the csv_export_batch_size filter in a controlled extension to change the default batch of 100.
Where to goDeveloper extension → csv_export_batch_size filter
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
Use the csv_export_batch_size filter in a controlled extension to change the default batch of 100. 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 Developer extension → csv_export_batch_size filter.
- Verify that your account meets the access rule: Developer / 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
Default100 rows per batch
Filtercsv_export_batch_size
Category/help-centre/category/csv-export-manager/
Topic/help-centre/topic/csv-export-manager-format-security/
Rules and limits
- Test memory, execution time and database load before increasing the batch.
Check it worked
- The change the csv export batch size through the filter 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.