[ADD] estate: implement core estate management features #1109

jakan-odoo · 2026-01-01T11:41:35Z

Added models for properties, property types, tags, and offers
Designed a structured data model to manage real estate records
Created menus and actions for a clear and user-friendly interface
Implemented validations for expected and selling prices
Handled business rule violations using UserError and ValidationError

- Real Estate module created - Basic structure and required fields added - CHAPTER 1, 2, and 3

- Added basic security access for estate records - Fixed missing whitespace and formatting issues - Covers CHAPTER 4

robodoo · 2026-01-01T11:41:39Z

- Added form and list views for estate records - Added menu and action to access the module - Covers CHAPTER 5

- Added list, form, and search views - Added domains and group by options - Covers CHAPTER 6

mash-odoo

Hello @jakan-odoo,
Good start on the PR,
Please view the comments and apply the needed changes.

mash-odoo · 2026-01-02T12:54:41Z

estate/models/estate_property.py

+from odoo import fields, models
+from dateutil.relativedelta import relativedelta


For ordering of imports, refer this: https://www.odoo.com/documentation/19.0/contributing/development/coding_guidelines.html#imports

mash-odoo · 2026-01-02T12:56:10Z

estate/views/estate_property_views.xml

+    <record id="estate_property_list_view" model="ir.ui.view">
+        <field name="name">estate.property.list</field>


For naming a view: <model_name>_view_<view_type>, where view_type is kanban, form, list, search, …
You can refer this guideline: https://www.odoo.com/documentation/19.0/contributing/development/coding_guidelines.html#xml-ids-and-naming

mash-odoo · 2026-01-02T13:11:41Z

estate/views/estate_property_views.xml

+    <record id="estate_property_form_view" model="ir.ui.view">
+        <field name="name">estate.property.form</field>


Do same as suggested above

- Added Many2one relation between models - Improves data linking between records - Covers CHAPTER 7

- Added One2many and Many2many relations between models - Improves linking and management of related records - Covers CHAPTER 7

- Added computed fields for automatic values - Added onchange methods to update fields - Covers CHAPTER 8

- Created Sell, Cancel, Accept, and Refuse buttons - Buttons call related methods on the estate models - Buyer and selling price are set when an offer is accepted - Covers CHAPTER 9

mash-odoo

Hello,
Good going on the task..
Here are some suggestions..

mash-odoo · 2026-01-06T12:18:39Z

estate/views/estate_property_views.xml

+                <field name="bedrooms"/>
+                <field name="living_area"/>
+                <field name="selling_price"/>
+                <filter string="Available Properties" name="available properties" domain="['|', ('state', '=', 'new'), ('state', '=', 'offer_received')]"/>


Can we write this filter in any other way?

Yes ma'am,
We can write filter like this
<filter string="Available Properties" name="available_properties" domain="[('state', 'in', ('new', 'offer_received'))]"/>

mash-odoo · 2026-01-06T12:34:52Z

estate/views/estate_property_tag_views.xml

+            </form>
+        </field>
+    </record>
+</odoo>


Leave a line at the end of file

mash-odoo · 2026-01-06T12:39:38Z

estate/models/estate_property.py

+            ("north", "North"),
+            ("south", "South"),
+            ("east", "East"),
+            ("west", "West")])


Suggested change

("north", "North"),

("south", "South"),

("east", "East"),

("west", "West")])

('north', "North"),

('south', "South"),

('east', "East"),

('west', "West")])

mash-odoo · 2026-01-06T12:40:18Z

estate/models/estate_property.py

+            ('new', 'New'),
+            ('offer_received', 'Offer Received'),
+            ('offer_accepted', 'Offer Accepted'),
+            ('sold', 'Sold'),
+            ('cancelled', 'Cancelled'),


Suggested change

('new', 'New'),

('offer_received', 'Offer Received'),

('offer_accepted', 'Offer Accepted'),

('sold', 'Sold'),

('cancelled', 'Cancelled'),

('new', "New"),

('offer_received', "Offer Received"),

('offer_accepted', "Offer Accepted"),

('sold', "Sold"),

('cancelled', '"Cancelled"),

mash-odoo · 2026-01-06T12:40:53Z

estate/__manifest__.py

@@ -0,0 +1,20 @@
+{
+    'name': 'Real Estate',


Suggested change

'name': 'Real Estate',

'name': "Real Estate",

mash-odoo · 2026-01-06T12:41:15Z

estate/__manifest__.py

+    'version': '1.0',
+    'category': 'Real Estate',
+    'summary': 'Manage real estate properties',
+    'description': 'This module allows managing properties.',


Suggested change

'description': 'This module allows managing properties.',

'description': "This module allows managing properties.",

mash-odoo · 2026-01-08T09:50:40Z

estate/models/estate_property.py

+from dateutil.relativedelta import relativedelta
+from odoo import fields, models, api


For ordering of imports, refer this: https://www.odoo.com/documentation/19.0/contributing/development/coding_guidelines.html#imports

- Added SQL constraints to ensure data validity - Added Python constraints for business rules - Covers CHAPTER 10

- Added inline views for related records - Applied widgets to improve user interface - Set default ordering using _order - CHAPTER 11

- Added maintenance request model with title, cost, and status - Ensured approved requests have a positive cost - Displayed total maintenance cost on the property - Prevented property sale when maintenance is not completed

- Replaced direct cost check with float_is_zero - Ensures correct validation for decimal precision

- Added manual ordering and widget options - Applied conditional button visibility using invisible - Made list views editable and some fields optional - Added decorations, default filters, and stat buttons - Covers CHAPTER 11

mash-odoo

Hello!
Thank you for your work..
Here are some suggestions and questions..

estate/models/estate_property_offer.py

mash-odoo · 2026-01-12T12:34:05Z

estate/models/estate_property_offer.py

+            offer.status = "refused"
+        return True
+
+    _check_offer_price_positive = models.Constraint(


Follow this conventions while declaring fields, constraints, methods or CRUD operations.

mash-odoo · 2026-01-12T12:34:26Z

estate/models/estate_property_type.py

+    _order = 'name'
+
+    name = fields.Char(required=True)
+


Suggested change

estate/views/estate_property_views.xml

estate/views/estate_property_type_views.xml

estate/models/estate_property.py

mash-odoo · 2026-01-13T05:01:30Z

estate/models/estate_property.py

+            property.state = 'cancelled'
+        return True
+
+    _check_expected_price_positive = models.Constraint(


Follow this conventions while declaring fields, constraints, methods or CRUD operations.

estate/models/estate_property.py

mash-odoo · 2026-01-16T11:02:57Z

estate/views/estate_property_views.xml

+                <header>
+                    <field name="state" widget="statusbar" statusbar_visible="new,offer_received,offer_accepted,sold"/>
+                </header>
+                <sheet>
+                    <header>
+                        <button name="action_sold" type="object" string="Sold" class="btn-primary" invisible="state in ('sold', 'cancelled')"/>
+                        <button name="action_cancel" type="object" string="Cancel" class="btn-secondary" invisible="state in ('sold', 'cancelled')"/>
+                    </header>


Suggested change

<header>

<field name="state" widget="statusbar" statusbar_visible="new,offer_received,offer_accepted,sold"/>

</header>

<sheet>

<header>

<button name="action_sold" type="object" string="Sold" class="btn-primary" invisible="state in ('sold', 'cancelled')"/>

<button name="action_cancel" type="object" string="Cancel" class="btn-secondary" invisible="state in ('sold', 'cancelled')"/>

</header>

<header>

<field name="state" widget="statusbar" statusbar_visible="new,offer_received,offer_accepted,sold"/>

<button name="action_sold" type="object" string="Sold" class="btn-primary" invisible="state in ('sold', 'cancelled')"/>

<button name="action_cancel" type="object" string="Cancel" class="btn-secondary" invisible="state in ('sold', 'cancelled')"/>

</header>

<sheet>

You can add these buttons directly in the header.

- Used Python inheritance to extend existing logic - Applied model inheritance to add fields and behavior - Used view inheritance to update and extend UI - Covers CHAPTER 12

- Added translatable strings for the module - Updated constraint names for clarity - Applied small user interface changes - Added archived filter for records

- Created new estate_account module - Linked estate module with account module - Added invoice creation for sold properties - Covers CHAPTER 13

- Added investor profile linked to partner data - Deleting partner removes investor, investor delete keeps partner - Computed total unsold property value on res.partner - Sum based on expected price of non-sold properties

- Added a Kanban view for estate properties - Grouped properties by type by default - Covers CHAPTER 14

- Implemented a Counter component to show reactive state using useState - Split logic into reusable child components and used them in Playground - Add Card component to showcase props, markup rendering, and validation - Added offer accept button to automatically accept the highest offer price CHAPTER 1

- Added props validation to Owl components - Implemented logic to calculate the sum of two counters CHAPTER 1

- Added a basic todo list component - Used dynamic attributes for state-based updates - Implemented event handler to add new todos CHAPTER 1

mash-odoo

Hello!
Thank you for your work.
I have added some questions and suggestions..

mash-odoo · 2026-01-29T09:14:26Z

estate/views/estate_property_views.xml

+                    <field name="state" widget="statusbar" statusbar_visible="new,offer_received,offer_accepted,sold" options="{'clickable': '1'}"/>
+                    <button name="action_sold" type="object" string="Sold" class="btn-primary" invisible="state in ('sold', 'cancelled')"/>
+                    <button name="action_cancel" type="object" string="Cancel" class="btn-secondary" invisible="state in ('sold', 'cancelled')"/>
+                    <button name="offer_accepted" type="object" string="Offer Accept" class="btn-primary"/>


Suggested change

<button name="offer_accepted" type="object" string="Offer Accept" class="btn-primary"/>

<button name="action_best_offer" type="object" string="Best Offer" class="btn-primary"/>

Give meaningful names

mash-odoo · 2026-01-29T09:15:21Z

estate/models/estate_property.py

+    def offer_accepted(self):
+        for record in self:
+            if not record.offer_ids:
+                raise UserError("There are no offers to accept")
+
+            best_offer = max(record.offer_ids, key=lambda p: p.price)
+            best_offer.action_accept()


Try optimizing this. Instead of throwing user error, maybe handle the visibility of the button directly on the state where it should be shown.

estate_property.py

def action_best_offer(self): for record in self: best_offer = max(record.offer_ids, key=lambda p: p.price) best_offer.action_accept() return True

estate_property_views.xml
<button name="action_best_offer" type="object" string="Best Offer" class="btn-primary" invisible="not offer_ids"/>

mash-odoo · 2026-01-29T09:15:44Z

estate/models/estate_property_maintenance.py

+            ('new', "New"),
+            ('approved', "Approved"),
+            ('done', "Done"),
+            ('cancle', "Cancle")


Suggested change

('cancle', "Cancle")

('cancel', "Cancel")

mash-odoo · 2026-01-29T09:15:57Z

estate/models/estate_property_maintenance.py

+    _description = 'Estate Property maintenance'
+
+    title = fields.Char(required=True)
+    cost = fields.Float(string="Cost")


no need to give the string

mash-odoo · 2026-01-29T09:18:02Z

estate/views/estate_property_maintenance_views.xml

+            <list>
+                <field name="title"/>
+                <field name="cost"/>
+                <button name="maintenance_accept" type="object" string="Confirm" icon="fa-check"/>


Suggested change

<button name="maintenance_accept" type="object" string="Confirm" icon="fa-check"/>

<button name="action_accept_maintenance" type="object" string="Confirm" icon="fa-check"/>

estate/views/estate_property_type_views.xml

mash-odoo · 2026-01-29T09:20:17Z

.gitignore

+
+i18n


unnecessary diff

mash-odoo · 2026-01-29T09:26:59Z

estate/models/estate_property_offer.py

+            # Set property state
+            property_rec.state = "offer_received"
+
+        return super().create(vals_list)


Why do we call super()?

We call super because it calls to parent create() method and the parent method is used for saving the record in database.

mash-odoo · 2026-01-29T09:33:09Z

estate/models/estate_property.py

+    seller_id = fields.Many2one("res.users", string="Seller", default=lambda self: self.env.user)
+    tag_ids = fields.Many2many("estate.property.tag", string="Property Tags")
+    offer_ids = fields.One2many("estate.property.offer", "property_id", string="Property Offers")
+    total_area = fields.Float(string="Total Area", compute="_compute_total_area", store=True)


Can you try implementing searching/filtering of data without using store=True?

Without using store=True i can use search method for searching data

estate_property.py
total_area = fields.Float(string="Total Area", compute="_compute_total_area", search="_search_total_area")

@api.depends('living_area', 'garden_area') def _compute_total_area(self): for property in self: property.total_area = property.living_area + property.garden_area

def _search_total_area(self, operator, value): if operator == '>' and value == 500: records = self.search([]) ids = [] for rec in records: if (rec.living_area) + (rec.garden_area) > 500: ids.append(rec.id) return [('id', 'in', ids)] return []

estate_property_views.xml
<filter string="Total Area > 500" name="total_area_gt_500" domain="[('total_area', '>', 500)]"/>

mash-odoo · 2026-01-29T09:34:36Z

estate/models/estate_property.py

+    def action_cancel(self):
+        for property in self:
+            if property.state == 'sold':
+                raise UserError("Cancelled property cannot be sold")
+            property.state = 'cancelled'
+        return True


Rewrite this without using for loop.

def action_cancel(self): if self.filtered(lambda p: p.state == 'sold'): raise UserError("Cancelled property cannot be sold") self.write({'state': 'cancelled'}) return True

- Added default properties, property types, tags, and offers - Automatically loads sample records when a new database is created - Helps users see estate records on first login

jakan-odoo added 2 commits December 31, 2025 15:47

[ADD] estate: initialize module structure and model

71296e3

- Real Estate module created - Basic structure and required fields added - CHAPTER 1, 2, and 3

[ADD] estate: add security rules and fix style

3665d34

- Added basic security access for estate records - Fixed missing whitespace and formatting issues - Covers CHAPTER 4

jakan-odoo added 2 commits January 1, 2026 18:48

[ADD] estate: add basic user interface

d8791e0

- Added form and list views for estate records - Added menu and action to access the module - Covers CHAPTER 5

[IMP] estate: create basic views and search

378ed7c

- Added list, form, and search views - Added domains and group by options - Covers CHAPTER 6

mash-odoo requested changes Jan 2, 2026

View reviewed changes

jakan-odoo added 4 commits January 5, 2026 18:45

[IMP] estate: add many2one model relation

f155702

- Added Many2one relation between models - Improves data linking between records - Covers CHAPTER 7

[IMP] estate: add one2many and many2many relations

1c69bbe

- Added One2many and Many2many relations between models - Improves linking and management of related records - Covers CHAPTER 7

[IMP] estate: add computed fields and onchanges

9131c01

- Added computed fields for automatic values - Added onchange methods to update fields - Covers CHAPTER 8

[IMP] estate: implement object-based actions

2784e60

- Created Sell, Cancel, Accept, and Refuse buttons - Buttons call related methods on the estate models - Buyer and selling price are set when an offer is accepted - Covers CHAPTER 9

mash-odoo requested changes Jan 8, 2026

View reviewed changes

jakan-odoo added 5 commits January 8, 2026 18:34

[IMP] estate: add sql and python constraints

8c66cd9

- Added SQL constraints to ensure data validity - Added Python constraints for business rules - Covers CHAPTER 10

[IMP] estate: add inline views, widgets, and order

dbb059f

- Added inline views for related records - Applied widgets to improve user interface - Set default ordering using _order - CHAPTER 11

[IMP] estate: add property maintenance requests

aee8aeb

- Added maintenance request model with title, cost, and status - Ensured approved requests have a positive cost - Displayed total maintenance cost on the property - Prevented property sale when maintenance is not completed

[FIX] estate: improve maintenance cost validation

6dd7eec

- Replaced direct cost check with float_is_zero - Ensures correct validation for decimal precision

[IMP] estate: enhance views with UI improvements

ac29768

- Added manual ordering and widget options - Applied conditional button visibility using invisible - Made list views editable and some fields optional - Added decorations, default filters, and stat buttons - Covers CHAPTER 11

mash-odoo requested changes Jan 16, 2026

View reviewed changes

jakan-odoo added 8 commits January 16, 2026 17:53

[IMP] estate: apply python, model, and view inheritance

54f03a6

- Used Python inheritance to extend existing logic - Applied model inheritance to add fields and behavior - Used view inheritance to update and extend UI - Covers CHAPTER 12

[ADD] estate: add translations, constraints, and UI updates

cc37406

- Added translatable strings for the module - Updated constraint names for clarity - Applied small user interface changes - Added archived filter for records

[IMP] estate_account: integrate estate with accounting

50ec57f

- Created new estate_account module - Linked estate module with account module - Added invoice creation for sold properties - Covers CHAPTER 13

[IMP] estate: add investor profile and compute unsold value

616598d

- Added investor profile linked to partner data - Deleting partner removes investor, investor delete keeps partner - Computed total unsold property value on res.partner - Sum based on expected price of non-sold properties

[IMP] estate: add kanban view and default grouping

5e71759

- Added a Kanban view for estate properties - Grouped properties by type by default - Covers CHAPTER 14

[ADD] awesome_owl: add props validation and counter sum logic

f8b317e

- Added props validation to Owl components - Implemented logic to calculate the sum of two counters CHAPTER 1

[ADD] awesome_owl: implement todo list with dynamic behavior

4e1415c

- Added a basic todo list component - Used dynamic attributes for state-based updates - Implemented event handler to add new todos CHAPTER 1

jakan-odoo changed the title ~~19.0 real estate tutorial jakan~~ [ADD] estate: implement core estate management features Jan 29, 2026

mash-odoo requested changes Jan 29, 2026

View reviewed changes

[ADD] estate: load default data on database creation

fd72a7b

- Added default properties, property types, tags, and offers - Automatically loads sample records when a new database is created - Helps users see estate records on first login

		from odoo import fields, models
		from dateutil.relativedelta import relativedelta

		<record id="estate_property_list_view" model="ir.ui.view">
		<field name="name">estate.property.list</field>

		<record id="estate_property_form_view" model="ir.ui.view">
		<field name="name">estate.property.form</field>

	'description': 'This module allows managing properties.',
	'description': "This module allows managing properties.",

		from dateutil.relativedelta import relativedelta
		from odoo import fields, models, api

	<button name="offer_accepted" type="object" string="Offer Accept" class="btn-primary"/>
	<button name="action_best_offer" type="object" string="Best Offer" class="btn-primary"/>

	<button name="maintenance_accept" type="object" string="Confirm" icon="fa-check"/>
	<button name="action_accept_maintenance" type="object" string="Confirm" icon="fa-check"/>


		i18n No newline at end of file

[ADD] estate: implement core estate management features #1109

Are you sure you want to change the base?

[ADD] estate: implement core estate management features #1109

Uh oh!

Conversation

jakan-odoo commented Jan 1, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

robodoo commented Jan 1, 2026

Uh oh!

mash-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!

mash-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!

mash-odoo left a comment

Choose a reason for hiding this comment

Uh oh!

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Uh oh!

Choose a reason for hiding this comment

Uh oh!

mash-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!

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

jakan-odoo commented Jan 1, 2026 •

edited

Loading