Bulk Data Export/POWER BI · ONEDRIVE · CSV / XLSX
by Falak Solutions https://www.falak-solutions.com$ 397.54
| Availability |
Odoo Online
Odoo.sh
On Premise
|
| Lines of code | 901 |
| Technical Name |
f_bulk_data_export |
| License | OPL-1 |
| Website | https://www.falak-solutions.com |
| Versions | 16.0 19.0 |
| Availability |
Odoo Online
Odoo.sh
On Premise
|
| Lines of code | 901 |
| Technical Name |
f_bulk_data_export |
| License | OPL-1 |
| Website | https://www.falak-solutions.com |
| Versions | 16.0 19.0 |
Bulk Data Export
Odoo 16 â high-volume CSV/Excel extractsOverview
Export large datasets from any Odoo model using a dynamic domain filter (visual domain builder), selected fields, optional date range, and chunked CSV or Excel output. Save files on the server or upload directly to Microsoft OneDrive via Microsoft Graph. Designed for Power BI, data warehouses, Excel modelling, and repeated analytics refresh workflows (including stable filenames when you need a fixed dataset path).
Who this is for: teams that outgrow list-view export â Odoo bulk export to CSV or Excel, scheduled or incremental runs, large tables (e.g. move lines, stock history), Power BI or spreadsheet-led BI, pushing files to OneDrive via Microsoft Graph and Azure AD, ETL-style nightly extracts, and stable filenames for refresh workflows.
Key features
Bulk extract
Many rows, automatically split into multiple files when limits are reached so exports stay reliable on heavy models.
Dynamic domain
Use Odooâs standard domain widget â no custom SQL â to define who and what is included in each run.
Field selection
Pick columns, order them, and set export labels suited for downstream tools.
CSV and Excel
Choose the format that fits Power BI, spreadsheets, or staging files.
OneDrive upload
Optional direct upload to a user folder in OneDrive using Microsoft Graph API credentials stored in the export profile.
Logs and downloads
Track runs and retrieve outputs from export logs when local download is enabled.
Screenshots
Taken from a demo / internal database: generic export names and standard Odoo models only â no customer contacts, amounts, or credentials are shown. Click an image in Odooâs Apps page to open the gallery.
Export configurations
List view: model, local or OneDrive destination, CSV/XLSX, last run and status.
Configuration form
Model, dates, format, filename mode, chunk size â plus domain preview and Edit domain.
Fields to export
Choose stored fields, labels for CSV/XLSX headers, order, and relational sub-fields.
OneDrive destination
Switch between server folder and OneDrive; Test Connection confirms Graph access.
Export logs
History, chunked files, sizes, and downloads when exports are stored on the server.
Scheduled action
Enable the technical scheduled action to run configured exports on a recurring interval.
Prerequisites
- Odoo 16.0 (Community or Enterprise).
- Python packages on the server: xlsxwriter and requests.
- For local exports: valid server path and disk space.
- For OneDrive: see Microsoft 365 setup below; outbound HTTPS to Microsoft login and Graph hosts.
- Understanding of Odoo record rules and user rights: exports follow the same data access as the running user or cron context.
How to use it: a full step-by-step tutorial (menus, domain, fields, local vs OneDrive, test, run, logs, scheduled action) is in the module file doc/index.rst inside the addon (also indexed as module documentation on the App Store).
Microsoft 365 / OneDrive (Graph)
The integration uses OAuth2 client credentials (application identity) against Microsoft Graph
with scope https://graph.microsoft.com/.default. It uploads to
one designated userâs OneDrive using the email you enter in the export profile.
- In Azure Entra ID, create an app registration, add a client secret, and copy Tenant ID, Client ID, and secret into Odoo.
- Under Microsoft Graph, add Application permission Files.ReadWrite.All (or the subset your administrator approves that still allows creating files under the target userâs drive).
- Grant admin consent for the tenant for those application permissions.
- Use the userâs OneDrive / sign-in email in the OneDrive user email field.
Full detail for administrators is in the module documentation (doc/index.rst inside the addon). Permissions and Microsoft UI labels may change; your Entra admin should validate the registration against your security policy.
License (Odoo Apps)
This paid Apps edition is published under the Odoo Proprietary License (OPL-1). Some earlier or internal builds of similar exporters may have been shared under LGPL-3. LGPL-3 is an open-source licence with source and redistribution rules favourable to the community; OPL-1 is a proprietary licence typical for commercial Odoo Apps (purchase confers use under its terms; redistribution of the product as free source is not the default). Confirm with your legal counsel and any existing customer agreements before you rely on OPL-1 for sales â the two licences are not equivalent.
Compatibility
This module has been developed and tested against Odoo 16.0 on both the Community and Enterprise editions. It is fully compatible with the following deployment options:
| â Odoo.sh Odoo's managed cloud platform | â On-Premise Self-hosted servers and private infrastructure |
| â Community Edition Full functionality without Enterprise dependencies | â Enterprise Edition Seamless integration with all Enterprise features |
Falak Solutions
Professional Odoo development
Bulk Data Export — Docs
Table of Contents
Overview
Export any Odoo model to CSV or Excel (.xlsx) with advanced filtering, scheduling, chunking, and optional OneDrive upload. Built for Power BI, data warehouses, and recurring analytics workflows.
Common use cases: Odoo bulk export, large-dataset extract, dynamic domain filtering, scheduled cron export, incremental export since last run, Power BI refresh, OneDrive upload via Microsoft Graph, and chunked multi-part files for heavy models.
Prerequisites
| Requirement | Details |
|---|---|
| Odoo version | 16.0 (Community or Enterprise) |
| Python packages | xlsxwriter and requests — install on the Odoo server with pip install xlsxwriter requests |
| Local exports | Server folder with write access and sufficient disk space |
| OneDrive exports | Outbound HTTPS to login.microsoftonline.com and graph.microsoft.com |
Quick Start
- Install the module from Apps.
- Open Bulk Data Export → Export Configurations → Create.
- Select a model, define a filter domain, pick fields, choose CSV or Excel.
- Click Run Export Now — download the file from the Logs tab.
Step-by-Step Guide
1 — Create an export configuration
Open Bulk Data Export → Export Configurations and click Create.
- Export Name — a descriptive label (e.g. Daily account move lines).
2 — Choose the data source
- Model — the Odoo model to export (e.g. Journal Item, Sale Order).
- Date field (optional) — a stored date or datetime field. When set, Date From / Date To filters appear and restrict exported rows to that range.
3 — Define the filter domain
In Filter Domain, use the visual domain editor to include/exclude records — same concept as advanced filters in list views. Leave [] for no extra filter.
4 — Select fields to export
In Fields to Export, add one line per column:
- Field — must be a stored field (binary, HTML, one2many, and many2many are excluded).
- Sub-field — for Many2one fields, optionally export a related value (e.g. partner → name).
- Label — custom column header in the output file. Drag the handle to reorder columns.
At least one field is required before running an export.
5 — Configure export options
| Option | Description |
|---|---|
| File format | CSV or Excel (.xlsx) |
| Filename mode | With Timestamp — unique file per run (good for archives). Fixed Name — overwrite each run (ideal for Power BI). |
| Export mode | Full — all matching records every run. Incremental — only records changed since last export. |
| Record limit | 0 = no cap (subject to chunking). |
| Records per file | Split large datasets into multiple chunked files. |
| Company | One configuration per company in multi-company setups. |
6 — Choose the destination
- Local folder:
- Set an absolute path on the Odoo server. The OS user running Odoo must have write access.
- OneDrive:
- Fill in Azure Tenant ID, Client ID, Client Secret, OneDrive user email, and optionally a folder path. See the OneDrive Setup section below.
7 — Test and run
- Click Test Connection — verifies local path writability or OneDrive/Graph access.
- Click Run Export Now and confirm. A notification directs you to the Logs tab.
8 — Download results
Open the Export Logs tab (or the Logs smart button). Each successful run shows a Download link. For OneDrive destinations, the upload path is recorded on the log.
9 — Schedule automatic exports
Go to Settings → Technical → Automation → Scheduled Actions and find Bulk Data Export: Scheduled Run.
- Set the interval (e.g. daily) and enable the action.
- The cron processes every active configuration that has at least one export field and a valid destination.
Tip
Power BI tip: Use Fixed Name + OneDrive (or a shared local path). Schedule the Odoo cron and the Power BI dataset refresh on a matching interval.
OneDrive Setup
This module uses OAuth 2.0 client credentials (application identity) against Microsoft Graph v1.0. No interactive user sign-in is required from Odoo.
API calls used:
- GET /users/{email}/drive — connection test
- PUT /users/{email}/drive/root:/{folder/file}:/content — small file upload
- POST .../createUploadSession — resumable upload for large files
Azure Portal configuration
Register an application in Microsoft Entra ID (Azure AD).
Create a client secret under Certificates & secrets.
Under API permissions → Microsoft Graph, add Application permission Files.ReadWrite.All — then click Grant admin consent for the tenant.
Copy these values into the Odoo export configuration:
Odoo field Azure value Azure Tenant ID Directory (tenant) ID Application (Client) ID Application (client) ID Client Secret Client secret value OneDrive user email User principal name (Microsoft 365 sign-in)
Important
Application permissions with broad file access are powerful. Use a dedicated app registration, rotate secrets regularly, and restrict who can edit export configurations in Odoo. Follow your organisation's cloud security baseline.
Security and Access
- Exports respect standard Odoo record rules and the user context of the run.
- Manual runs use your session user; scheduled actions run as the cron user (typically OdooBot / admin).
- Restrict who can enable cron or adjust the action's user if you need tighter data scope.
License
This module is published under OPL-1 (Odoo Proprietary License v1.0) on the Odoo Apps Store. Earlier or internal builds may have been delivered under LGPL-3.
- LGPL-3 — open-source; source access and redistribution under LGPL conditions.
- OPL-1 — proprietary; purchase grants use under its terms, redistribution is restricted.
Confirm with legal counsel before relying on either licence for commercial distribution.
Support
Purchasers may use the support email shown on the Odoo Apps listing for defect reports related to this module.
Odoo Proprietary License v1.0 This software and associated files (the "Software") may only be used (executed, modified, executed after modifications) if you have purchased a valid license from the authors, typically via Odoo Apps, or if you have received a written agreement from the authors of the Software (see the COPYRIGHT file). You may develop Odoo modules that use the Software as a library (typically by depending on it, importing it and using its resources), but without copying any source code or material from the Software. You may distribute those modules under the license of your choice, provided that this license is compatible with the terms of the Odoo Proprietary License (For example: LGPL, MIT, or proprietary licenses similar to this one). It is forbidden to publish, distribute, sublicense, or sell copies of the Software or modified copies of the Software. The above copyright notice and this permission notice must be included in all copies or substantial portions of the Software. THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.
Please log in to comment on this module