Our Most Suggested Products
Advanced Power BI Connector
Odoo Power BI Connector connects Odoo with Microsoft Power BI and Microsoft Fabric for advanced reporting and analytics. It allows users to sync Power BI workspaces, create datasets from Odoo models, generate table columns, export records, and manage reports and dashboards directly from Odoo. The module supports secure Microsoft Entra authentication using Tenant ID, Client ID, and Client Secret. Users can export Odoo data such as sales orders, customers, products, invoices, purchases, inventory, and CRM records to Power BI for creating visual reports and dashboards. It also supports Microsoft Fabric Eventhouse and KQL Database integration for real-time analytics, high-volume data, logs, and event-based reporting. A built-in dashboard provides quick access to workspaces, datasets, tables, reports, Eventhouses, and KQL databases. This connector helps businesses automate reporting, centralize Odoo data analytics, and make better decisions using Power BI and Microsoft Fabric.
Features
Screenshots
Support
Service
Features
Power BI Connection
Configure a secure connection between Odoo and Microsoft Power BI using Microsoft Entra credentials such as Tenant ID, Client ID, and Client Secret. The module allows users to test the connection from Odoo before starting workspace synchronization or data export.
Workspace Synchronization
Sync existing Power BI workspaces with Odoo and manage workspace details from one place. This helps users select the correct workspace for publishing datasets, reports, dashboards, Eventhouses, and KQL databases.
Dataset Management
Create and manage Power BI push datasets directly from Odoo. Users can define dataset name, workspace, export mode, batch size, and related Odoo tables before publishing the dataset to Power BI.
Odoo Data Export
Export Odoo records to Power BI using selected models, fields, domains, and limits. This allows users to send business data such as sales orders, invoices, customers, products, purchases, CRM leads, and inventory records to Power BI for reporting.
Automatic Column Generation
Generate export columns automatically from selected Odoo models. The module detects Odoo fields and maps them to Power BI or KQL-compatible field types, reducing manual configuration and setup time.
Scheduled Export
Automate data export from Odoo to Power BI at defined intervals. Users can configure scheduled exports so Power BI datasets stay updated without manually clicking the export button every time.
Reports and Dashboards Sync
Sync Power BI reports and dashboards into Odoo after they are created in Power BI. Users can view report and dashboard metadata in Odoo and open Power BI reports directly from the Odoo interface.
Microsoft Fabric Integration
Enable Microsoft Fabric support for advanced analytics and real-time intelligence. The module supports Fabric API configuration and allows users to work with Eventhouses and KQL databases from Odoo.
Eventhouse and KQL Database Management
Create, publish, refresh, and manage Microsoft Fabric Eventhouses and KQL databases from Odoo. This feature is useful for real-time analytics, log data, high-volume records, and event-based reporting scenarios.
Connector Dashboard
Use the built-in dashboard to get a quick overview of Workspaces, Eventhouses, KQL Databases, Datasets, Tables, and Reports. Each tile is clickable, allowing users to quickly access related records and monitor connector activity.
Screenshot
1). Assign Power BI Connector Access Rights
The user must be given the correct access rights before using the connector. Select Power BI Connector: Manager so the user can configure connections, sync workspaces, create datasets, manage tables, and export data to Power BI.
2). Open Power BI Connector App
After access rights are assigned, the Power BI Connector app becomes available from the Odoo app menu. Users can open the module from here to access the dashboard, workspace sync, data sync, reports, and configuration menus.
3). Power BI Connector Dashboard
The dashboard gives a quick overview of connector records. Users can view total counts for Workspaces, Eventhouses, KQL Databases, Datasets, Tables, and Reports. Each tile is clickable and helps users quickly open related records.
4). Open Connections Menu
The Connections menu is available under Configuration. This section is used to create and manage Microsoft Power BI connection records.
5). Test Power BI Connection
The connection form stores Microsoft Power BI credentials such as Tenant ID, Client ID, Client Secret, API base URL, and token scopes. Click Test Connection to verify that Odoo can successfully connect with Microsoft Power BI. Once verified, the status changes to Connected.
6). Sync Power BI Workspaces
After the connection is successful, click Sync Workspaces to import accessible Power BI workspaces into Odoo. A success message appears in the chatter when the workspace sync is completed.
7). Dataset List
The Datasets menu lists all Power BI datasets created or synced in Odoo. Users can check dataset name, workspace, dataset ID, scheduled export status, last export date, state, and active status from this list.
8). Create Dataset with Odoo Table
A dataset is created to export Odoo data to Power BI. Users can select the Power BI connection, workspace, dataset type, export mode, and batch size. In the Tables tab, users can add Odoo models such as Purchase Orders, Sales Orders, Customers, or Invoices.
9). Table List
The Tables menu displays all configured export tables. Each table is linked to a dataset or KQL database and an Odoo model. Users can review table status, export limit, last row count, and last export details.
10). Generate Columns for Table
After creating a table, click Generate Columns to automatically create export columns from the selected Odoo model. This saves time and helps users prepare the table structure without manually adding each field.
11). Generated Table Columns
The generated columns appear under the Columns tab. Users can review selected Odoo fields, column names, field types, Power BI types, and KQL types. Unwanted fields can be removed before publishing or exporting data.
12). Publish Dataset
Once the dataset and table columns are ready, click Publish Dataset. This creates the dataset structure in Power BI and prepares it to receive exported Odoo data.
13). Dataset Published Successfully
After publishing, the dataset status changes to Published, and the Power BI Dataset ID is filled automatically. This confirms that the dataset has been created successfully in Power BI and is ready for data export.
14). Export Dataset Data to Power BI
After the dataset is published, click Export Now to send the configured Odoo records to Power BI. This action exports the data from the selected Odoo table, such as Purchase Orders, into the Power BI dataset.
15). Dataset Export Completed Successfully
Once the export is completed, Odoo shows a confirmation message in the chatter with the number of exported rows. This helps users confirm that the data was successfully sent to Power BI.
16). View Exported Data in Power BI Report
After exporting data, users can open Power BI and create reports using the exported dataset fields. The available fields appear in the Power BI data panel, and users can build charts, tables, and dashboards from Odoo data.
17). Configure Scheduled Export
The Scheduled Export tab allows users to automate data export from Odoo to Power BI. Users can enable scheduled export, set the interval, and view the next export time so Power BI data stays updated automatically.
18). Enable Microsoft Fabric Integration
To use Microsoft Fabric features, enable Microsoft Fabric in the Power BI connection. After enabling it, click Sync Workspaces so Odoo can fetch Fabric-enabled workspaces from Power BI.
19). View Synced Fabric Workspace
The workspace list shows synced Power BI and Fabric workspaces. Users can select the Fabric workspace where Eventhouses, KQL Databases, and advanced analytics items will be created.
20). Open Eventhouses Menu
The Eventhouses menu is available under the Workspace section. Users can create and manage Microsoft Fabric Eventhouses from this menu.
21). Publish Eventhouse
An Eventhouse is created in Odoo and linked with a Fabric workspace. Click Publish Eventhouse to create the Eventhouse in Microsoft Fabric.
22). Eventhouse Published Successfully
After publishing, the Eventhouse status changes to Published. Odoo automatically stores the Fabric Eventhouse ID, Query Service URI, and Ingestion Service URI, confirming that the Eventhouse is ready to use.
23). Open KQL Databases Menu
The KQL Databases menu lists all KQL databases configured in Odoo. Users can create a KQL database and link it with the selected Eventhouse.
24). Publish KQL Database
After creating a KQL database record, click Publish KQL Database to create or link the database in Microsoft Fabric. This database will store the exported Odoo table data for KQL-based analysis.
25). KQL Database Published Successfully
Once published, the KQL Database status changes to Published. Odoo fills the Fabric KQL Database ID, Query Service URI, and Ingestion Service URI, showing that the database is ready for KQL tables and data export.
26). Generate Columns for KQL Table
For KQL export, create a table and select the KQL Database, Odoo model, domain, order, and limit. Click Generate Columns to automatically prepare columns from the selected Odoo model.
27). Review Generated KQL Table Columns
Generated columns appear under the Columns tab. Users can review the Odoo fields, column names, Power BI types, and KQL types before publishing the KQL table or exporting data to Microsoft Fabric.
28). Publish KQL Table Schema
After the columns are generated for the KQL table, click Publish KQL Table. This creates the table structure in Microsoft Fabric KQL Database, so Fabric can store the exported Odoo records in the correct format.
29). KQL Table Published Successfully
Once the KQL table schema is published, the table status changes to Published. A success message appears in the chatter, confirming that the table structure has been created in Microsoft Fabric.
30). Export Data to KQL
After the KQL table is published, click Export to KQL to send Odoo data into Microsoft Fabric. This exports records from the selected Odoo model, such as Sales Orders, into the KQL table.
31). Review Export Logs
The Export Logs menu shows the result of each export operation. Users can check the export name, related workspace, dataset, table, status, and exported row count. This helps confirm whether the data export was successful.
32). View Exported Table in Microsoft Fabric
After exporting data, users can open Microsoft Fabric and view the KQL Database. The exported table appears under the Tables section, and the activity tracker shows ingestion and query activity for the database.
33). Run KQL Query in Microsoft Fabric
Users can open the KQL Queryset and run queries on the exported Odoo data. In this example, the query calculates the total sales amount from the Sale Order KQL table, allowing users to analyze Odoo data directly inside Microsoft Fabric.
User Guide
Teams
team@inkerp.com
Suggested Products
| Availability |
Odoo Online
Odoo.sh
On Premise
|
| Odoo Apps Dependencies |
Discuss (mail)
|
| Lines of code | 4596 |
| Technical Name |
eg_powerbi_connect |
| License | OPL-1 |
| Website | http://www.inkerp.com |
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