[ADD] estate: started the server framework, completed the coding guidelines, setup guide, and chapter 1 by abkus-odoo · Pull Request #1348 · odoo/tutorials

abkus-odoo · 2026-06-23T12:03:09Z

Real Estate Management Module

Complete Property Lifecycle: Managed properties from creation to sale, including offer submission, acceptance, and rejection workflow.

Relational Data Structure: Utilized Many2one, One2many, and Many2many relationships to build a structured and connected data model.

Dynamic Business Logic: Implemented computed fields and onchange methods to enable automatic calculations and responsive UI behavior.

Data Integrity Enforcement: Applied Python constraints and SQL constraints to ensure valid and consistent business data.

User-Friendly Interface: Designed intuitive list, form, and search views along with proper actions and menu navigation.

Access & Security Management: Configured access rights and record rules to control data visibility and ensure secure usage.

robodoo · 2026-06-23T12:03:13Z

abkus-odoo · 2026-06-24T05:25:48Z

#1265
Continue Estate Module

bit-odoo

Hello
can you please improve all your all commit message tags, header, and also improve the PR title and description.

Thanks

bit-odoo · 2026-06-26T08:50:54Z

+
+
+class EstateProperty(models.Model):
+


unneccary space.

bit-odoo · 2026-06-26T09:01:14Z

+    _check_expected_price = models.Constraint(
+        "CHECK(expected_price>0)", "Expected price must be strictly positive"
+    )
+
+    _check_selling_price = models.Constraint(
+        "CHECK(selling_price>0)", "Selling price must be positive"
+    )


Can you please follwe the coding guidelines?
https://www.odoo.com/documentation/19.0/contributing/development/coding_guidelines.html#symbols-and-conventions

bit-odoo · 2026-06-26T09:02:42Z

+                vals['property_id'])
+            for offer in property_id.offer_ids:
+                if current_price < offer.price:
+                    raise UserError(


It is good if you make the error message translatable.

suggested changes are done

bit-odoo · 2026-06-26T09:03:52Z

+
+    name = fields.Char(required=True)
+    color = fields.Integer()
+    _unique_price = models.Constraint(


Should be one empty line before it.

bit-odoo · 2026-06-26T09:04:27Z

+
+
+class ResUsers(models.Model):
+


unneccary extra line.

bit-odoo · 2026-06-26T09:06:11Z

+                            <field name="postcode" />
+                            <field name="expected_price" />
+                        </group>
+


unneccary extra line.

bit-odoo · 2026-06-26T09:06:16Z

+                                options="{'color_field': 'color'}" />
+                        </group>
+                    </div>
+


unneccary extra line.

bit-odoo · 2026-06-26T09:08:41Z

+                        <page string="Offer">
+                            <field name="offer_ids" readonly="state in ('offer_accepted', 'sold', 'canceled')"/>
+                        </page>
+


unneccary extra line.

bit-odoo · 2026-06-26T09:08:47Z

+                                <field name="total_area" />
+                            </group>
+                        </page>
+


unneccary extra line.

bit-odoo · 2026-06-26T09:22:04Z

+                                <field name="garden_area" invisible="not garden"/>
+                                <field name="garden_orientation" invisible="not garden"/>
+                                <field name="active" />
+                                <field name="state" />


No need to define this field here, as we already display it in the header.

- Added estate.property model - Defined basic property fields - Added understanding of Odoo three-tier architecture

- Created estate module structure - Added __init__.py and __manifest__.py - Configured base module dependency - Enabled module as an installable app

- Created estate.property ORM model - Added core property fields (name, description, postcode, prices, features) - Defined garden orientation selection (North, South, East, West) - Set required constraints on important fields (name, expected_price) - Initialized estate_property database table via ORM

- Created ir.model.access.csv for estate.property model - Added read, write, create and delete permissions - Learned how Odoo security works using access rights - Added security file in __manifest__.py - Fixed access warning for estate.property model

- Added estate_property_views.xml with basic act_window action - Connected estate.property model with UI through action - Understood how menu > action >view >model flow works in Odoo - Created views folder and add the estate_property_views.xml file - After adding this file Odoo loads it successfully during module update - Action gets created in the database but nothing shows in UI bcz menu is not added

- Added estate_menu.xml and connected menu with action - Added estate_property_views.xml with list and form views - Learned basic structure of Odoo views and actions - Completed Chapter 5 and understood form/list view concepts - Practiced menu >action >view connection flow

- Added custom search view for estate properties - Implemented search fields for property filtering - Added predefined filters and group by functionality - Practiced and understood search views, filters, domains, and group by concepts from Chapter 6 exercise

- Started Chapter 7 on relational fields - Revised earlier Odoo tutorial chapters - Reviewed models, views, ORM, and field concepts

- Fixed code formatting issues and removed unnecessary whitespace - Cleaned up XML and Python structure for better readability - Started learning relational fields (Many2one) - Began exercises from the chapter on Many2one fields

- Studied Many2one field behavior and relationships - Explored res.partner and res.users models - Started implementing Many2one field exercises in estate module - Improved understanding of relational fields in Odoo

- Learned Many2many stores recordsets (multiple linked records) - Understood comodel_name defines target model relationship - Learned optional relation table and column mapping behavior - Understood ORM auto-generates relation table if not specified

Completed Many2many field exercise for property tags - Added estate.property.tag model estate_property_tag.py - Created views for property tags list and form views - Added menu and action for Property Tags in Estate module

- Completed One2many field exercise, added estate_property_offer model, and implemented its views - Added offer_ids field in estate_property_offer.py

- Started learning computed fields and completed the first exercise - Added total_area field in estate_property.py - Computed total_area from living_area and garden_area using a compute method

- Added best_offer field on estate.property - Implemented compute method using mapped() to determine highest offer price - Updated dependencies on offer_ids.price for automatic recomputation

- Added validity and date_deadline fields to estate.property.offer - Implemented computed date_deadline field with @api.depends - Added inverse method to recalculate validity from deadline date - Added garden onchange in estate.property to auto-set garden area and orientation - Configured default values and field synchronization for offer deadlines

- Added Cancel and Sold actions on estate.property with state transition validation - Prevented cancelled properties from being sold and sold properties from being cancelled using UserError - Added Accept and Refuse actions on estate.property.offer - Implemented offer status updates and corresponding form view buttons with icons

- Added SQL constraints in estate models: - property: expected_price > 0, selling_price >= 0 - offer: price > 0 - tag: UNIQUE(name) - property type: UNIQUE(name

…dget - Added property_ids One2many field in estate.property.type - Implemented inline list view for properties in property type form - Added statusbar widget in estate.property state field - Updated form view to display related properties with limited fields

- Added model ordering for properties, offers, tags, and property types Added sequence field with manual ordering support for property types Configured property type field to disable create/edit from property form Added color field to tags and enabled color picker widget

- Added invisible rules for garden fields and offer buttons - Restricted offer creation based on property state (readonly) - Made list views editable for property, offer and tags - Updated list view fields (optional date_availability, hidden by default) - Added decorations for property and offer states - Set default 'Available' filter and updated living area search domain

- Added stat button on estate.property.type to open estate.property.offer action using type='action' - Displayed all related offers using offer_ids and offer_count in the view - Implemented navigation from property type to offers list view via smart/stat button - Added domain filter on estate.property.offer action to show only offers linked with active property type (property_type_id = active_id)

-Added business logic to CRUD methods -Prevented deletion of properties unless state is 'New' or 'Cancelled' -Updated property state to 'Offer Received' when creating offers -Added validation to prevent lower offers than existing ones -Added property_ids field to users with available properties domain

- Created dedicated estate_account link module for Estate and Accounting integration - Preserved modular design by avoiding a hard dependency on the Accounting module - Overrode the property sale confirmation workflow to generate invoices on sale - Automatically created a customer invoice for the buyer when a property is marked as sold - Added invoice lines for a 6% sales commission and a fixed 100.00 administrative fee - Applied invoicing business rules defined for the tutorial

abkus-odoo self-assigned this Jun 23, 2026

abkus-odoo requested a review from bit-odoo June 23, 2026 12:03

abkus-odoo closed this Jun 24, 2026

abkus-odoo reopened this Jun 24, 2026

abkus-odoo force-pushed the 19.0-tutorial-abkus branch from a66e25d to c5b86bf Compare June 25, 2026 13:09

bit-odoo reviewed Jun 26, 2026

View reviewed changes

abkus-odoo force-pushed the 19.0-tutorial-abkus branch 2 times, most recently from 1a1df35 to 9a5ac58 Compare June 30, 2026 05:36

[ADD] estate: Create estate property model

c899377

- Added estate.property model - Defined basic property fields - Added understanding of Odoo three-tier architecture

abkus-odoo force-pushed the 19.0-tutorial-abkus branch 3 times, most recently from abd60ed to c5b8376 Compare June 30, 2026 06:09

abkus-odoo added 16 commits July 1, 2026 16:13

[IMP] estate: Initialize Estate application module

50755fd

- Created estate module structure - Added __init__.py and __manifest__.py - Configured base module dependency - Enabled module as an installable app

[IMP] estate: revise previous chapters and begin relational fields

d320f73

- Started Chapter 7 on relational fields - Revised earlier Odoo tutorial chapters - Reviewed models, views, ORM, and field concepts

[IMP] estate: learn and implement Many2one relations

85beace

- Studied Many2one field behavior and relationships - Explored res.partner and res.users models - Started implementing Many2one field exercises in estate module - Improved understanding of relational fields in Odoo

[ADD] estate: implement Many2many tags for properties

cc5d490

Completed Many2many field exercise for property tags - Added estate.property.tag model estate_property_tag.py - Created views for property tags list and form views - Added menu and action for Property Tags in Estate module

[ADD] estate: implement One2many offers for properties

bb1821b

- Completed One2many field exercise, added estate_property_offer model, and implemented its views - Added offer_ids field in estate_property_offer.py

[ADD] estate: implement computed total_area field

abd8b8f

- Started learning computed fields and completed the first exercise - Added total_area field in estate_property.py - Computed total_area from living_area and garden_area using a compute method

[ADD] estate: compute best offer using mapped()

61ddca8

- Added best_offer field on estate.property - Implemented compute method using mapped() to determine highest offer price - Updated dependencies on offer_ids.price for automatic recomputation

abkus-odoo added 7 commits July 1, 2026 16:13

[ADD] estate: implement SQL constraints for data integrity

fc9fa2c

- Added SQL constraints in estate models: - property: expected_price > 0, selling_price >= 0 - offer: price > 0 - tag: UNIQUE(name) - property type: UNIQUE(name

abkus-odoo force-pushed the 19.0-tutorial-abkus branch from 6afcf26 to e6d6e48 Compare July 1, 2026 10:44



		class EstateProperty(models.Model):



		class ResUsers(models.Model):

Uh oh!

Conversation

abkus-odoo commented Jun 23, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

robodoo commented Jun 23, 2026

Uh oh!

abkus-odoo commented Jun 24, 2026

Uh oh!

bit-odoo left a comment

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

3 participants

abkus-odoo commented Jun 23, 2026 •

edited

Loading