Record Templates & Quick
Save any record as a template and one-click clone it with field overrides
Re-keying near-identical records — the same service order, the same project skeleton, the same product setup — wastes hours every week and invites copy-paste mistakes. Odoo's native duplicate copies one record with no saved defaults, no governance and no cross-model reuse. This app lets any team snapshot ANY record as a named, override-aware template and spin up new records (or whole bundles) in one click. Sales, project managers and operations stop retyping and start cloning, with usage tracking proving how much repetitive entry it removes — all with zero custom code.
Key Features
Save any record as a template from the Action menu
A generic server action is automatically bound to every installed model on setup, so the Save as Template entry appears in the Action (⚙) dropdown on any list or form view - partners, sale orders, products, projects, tasks, and more. Selecting a record and clicking Save as Template opens the wizard, which snapshots the record's stored fields into a reusable gb.record.template via capture_from_record. After installing new Odoo apps use the Rebind Action to All Models menu item to extend coverage instantly.
One-click create and open
Each template's action_create_one button instantiates a single record and opens its form immediately. The instantiate() method rebuilds create vals from the captured JSON, validates field names against the live model, and bumps use_count and last_used so you can trust the audit trail.
Quick-create wizard with runtime overrides
action_quick_create opens gb.quick.create.wizard, which seeds one override line per captured field. Tick Override on the fields you want to change, type a new value, set how many copies, and action_create makes them all — typed_value() casts your text to the correct integer, float, boolean or many2one.
Per-template default overrides
override_ids hold structured gb.record.template.override lines applied automatically on every instantiation — always blank a reference, force a default stage. _build_create_vals layers captured values, template defaults, then runtime overrides so the right value always wins.
Field blacklist keeps clones clean
A GLOBAL_BLACKLIST drops id, create/write metadata, messages and activities, and the blacklist_fields char lets you add per-template skips. Volatile fields never get copied, so cloned records start in a clean, consistent state.
Template bundles for multi-record setups
gb.record.template.bundle groups several templates with per-line multipliers (count, capped at 200). action_run instantiates every line in sequence order — a project plus its standard tasks, a customer plus default contacts — and opens the first model's results in one go.
Usage tracking and favourites
Templates record use_count, last_used and an is_favorite flag (action_toggle_favorite), while bundles track run_count and last_run. The list is ordered favourites-first so your handiest patterns sit at the top, and field_count shows how rich each snapshot is.
Works on any model, no code
model_id points at ir.model and model_name carries the technical name, so a dynamic selector lets templates target sale orders, products, partners, projects or tasks alike. _copyable_fields introspects each model at runtime, so there is no per-model coding to maintain.
Use Cases
Screenshots
Bundles
Record Templates
Save As Template
Why Choose This Module
Snapshot ANY Odoo record — a sale order, a project, a product, a partner, a task — as a named template, then spin up new records from it in one click, optionally overriding a few fields at creation time. Native Odoo has duplicate, but no governed, reusable, override-aware template library that works across every model. This adds exactly that.
Specifications
- Compatible: Odoo 18.0 / 19.0
- License: OPL-1
- Languages: English
- Author: Pokutsoft
- Dependencies: base
- Support: support@pokutsoft.com
Update date: 2026-07-02