README.rst

Scheduled Asynchronous Export

Schedule automated exports sent by email at regular intervals (hours, days, weeks, months) to selected users.

Export Groups allow bundling multiple exports into a single email with multiple attachments - useful for consolidated reporting.

Table of contents

• Configuration
  • Creating an Export List
  • Configuring a Scheduled Export
• Usage
  • Export Groups
• Bug Tracker
• Credits
  • Authors
  • Contributors
  • Maintainers

Configuration

Creating an Export List

1. Open any model's list view (e.g., Partners, Sales Orders)
2. Select at least one record
3. Click Action → Export
4. Select fields to export
5. Save the field list with a meaningful name

Configuring a Scheduled Export

Navigate to Settings → Technical → Automation → Scheduled Exports and create a new record with:

• Model and export list (created above)
• Export domain (filter records to export)
• Export format (CSV or Excel)
• Recipients (users who will receive the export)
• Schedule (frequency and next execution date)
• Language (for field labels in the export)

A cron job runs hourly to execute scheduled exports and groups.

Usage

When a scheduled export is configured, its execution is automatic based on the schedule.

Users receive an email with a download link for the exported file. Attachments remain in the database for 7 days by default (configurable via the attachment.ttl system parameter).

Export Groups

Group multiple exports into a single email:

1. Navigate to Settings > Technical > Automation > Grouped Scheduled Exports
2. Create a group specifying:
   • Recipients (users with email addresses)
   • Email template
   • Exports to include (select from standalone exports or create new ones)
   • Schedule (interval, next execution, language)
3. Use Send Test Email Now to verify configuration

Important: When an export is added to a group, it automatically inherits the group's scheduling parameters (recipients, interval, language, etc.). Individual exports within a group cannot be executed separately - only the group's cron job triggers their execution as a batch.

Bug Tracker

Bugs are tracked on GitHub Issues. In case of trouble, please check there if your issue has already been reported. If you spotted it first, help us to smash it by providing a detailed and welcomed feedback.

Do not contact contributors directly about support or help with technical issues.

Credits

Authors

• Camptocamp
• ACSONE SA/NV

Contributors

• Guewen Baconnier (Camptocamp)
• Komit:
  • Cuong Nguyen Mtm <cuong.nmtm@komit-consulting.com>
• Stéphane Mangin (ACSONE SA/NV)

Maintainers

This module is maintained by the OCA.

OCA, or the Odoo Community Association, is a nonprofit organization whose mission is to support the collaborative development of Odoo features and promote its widespread use.

Current maintainers:

This module is part of the OCA/queue project on GitHub.

You are welcome to contribute. To learn how please visit https://odoo-community.org/page/Contribute.