Skip to Content

Required Field Asterisk

by
Odoo
v 18.0 Third Party 18
Download for v 18.0 Deploy on Odoo.sh
You bought this module and need support? Click here!
Odoo 18 · Pure CSS · Zero Config

Required Field Asterisk

Never let users miss a mandatory field again. This lightweight module adds a clear red * to every required field across all Odoo 18 backend form views — labeled fields, no-label fields, full-width fields, and custom title headers included.

LGPL-3 Depends: web No Python · No DB Migration No Configuration Needed by ERP23 · erp-23.com
🅄 All Field Layouts Covers labeled, nolabel, full-width, and oe_title header fields — every required field gets marked.
⚡ Zero Footprint Pure CSS. No Python models, no database tables, no settings menus. Install and it just works.
✓ Instant UX Improvement Users immediately see which fields are mandatory before submitting — reducing form errors and re-work.

Overview

Odoo's native form views do not display a visible indicator on required fields until after a failed save attempt. Required Field Asterisk adds a red * marker proactively — before the user even tries to save — so mandatory fields are clear at a glance. The implementation is a single focused SCSS file that targets every known required-field DOM layout in Odoo 18.

All Required Field Layouts Covered

Case 1

Labeled Field in Group

Standard fields with a visible label inside an o_group container.

Case 2

No-Label Field

Fields using nolabel="1" — marker added before the field widget itself.

Case 3

Full-Width Separator Field

Required fields placed after an o_horizontal_separator that spans the full form width.

Case 4a

Title Header with Label

oe_title blocks where a separate label.oe_edit_only element is present.

Case 4b

Title Header without Label

oe_title blocks where the required field is an inline <h1> with no separate label (e.g. Contacts).

Screenshot

Required Field Asterisk in action

Red * markers on all required fields — labeled, nolabel, title headers, and full-width fields

✓ What is Covered

  • Labeled fields inside o_group
  • Fields with nolabel="1"
  • Full-width required fields (after separators)
  • oe_title headers with and without labels
  • Edit mode only — no marker in readonly/view mode
  • Works across all standard Odoo 18 form views

⊗ What is NOT Affected

  • Radio button option labels (e.g. Send / Receive)
  • One2many / Many2many table fields (x2many)
  • Required fields in list / kanban / pivot views
  • Website / portal views
  • Read-only records

Installation

  1. Download the module from the Odoo App Store.
  2. Place the bs_required_field_asterisk folder in your Odoo addons directory.
  3. Restart the Odoo server.
  4. Go to Settings → Apps, search for Required Field Asterisk, and click Install.
  5. Navigate to any form view — all required fields now show a red *.
No configuration required. The module activates immediately after installation. There are no settings menus, no models, no database migrations. To remove it, simply uninstall it.

Technical Details

📄
Single SCSS File One focused stylesheet — no Python, no XML models, no JS
🛡
Odoo 18 Ready Targets the exact DOM structures used in Odoo 18 Community & Enterprise
⚖
LGPL-3 License Open source — free to use, modify, and distribute
🚀
Zero Performance Impact Pure CSS compiled at deploy time — zero runtime JavaScript overhead

Support & Contact

We’re here to help — reach out via any channel below.

🌐
Website erp-23.com
🐞
Bug Reports GitHub Issues
🏢
Company BrainStation-23

© 2025 ERP23 — a product of BrainStation-23. Released under LGPL-3. Compatible with Odoo 18.0.

Availability
Odoo Online
Odoo.sh
On Premise
Lines of code 37
Technical Name bs_required_field_asterisk
LicenseLGPL-3
Websitehttps://erp-23.com

Please log in to comment on this module

  • The author can leave a single reply to each comment.
  • This section is meant to ask simple questions or leave a rating. Every report of a problem experienced while using the module should be addressed to the author directly (refer to the following point).
  • If you want to start a discussion with the author, please use the developer contact information. They can usually be found in the description.