Advanced BigQuery Connector - Filtering, Batching & Schedule Export
by Niyu Labs https://niyulabs.com$ 449.00
| Availability |
Odoo Online
Odoo.sh
On Premise
|
| Lines of code | 1764 |
| Technical Name |
odoo-bigquery |
| License | OPL-1 |
| Website | https://niyulabs.com |
| Versions | 14.0 15.0 16.0 17.0 18.0 19.0 |
Stop reporting on live Odoo. Move serious analytics to BigQuery.
Export selected Odoo data to Google BigQuery with three practical controls: filter exactly what should go out, keep tables updated with incremental sync, and run near real-time exports as fast as every 1 minute. Keep Odoo fast while BI, AI and analytics teams work on warehouse data.
| ✓ Select exact Odoo fields | ✓ Filtering before export | ✓ Incremental sync | ✓ 1-minute realtime export |
Native ecosystem support
|
Power BI
Build management dashboards from BigQuery instead of slowing down live Odoo. |
Tableau
Analyze sales, inventory, accounting and custom module data in Tableau. |
Looker Studio
Create shareable reports for teams, managers and clients using BigQuery data. |
BigQuery
Store Odoo data in a warehouse built for SQL, BI, AI and large analytics workloads. |
Odoo is for operations. BigQuery is for analytics.
Heavy dashboards, SQL queries, forecasting and AI analysis should not fight with the live ERP database.
⚡ Keep Odoo fastMove analytical workloads away from the transactional database so daily Odoo screens remain responsive. |
📊 Give BI clean dataUse BigQuery as the source for Power BI, Looker Studio, Tableau, SQL users and data teams. |
🔄 Update without starting overIncremental sync, cursors and schedules keep warehouse tables fresh without repeated manual exports. |
Not just another BigQuery connector. Built for controlled, fresh Odoo data.
The key value is simple: choose the exact columns, send only the right records, update only what changed, and keep BigQuery close to live without manual exports.
|
01 • Incremental sync
Update changed rows without rebuilding the table.After the first export, the connector can continue from the last sync cursor and push new or updated Odoo records to BigQuery. |
02 • Realtime export
Run exports as often as every 1 minute.For reports that need fresh data, set a 1-minute auto export interval and let the Odoo cron keep BigQuery updated. |
03 • Filtering
Export only the records the report actually needs.Use Odoo domain filters per export definition, so BigQuery receives clean business slices instead of every record. |
04 • Column selection
Export only the fields your report needs.Choose exact Odoo fields per export definition instead of sending every column to BigQuery. Keep tables smaller, cleaner and easier to use. |
This is where the connector stops being a simple exporter and delivers realtime incremental sync for BigQuery.
Basic connectors usually send the whole table again and again. Niyu BigQuery Connector is built like a real data pipeline: after the first export, it can track what changed, push only new or updated Odoo records, and keep BigQuery fresh as often as every 1 minute.
No repeated full-table exportsAfter the first load, the connector can continue from the last sync point and send only records that are new or changed. This saves time, reduces unnecessary load, and makes frequent reporting realistic. |
Dashboards stay close to liveRun scheduled exports as often as every 1 minute. Sales, inventory, accounting, and operations dashboards can stay close to current Odoo activity without manual CSV work. |
Real update logic in BigQuerySync cursors, batching, and BigQuery MERGE logic help update existing rows and insert new rows properly. BigQuery receives updated business data instead of duplicate table dumps. |
Do not dump your whole Odoo database into BigQuery. Domain filtering lets you export the exact business slice.
Most connectors treat export as a blind data dump. Niyu BigQuery Connector lets you apply Odoo domain filters before the data leaves Odoo, so BigQuery receives only the records that actually belong in the report.
Export exact business slicesCreate focused exports for posted invoices, confirmed sales, active products, selected companies, specific warehouses, or any custom Odoo condition your reporting team needs. |
Cleaner tables from the startKeep cancelled, archived, draft, test, or irrelevant records out of BigQuery when the dashboard does not need them. Less noise means faster analysis and fewer report mistakes. |
Reporting logic stays visibleThe export definition itself shows the business rule used to build the BigQuery table. Teams can understand why a dataset contains certain records instead of guessing later. |
One controlled pipeline from Odoo to every analytics tool.
Pick the data, export safely, store it in BigQuery, then connect dashboards and AI tools.
01 Select dataChoose Odoo model/table, columns and optional domain filter. |
02 Export safelyRun manually, use incremental sync or schedule near real-time export every 1 minute. |
03 Store in BigQueryUse schema mapping, staging tables and MERGE logic. |
04 Build reportsConnect BI, SQL, AI and data science workflows. |
Connect Odoo to your Google Cloud project.
Add Project ID, Dataset ID and the service account JSON. The module then knows exactly where BigQuery exports should go.
Google Cloud projectPoint the connector to the correct project and dataset before exports begin. |
Service account JSONAuthenticate Odoo with BigQuery using a service account key. |
Admin-friendly setupNo separate script is needed. The connector is managed from Odoo UI. |
Create one export per business question.
Each query can control the source table, selected fields, domain filters, incremental sync behavior, 1-minute export interval and runtime state.
Column controlExport only the fields the report needs, not every column from Odoo. |
Domain filterRestrict records before they reach BigQuery using Odoo domain logic. |
Incremental syncTrack timestamp and ID cursors so updates can continue without full rebuilds. |
Scheduled exportRun exports automatically at configured intervals, including near real-time 1-minute export cycles. |
Errors, stuck jobs and full refreshes are visible.
The query list does not hide operational problems. Failed queries show a red state, and recovery buttons appear only when they are relevant.
🚩 Red error stateIf a query fails, the error state is clearly visible in red so admins know it needs attention. |
🔓 Reset Stuck StateIf a query is stuck because a previous run was interrupted, the Reset Stuck State button appears. |
✖ Clear ErrorWhen an export error exists, Clear Error appears so the admin can clean the visible state after fixing the cause. |
↻ Hard RefreshHard Refresh can resend the whole table again when a clean rebuild is required. |
Every export leaves a readable trail.
Admins can review what ran, when it ran, how many rows moved, what failed and which user or process triggered it.
Date filtersFilter logs by Today, Last 7 Days, Last 30 Days, Last Month or custom ranges. |
Event filtersReview starts, batches, cron runs, successes, warnings, errors and stuck events. |
Rows exportedTrack moved rows, last batch activity and current run progress. |
Debug detailsUse messages, severity and run tokens to understand exactly what happened. |
Know what changed before an export changed.
Change logs help teams review configuration edits such as selected columns, domain filters, table changes, sync settings and schedule updates.
Time filtersReview recent edits with filters like Last 30 Days, Last Month and custom date ranges. |
Configuration historySee changes to table, fields, domain filters and incremental settings. |
Before and afterUnderstand what changed instead of guessing why an export behaves differently. |
User visibilityTrack who changed important export configuration when reviewing issues. |
Odoo data lands where analytics teams need it.
After export, selected Odoo records become queryable BigQuery tables for reports, SQL analysis, dashboards and AI workflows.
Built for large Odoo tables, not demo records.
The connector uses batching, cursors, staging tables, MERGE logic, locks, schema handling and recovery state.
📦 Batch processingLarge tables are processed in controlled batches instead of one fragile all-at-once export. |
🔄 Cursor based exportLast sync timestamp and last synced ID help incremental exports continue safely. |
🔒 Lock protectionExport locks and stuck-state detection reduce duplicate run confusion. |
🔗 Staging tablesEach batch can land in temporary BigQuery staging before final table update. |
⇄ BigQuery MERGEExisting rows are updated and new rows are inserted using record keys. |
🛠 Type conversionOdoo values are transformed for BigQuery types such as string, integer, float, boolean, timestamp and date. |
Keep export management in the right hands.
Give administrators and managers control over configuration while keeping normal users away from dangerous setup actions.
Connector user groupAllow controlled access to connector menus and safe review actions. |
Connector manager groupLimit setup, query creation and recovery actions to trusted users. |
Safer workflowSeparate export administration from regular Odoo usage. |
Everything buyers need to know before installing.
A serious connector should be configurable, observable and recoverable from inside Odoo.
Any Odoo tableCreate separate export definitions from Odoo source tables and custom models. |
Column selectionChoose only the fields required by reporting teams. |
Odoo domain filteringExport only records that match the business reporting condition. |
Incremental syncRepeated exports can focus on new and changed rows instead of rebuilding the full table every time. |
Scheduled exportSet automatic export intervals per query, including a 1-minute cycle for near real-time reporting. |
Manual runRun an export immediately when data is needed now. |
Hard RefreshResend the whole table again when a clean rebuild is required. |
Clear ErrorClear visible error state after fixing the root cause. |
Reset Stuck StateRecover a query when an interrupted run left the lock active. |
Query logsAudit run events, row counts, errors, warnings and progress. |
Change logsReview what changed in export configuration and when. |
BI readyFeed BigQuery into Power BI, Looker Studio, Tableau, SQL and AI tools. |
What customers can build after installing it.
The value is not only export. The value is making Odoo data usable outside Odoo.
Sales dashboardsMove orders, order lines, invoices, customers and sales team data to BigQuery. |
Inventory reportingAnalyze product movement, quantities, warehouses and operational history. |
Finance analyticsExport accounting data for revenue, margin, payment and compliance reporting. |
AI analysisUse warehouse data for AI analysis without giving tools direct load on Odoo. |
Custom module reportingExport custom module data when the model and selected fields are available. |
Executive reportingCreate fast reporting layers for founders, managers and department heads. |
Common buyer questions.
Can I filter what gets exported?Yes. Use Odoo domain filters to restrict records before they reach BigQuery. |
Can I choose only required fields?Yes. Select exact columns per query instead of exporting every field by default. |
Does it support incremental sync?Yes. Enable incremental auto export per query, then use the sync cursor so future runs focus on new and changed rows. |
What happens if an export fails?The query shows an error state. Admins can inspect logs, fix the issue and use Clear Error when appropriate. |
What if a query gets stuck?Reset Stuck State appears when a stuck lock state needs recovery after an interrupted export. |
Can I rebuild a table?Yes. Hard Refresh can resend the whole table again when a full rebuild is required. |
Turn Odoo into a serious warehouse source for reporting, BI and AI.
Clean exports. Column selection. Domain filters. Incremental sync. 1-minute realtime export. Batch processing. BigQuery MERGE. Query logs. Change logs. Error states. Recovery controls.
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
equipo de soporte es rápido
Me alegró mucho poder mantener la sincronización entre los datos de Odoo y Power BI en menos de 30 minutos. BigQuery es un buen medio.
There are no comments yet!