Skip to Content

From cells to insights: Mastering Odoo 19 Pivot Tables to Dashboards

Duration: 25:53


PART 1 — Analytical Summary 🚀

Context 💬

Richard from Odoo delivers a hands-on walkthrough titled “From cells to insights: Mastering Odoo 19 Pivot Tables to Dashboards.” The session starts with a single “cell” value and builds all the way to fully interactive Dashboards, illustrating how operational records in Odoo morph into strategic insights. The focus is squarely on Pivot Tables in Odoo 19, how they connect to Odoo Spreadsheet, and how teams can manipulate, compute, visualize, and share data without leaving the Odoo suite. A brief Q&A closes the talk, clarifying version differences and design choices behind pivot behavior.

Core ideas & innovations 🧠

The talk reframes pivots as the most “pivotal” step from transactions to insights. In Odoo, every record carries fields that naturally map to pivot logic: categorical fields (e.g., buyer, date, country) become Dimensions, and numerical fields (e.g., count, totals, averages) become Measures. Richard demonstrates this from the Purchase app: grouping orders by order date (monthly granularity) and by buyer, then layering measures like Untaxed Total or Count.

The next leap is bringing pivots into Odoo Spreadsheet, where two insertion modes define your analysis workflow:

  • The Static Pivot (default) writes one Odoo formula per cell, effectively a snapshot of the pivot at insertion time. It’s ideal for quick, ad‑hoc computations and column math (e.g., a simple month-to-month delta) but won’t auto-extend with new periods or adapt to later regrouping.
  • The Dynamic Pivot renders with a single array-style formula tied to a defined data source (e.g., “Pivot 1”). It auto-updates with new data (e.g., a newly created September purchase order instantly appears as a new column) and adapts to regrouping and filters. With array outputs comes the familiar “spill” consideration—inline formulas block the pivot’s range—so computations must be handled via pivot properties instead of cell-by-cell hacks.

From there, Richard opens the Pivot Properties side panel to manipulate dimensions and measures on the fly: changing date granularity (month → year), adding/removing dimensions, and dragging hierarchy levels. In Odoo 19, pivots gain two notable boosts: users can collapse/expand subgroup levels for readability and deep-dive across relational fields (e.g., grouping purchases by the buyer’s team via a relational drill-down). Measures are not just selected—they can be computed. Computed Measures let you build custom KPIs using Odoo formulas (e.g., average per buyer by dividing total by a distinct buyer count), enabling flexible analytics while staying dynamic.

Visualization sits one click away. Richard builds charts (including the new Radar Chart in Odoo 19) to compare vendor performance across 2023–2025, toggles value expressions (absolute vs. percentage of total), and sets up Global Filters for period, vendor, buyer, and category—ensuring every pivot and chart on the page reacts consistently. Finally, the spreadsheet is added to a Dashboard, where filter suggestions (new in 19) speed up common slicing needs and deliver a shareable, real-time view for teams.

The Q&A confirms version history: the Dynamic Pivot exists since Odoo 17 (different formula syntax), with major side-panel editing and computed-measure capabilities arriving in 18+, and Odoo 19 adding relational drill-down and subgroup expand/collapse. The default “static” insertion remains by design to keep entry-level usage simple, while advanced users can switch to dynamic for long-term reporting.

Impact & takeaways 💼

The session showcases how Odoo 19 streamlines the path from operational data to decisions:

  • It standardizes KPIs inside the platform, avoiding spreadsheet drift and manual exports.
  • Dynamic Pivots + Computed Measures automate long-term reporting, keeping analyses current as data grows, without rework.
  • Relational drill-down (e.g., by buyer team) unlocks cross-model insights that typically require separate BI tools.
  • Global Filters drive consistency and reuse—build a report once, then flex it across timeframes, vendors, or teams.
  • Performance-wise, pivots outperform list insertions at scale; they aggregate efficiently, load faster, and still allow one-click drilldown to contributing records.
  • Usability improves with expand/collapse controls and richer chart types, reinforcing storytelling in dashboards while preserving underlying auditability.

Practical guidance rounds out the talk: prefer pivots over long raw lists for future-proof performance, keep displayed dimensions lean for readability (use filters to narrow scope), and build reports that can be reused across periods rather than rebuilt each month. In short, Odoo 19 turns pivots into a living analytical layer—structured enough for governance, flexible enough for business users, and close enough to operations to stay trusted. ⚙️

PART 2 — Viewpoint: Odoo Perspective

Disclaimer: AI-generated creative perspective inspired by Odoo’s vision.

Our goal has always been to make sophisticated analysis feel simple. Embedding pivots and spreadsheets directly in Odoo means your KPIs live where your transactions live. You don’t export trust—you build it into the flow of work. Dynamic pivots and computed measures are powerful because they respect the single source of truth while giving teams the freedom to iterate quickly.

I’m especially proud of the relational drill-down. Real businesses don’t think in tables; they think in relationships—buyer to team, vendor to category, operations to finance. When you can pivot across those connections without switching tools, you empower more people to understand, act, and improve. That’s the community we’re building: curious users who automate the boring parts and focus on better decisions.

PART 3 — Viewpoint: Competitors (SAP / Microsoft / Others)

Disclaimer: AI-generated fictional commentary. Not an official corporate statement.

Odoo’s embedded spreadsheet and dynamic pivot model is compelling for mid-market teams. Keeping analytics inside the transaction system reduces friction and increases adoption. The UX is clean, and features like computed measures and global filters make day-to-day analysis approachable without a separate BI stack.

At larger scale, the challenge shifts to governance: data lineage, controls, segregation of duties, and regulatory reporting that spans multiple entities and complex consolidations. Tools like SAP Analytics Cloud or Microsoft Power BI excel at semantic modeling, centralized metrics governance, and high-volume performance. The interesting opportunity for customers is hybrid: leverage Odoo’s in-app agility for operational analytics, and integrate with enterprise BI for compliance-heavy, cross-system narratives. The UX differentiation is clear; the long game is how well these layers interoperate.

Disclaimer: This article contains AI-generated summaries and fictionalized commentaries for illustrative purposes. Viewpoints labeled as "Odoo Perspective" or "Competitors" are simulated and do not represent any real statements or positions. All product names and trademarks belong to their respective owners.

Share this post
Archive
Sign in to leave a comment
Getting started with Odoo Barcode