Advanced List View Manager

Key Features

OWL-based extension of the web client list renderer, so enhancements load inside the standard Odoo view instead of a bolted-on separate screen

Per-user column selection, order and width persisted in a dedicated model keyed to res.users and ir.model, surviving reloads and sessions

Column picker driven by fields_get metadata, exposing only fields the current user is permitted to read (ACL-aware)

Correct handling of stored vs non-stored computed fields: compute/@api.depends fields render read-only and are excluded from sort and export SQL

Inline cell editing that writes through the ORM write() path so constraints, computes, automated actions and audit logging all fire

Bulk multi-record edit of a chosen field across the current selection, respecting ir.rule record rules and ir.model.access permissions

Data-driven conditional row coloring: admin-defined rules (field, operator, value, color) replacing hard-coded decoration-* XML attributes

Saved view presets capturing columns, filters, sort and color scheme, switchable in one click and optionally shared to a user group

One-click Excel export (.xlsx via xlsxwriter) with header styling, honoring visible columns, current sort and active filters

One-click CSV export with configurable delimiter and UTF-8 encoding for downstream tooling and BI ingestion

Optional group-level default presets an admin can push, so a team opens a list already configured the intended way

Export and bulk actions rate-safe on large recordsets via batched search_read to avoid worker timeouts

Compatible with existing custom views and inheritance chains without overriding your base list definitions destructively

Configuration UI under Settings backed by standard menuitems and access groups, no server-side file edits needed to add color rules

Built to order, done for you

No DIY setup — a working app, built, installed and supported by ECOSIRE.

You order

Start with a one-time build price. We scope it with you at kickoff.

We build & install

ECOSIRE builds, configures and installs it on your Odoo.

Go live + support

You go live in about 2–4 weeks, with a post-launch support window.

About this Product

Teams that live in Odoo list views hit the same wall every day. The columns they need are buried behind the optional-fields dropdown and reset on every reload, there is no way to save a layout per user, bulk edits mean opening records one at a time, and "just send me this in Excel" becomes a manual copy-paste ritual. Odoo's core list view (the old tree) supports an optional-fields toggle and limited inline editing via editable="top", but it does not persist per-user column selection or order, has no conditional row-color engine beyond a few hard-coded decoration-* attributes tied to fixed field states, and its native export lives behind a separate modal rather than a one-click action. For power users who process hundreds of records a day, that friction compounds into real lost hours.

The Advanced List View Manager is a build-to-order module ECOSIRE develops against your exact models and workflows. At its core is an OWL-based extension of the web client's list renderer plus a small set of Python models (models.Model) that persist each user's view configuration: chosen columns, order, widths and active preset, keyed to res.users and the target ir.model. So a salesperson and an accountant can open the same Sales Order list and each see their own layout. Column add, remove and reorder are driven from the field metadata Odoo already exposes through fields_get, so only fields the user is permitted to read appear as options, and stored fields versus computed non-stored fields are handled correctly (non-stored compute fields render read-only and are excluded from sortable/export SQL).

Inline editing and bulk actions extend the standard editable-list behavior with a server-side write path that respects your ACLs and record rules. Edits and multi-record updates go through the ORM's write() so @api.depends recomputes, @api.constrains validators, automated actions and audit logging all fire exactly as they would in a form. Conditional row coloring is configured as data rather than baked into XML: admins define rules (field, operator, value, color) that we evaluate to emit the right row styling, replacing the rigid native decoration-danger/decoration-info model with something business users can maintain themselves. Saved presets let a user or a whole group snapshot a column layout, filter set and color scheme and switch between them in one click. Export is a first-class toolbar action producing a styled .xlsx (via xlsxwriter, the same library Odoo bundles for QWeb spreadsheet reports) or a clean .csv, honoring the visible columns, current sort and active filters, so what you see is exactly what you get.

Because this is build-to-order, nothing ships until we have your scope. We start with a short scoping call to confirm the target models (Sales, Inventory, Accounting, custom models, or all of them), which user groups get which capabilities, your export formatting needs, and your Odoo edition and version (17.0, 18.0 or 19.0; Community vs Enterprise affects which base list widgets exist). We build against a staging copy of your database, package the module with a clean __manifest__.py and proper ir.model.access.csv plus record rules, run UAT with your power users, then install on production with a rollback plan and hand over the git repository. Typical delivery is two to four weeks from confirmed scope.

What you get

Installable module source code built for your specific Odoo edition and version (17.0, 18.0 or 19.0), with a clean __manifest__.py and pinned dependencies

Installation and configuration on your environment, including menu, access-group and default-preset setup

Technical documentation: model reference, ir.model.access.csv / record-rule map, and where color rules and presets are stored

End-user guide plus a live training session for your power users on columns, presets, bulk edits and export

UAT on a staging copy of your database with a documented test checklist and a rollback plan before production install

Post-go-live support window for bug fixes and adjustments to the delivered scope

Full git repository handover so you own the code and can extend or re-deploy it yourself

Post-upgrade compatibility notes for moving the module across Odoo point releases

Who this is for

Operations & data-entry power users

People who spend most of their day in Sales Order, Inventory or PO lists processing high volumes. They need their own persistent column layout, fast inline edits and bulk updates without opening each record, so throughput goes up and copy-paste errors go down.

Finance & accounting teams

Accountants who reconcile and review long lists of journal items, invoices or payments. They want conditional row coloring to flag overdue or mismatched rows at a glance and a styled Excel export that matches the filtered view for month-end packs and auditors.

Team leads & department managers

Managers who want to standardize how their team works by pushing group-level default presets and color rules, while still letting each user tune their own columns. They need the configuration to be data-driven so they can maintain it without a developer.

Odoo administrators & internal IT

The people responsible for the instance who need the enhancement to respect existing ACLs and record rules, not override base views destructively, survive version upgrades, and arrive with docs and a git repo they can support in-house.

How Advanced List View Manager Compares

Criterion	ECOSIRE	Custom Build	Competitor
Per-user persistent columns	Saved per user and model, survives reloads and sessions	Possible but you build and maintain the storage model	Often global or per-view only, not per user
Conditional row coloring	Data-driven rules admins edit without code	Hard-coded unless you build a rule engine	Usually fixed decoration attributes in XML
Bulk inline edits	Multi-record write via ORM, honors constraints and rules	Feasible but validation handling is on you	Varies; many skip record-rule enforcement
Excel / CSV export	One-click styled xlsx and csv matching the filtered view	Buildable with xlsxwriter, extra dev time	Often plain export, formatting inconsistent
Saved presets	Per user and shareable group presets, one-click switch	Requires designing the preset model yourself	Sometimes offered, rarely group-shareable
ACL / record-rule respect	Built against your ir.model.access and ir.rule	Depends entirely on developer discipline	Generic; may not match your security model
Fit to your models	Scoped to your exact models and workflows	Fully bespoke but full cost and timeline	Generic across all models, no tailoring
Support & ownership	Post-go-live support window plus git repo handover	Whatever you staff internally	Vendor tickets, shared roadmap, no source ownership

Frequently Asked Questions about Advanced List View Manager

How long does delivery take?

Because this is build-to-order rather than an instant download, typical delivery is two to four weeks from confirmed scope. The timeline depends on how many models you want covered and the complexity of your export formatting and color rules. We lock the scope on the initial call, build against a staging copy of your database, and give you a target date before work starts.

Does it work with Odoo Community or only Enterprise?

Both. The module is built on the standard OWL web client and the ORM, which exist in Community and Enterprise alike. Enterprise ships a few extra list widgets and studio features; we confirm your edition on the scoping call and build against it so behavior matches your instance. We support Odoo 17.0, 18.0 and 19.0.

Will inline and bulk edits bypass my validations or permissions?

No. Every edit and bulk update goes through the ORM's write() method, so your @api.constrains validators, @api.depends recomputes, automated actions and audit logging all fire exactly as they do on a form. Column visibility and edit rights honor your ir.model.access.csv and ir.rule record rules, so a user never sees or writes a field they aren't entitled to.

Does it override or break my existing custom list views?

No. It extends the list renderer and reads field metadata rather than replacing your base view definitions, so your inheritance chains and custom XML stay intact. Presets and color rules are stored as data, not hard-coded into views, which also makes upgrades safer.

How do updates and support work after go-live?

Every build includes a post-go-live support window for bug fixes and adjustments within the delivered scope. You also receive the full git repository, so your own team can maintain and extend the module. For moving to a new Odoo major version or adding capabilities later, we scope that as a separate upgrade engagement and provide compatibility notes with the handover.

Can different users see different columns on the same list?

Yes. Column selection, order and width are persisted per user, keyed to res.users and the target model, so two people opening the same Sales Order list each keep their own layout. Admins can additionally push a group-level default preset so a team starts from a consistent configuration.

What does the Excel export actually contain?

The export produces a styled .xlsx (via xlsxwriter, the same library Odoo uses for spreadsheet reports) or a clean .csv reflecting exactly what's on screen: the visible columns, the current sort order and any active filters. On large recordsets we batch the read to avoid worker timeouts, so exporting thousands of rows stays reliable.