Odoo Field Inspector

Inspect Odoo form fields & list columns: CSS selector, XPath, technical field name, and live ir.model.fields data.

Odoo Field Inspector is a developer tool for Odoo functional consultants, implementation partners, and developers who need a field's technical name, XPath, or CSS selector without digging through Odoo's Technical Settings or opening Chrome DevTools. It works off the Odoo web client's standard markup (`.o_field_widget[name]`, list-view `data-name` columns) rather than a hardcoded version check, so it isn't tied to one specific Odoo release. Click a form field's label or a table's column header on any page — Odoo or not — and a developer-tool style panel slides in with everything about it: element type, id/name, classes, current and default value, required/read-only/disabled state, validation and ARIA attributes, a working CSS selector, an XPath, its parent element, and the owning <form>. FORM VIEW Click a <label>, <input>, <select>, <textarea>, checkbox/radio, contenteditable field, or an ARIA-labelled custom control. LIST VIEW Click a <th> or [role="columnheader"] to see the column name, index, attributes, selector, and a sample of the input control used in that column. Click a plain data cell instead of the header to see its row/ column position and (on Odoo pages) the same live field lookup below. BUILT FOR ODOO DEVELOPERS When a clicked field belongs to an Odoo form, list, or wizard, the panel leads with a live Odoo Field Definition pulled straight from that Odoo server: the model, the field's real ORM type, relation, required/ readonly/stored state, help text, decoded selection options, how the field is actually declared in the current view (widget=, domain=, context=, invisible=, required=, ...), a direct link to the field's own admin record, and a ready-to-paste <field name="..."/> view XML snippet. No more guessing a field's technical name from CSS classes. This has its own on/off toggle in the popup, separate from the general inspector switch, and follows your system's light/dark theme. KNOWS YOUR ODOO VERSION The panel reads your server's Odoo version once per tab and shows it, then builds the "Open in Odoo" link in the URL style that version actually supports: the old /web#model=...&id=... link on Odoo 16 and earlier, the /odoo/action-... route on 17 and later. The same link shape is used in Copy All, so pasted notes keep working. If the version can't be read, you get both link styles and an explanation instead of a broken link. KNOWS WHICH VIEW XML ID YOU'RE LOOKING AT The rendered page is a merge of a whole stack of views, so it can't tell you which file it came from. The panel resolves that: the active view's XML ID (e.g. base.view_partner_form), the chain it inherits from (e.g. your own my_addon.view_partner_form_inherit on top of it), and a direct link into Settings > Technical > Views for each one. List columns report the list view's own XML ID, not the form view's. It reads view metadata only, never the view's source XML. MAKE IT YOURS A gear in the panel header opens a Settings page: pick Light, Dark, or follow your system (which now repaints live when your OS flips); choose one of six accent colors that recolor links, tabs, the primary button and the outlines the extension draws around detected fields; and switch between Comfortable and Compact density. Every other setting — Highlight, Intercept clicks, Odoo Developer Mode, Show Sensitive Values, Copy format — lives in the same place. Your choice is remembered, and the popup matches it. Nothing about your theme is ever sent anywhere. A FULL SETTINGS PAGE, IN ITS OWN TAB Prefer room to breathe? The popup stays a quick on/off panel, and "All settings" underneath Enable Inspector opens the complete settings in a real browser tab: every setting, grouped as Appearance, Detection, Behavior and Debug, with a live preview of the actual inspector panel — the same stylesheet, icons and colors it uses on the page — that repaints as you change anything. It also shows the sites you chose to auto-enable the inspector on, so you can add or remove one (and hand that access back to Chrome) in one place, and a plain-language summary of what the extension does and does not send anywhere. Change a setting in the popup and the open tab follows, and the other way round: they are the same settings, not two. DEBUG WHEN YOU NEED IT Add ?debug=1 to a page's URL (or flip Debug logging in Settings) for verbose console diagnostics and a live readout of the effective settings. ?debug=0 forces it off; the URL always wins over the saved switch, it is never stored, and it can never turn the inspector on by itself. ODOO BUTTONS A dedicated Button tab tells you what a button will actually do: the Python method it calls, the action it opens, the special= built-in, the confirmation it asks for first, and the record (data-model/data-id) it would act on. Buttons are never hijacked by a normal click — in the default mode, clicking Save is just clicking Save — so you inspect them either with "Intercept clicks" off or by picking one in the search below, which opens a button's panel without pressing it. Attributes like groups=, invisible= and readonly= come from the button's own declaration in the view, because the rendered page does not keep them. FIELD FINDER A floating search button opens a page-wide search: filter every field, list column, and Odoo button on the page by label or technical name, live as you type, then click a result to jump straight to its full inspector panel. If an Odoo wizard (dialog) is open, the search automatically scopes to just that wizard's fields. NEVER TOUCHES YOUR DATA (BY DEFAULT) While inspecting, clicks on fields are intercepted before the page sees them — labels never toggle checkboxes, <select> never opens, and no value or focus state ever changes. Turn the inspector off and the page behaves exactly as it did before. CLICK-THROUGH WHEN YOU NEED IT Prefer to keep filling the form while you inspect it? Turn "Intercept clicks" off and the panel still opens on your click, but the click reaches the page normally, exactly as it would without the extension. It is a toggle, never the default, and the inspector still never writes to a field or submits anything itself. SENSITIVE VALUES REDACTED Values of password inputs, hidden token/CSRF fields, and other secret-named fields never appear in the panel, in Copy All, or in JSON output — they are replaced with a redaction marker before anything can be displayed or copied. Turn on "Show sensitive values" only when you actually need them. START AUTOMATICALLY ON YOUR OWN ODOO By default the inspector starts only when you turn it on, and a page reload switches it off again. Tick "Auto-enable on this site" in the popup and it starts by itself every time you load a page on that one site. Chrome asks for access to that origin only, the sites you remembered are listed in the popup and in the Settings page with a Remove button, and turning it off hands the access straight back to Chrome. Remembering one site never grants access to any other. PRIVACY Everything runs locally in your browser. The full Settings page is a page of this extension that only reads and writes your own local settings — it has no access to any page you are viewing. Theme, accent, density and the debug switch are local preferences, stored on your machine and never transmitted; a ?debug= parameter in a page URL is read only in that page's own tab, is never stored, and cannot enable the inspector by itself. The one exception: the Odoo field lookup above, which — only for fields recognized as Odoo fields — asks the SAME Odoo server you're already logged into for that field's definition, using your existing session, plus — when you inspect a button — that button's model and method/action name so its declaration can be read from the view (buttons are never intercepted on a normal click, and no record data, label, or target record is sent), plus one fixed hard-coded config key (web.base.build.description, at most once per tab) to read your server's version, and that model's view metadata (which view XML ID you're looking at and what it inherits from — ids and names, never the view's source XML). No field values, browsing history, or personal data are ever sent, and there is no server or analytics of ours in the loop at all. No host permissions are requested unless you opt in to per-site auto-enable, which grants access to the single site you pick and nothing else. Full privacy policy: https://mehedimk.github.io/Odoo-Field-Inspector/privacy.html No host permissions are requested up front, so Chrome never shows the broad "read and change all your data on all websites" warning: content scripts only run on a tab after you explicitly enable the inspector for it. The one exception is opt-in and per site: if you tick "Auto-enable on this site" in the popup, Chrome asks you to allow the extension on that one origin so the inspector can start automatically when you load pages there. It is used for nothing else, it is listed with a Remove button in the popup, and unticking it revokes the permission in Chrome too. WHO IT'S FOR Odoo developers debugging a view, functional consultants who need a field's technical name for a customization request without asking a developer, QA/testers writing CSS selectors for automated tests, and anyone who wants a field or table column's CSS selector and XPath on any website — not just Odoo. If you've ever opened Odoo's Technical Settings, turned on developer mode just to find one field's technical name, or hand-written a CSS selector by guessing at DOM structure in Chrome DevTools, this replaces that whole detour with one click.