[ADD] real_estate: Create New Module #1098

rugot-odoo · 2026-01-01T09:10:51Z

Complete Chapters 1–6 of Odoo tutorial

Architecture Overview
Create new application
Define models and basic fields
Security access rules
Add menus and actions
UI elements (list, form, search views)

robodoo · 2026-01-01T09:10:53Z

mash-odoo · 2026-01-01T09:21:20Z

Hello @rugot-odoo
For this PR, we only need the changes related to the real_estate module.
Could you please remove the extra files (like .idea and other unrelated diffs) and keep the commit limited to the module scope?

1. Architecture Overview 2. Create new application 3. Define models and basic fields 4. Security access rules 5. Add menus and actions 6. UI elements (list, form, search views) [ADD] real_estate: complete Chapters 1–6 of Odoo tutorial 1. Architecture Overview 2. Create new application 3. Define models and basic fields 4. Security access rules 5. Add menus and actions 6. UI elements (list, form, search views) [ADD] real_estate: complete Chapters 1–6 of Odoo tutorial 1. Architecture Overview 2. Create new application 3. Define models and basic fields 4. Security access rules 5. Add menus and actions 6. UI elements (list, form, search views) [FIX] real_estate: delete idea folder

rugot-odoo · 2026-01-01T10:03:47Z

Hello @mash-odoo
I’ve cleaned up the PR by removing all unrelated files (including .idea)

…onships Implement the property offers and tags model - Connected offers and tags with the main model - Completed relational field concepts as per the document

mash-odoo

Hello @rugot-odoo,
Good Work on the PR.
Please view my comments and apply the changes wherever needed.

real_estate/__manifest__.py

real_estate/models/real_estate_properties_model.py

real_estate/security/ir.model.access.csv

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

real_estate/views/properties_views.xml

@@ -0,0 +1,114 @@
+<odoo>
+    <data>


I noticed the <data> tag here, what was the reason for adding it?

Here, the tag is not required. However, it is useful when we want to control updates for a specific block of code. By using the tag with the noupdate attribute, we can prevent Odoo from updating that particular data during module upgrades or not

real_estate/views/properties_views.xml

real_estate/views/real_estate_properties_offer.xml

- Implemented @api.onchange methods - Added @api.depends for computed fields - Defined ondelete behavior to handle related record deletion safely

…onships Implement the property offers and tags model - Connected offers and tags with the main model - Completed relational field concepts as per the document

- Implemented @api.onchange methods - Added @api.depends for computed fields - Defined ondelete behavior to handle related record deletion safely

- Completed Unit 9 actions and business logic - Added property type field

- Added SQL constraints for data integrity - Implemented Python constraints - Configured statusbar widget in form views - Added inline list views for One2many fields

mash-odoo

Hello,
Good going on the PR,
Here are a few suggestions..

mash-odoo · 2026-01-09T06:17:39Z

real_estate/views/real_estate_properties_views.xml

+                        class="btn-secondary"
+                    />
+                    <field name="stage" widget="statusbar"
+                           options="{'clickable': False}"


What if this option is not written?

The statusbar is read-only by default, so it is not clickable even if the option is omitted.
The clickable: False is added only for clarity, is not strictly required
If we want users to change the state manually from the UI, we can explicitly enable it using clickable: 1.

mash-odoo · 2026-01-09T06:18:23Z

real_estate/models/real_estate_property_type.py

+        string='Properties'
+    )
+    _unique_type_name = models.Constraint(
+        'UNIQUE(name)',


Will this work for all the cases or is there any drawback?

This will work, but there is one drawback.
The UNIQUE(name) constraint is case-sensitive, so values like "House" and "house" would still be allowed.

mash-odoo · 2026-01-09T06:19:58Z

real_estate/views/real_estate_properties_views.xml

+                            <field name="date_availability"/>
+                            <field name="living_area"/>
+                            <field name="garden_area"/>
+                            <field name="total_area" readonly="1"/>


Do you think readonly is required here?

No, The attribute was added by mistake.
total_area is a computed field, which is already read-only by default.

mash-odoo · 2026-01-09T07:10:36Z

real_estate/models/real_estate_properties.py

+    @api.ondelete(at_uninstall=False)
+    def _unlink_if_accepted_offer(self):
+        for record in self:
+            for offer in record.offer_ids:
+                if offer.status == 'accepted':
+                    raise UserError("Can't delete an active record!")


Can you optimize this?

Yes, this can be optimized.
Instead of looping through all offers, we can directly filter the related recordset using filtered_domain.

@api.ondelete(at_uninstall=False)
def _unlink_if_accepted_offer(self):
if self.offer_ids.filtered_domain([('status', '=', 'accepted')]):
raise UserError("Can't delete an active record!")

real_estate/security/ir.model.access.csv

real_estate/views/real_estate_properties_views.xml

mash-odoo · 2026-01-09T08:45:38Z

real_estate/views/real_estate_properties_views.xml

+                    domain="['|','&amp;',('garden_orientation', '=' , 'north'),
+                    ('garden_orientation', '=' , 'south'),
+                    ('name', '=' , 'test')]"
+                />


As garden_orientation is a selection field, this AND condition won’t ever match.
Should this be an OR?

Got it.
The & was added for testing; this should be an OR condition.
You’re right, since garden_orientation is a selection field, it can’t be both values at the same time.

mash-odoo · 2026-01-09T08:54:40Z

real_estate/models/real_estate_property_offer.py

+    def action_accept(self):
+        # accepted_offer = self.search([
+        #     ('property_id', '=', self.property_id.id),
+        #     ('status', '=', 'accepted')
+        # ], limit=1)
+        # accepted_offer = self.property_id.offer_ids.filtered(
+        #     lambda o: o.status == 'accepted'
+        # )
+        accepted_offer = self.property_id.offer_ids.filtered_domain([
+            ('status', '=', 'accepted')
+        ])
+        if accepted_offer:
+            raise UserError(
+                "Only one offer can be accepted for a property."
+            )
+        self.status = 'accepted'
+        self.property_id.selling_price = self.price
+        self.property_id.stage = 'sold'
+        self.property_id.buyer_id = self.partner_id.id


Can try to make this more optimized?

Yes, this can be optimized.
Instead of assigning each field individually, we can update the related property in a single write() call.

self.property_id.write({
'selling_price': self.price,
'stage': 'sold',
'buyer_id': self.partner_id.id,
})

rugot-odoo marked this pull request as draft January 1, 2026 09:13

rugot-odoo force-pushed the 19.0-tutorial-rugot branch from fab8839 to 19545d8 Compare January 1, 2026 09:52

[FIX] real_estate : Delete .idea directory

b30b91c

rugot-odoo added 2 commits January 2, 2026 11:29

[FIX] real_estate: Implement many2one, one2many, and many2many relati…

f0334f2

…onships Implement the property offers and tags model - Connected offers and tags with the main model - Completed relational field concepts as per the document

[ADD] real_estate: Implement many2one, one2many, and many2many relati…

967fd9a

…onships Implement the property offers and tags model - Connected offers and tags with the main model - Completed relational field concepts as per the document

rugot-odoo changed the title ~~19.0 tutorial rugot~~ [ADD] real_estate: Create New Module Jan 2, 2026

mash-odoo requested changes Jan 2, 2026

View reviewed changes

rugot-odoo added 4 commits January 5, 2026 18:46

[ADD] real_estate: complete onchange, depends and ondelete decorators

fe80498

- Implemented @api.onchange methods - Added @api.depends for computed fields - Defined ondelete behavior to handle related record deletion safely

[ADD] real_estate: Implement many2one, one2many, and many2many relati…

e725c5f

…onships Implement the property offers and tags model - Connected offers and tags with the main model - Completed relational field concepts as per the document

[ADD] real_estate: complete onchange, depends and ondelete decorators

828453e

- Implemented @api.onchange methods - Added @api.depends for computed fields - Defined ondelete behavior to handle related record deletion safely

[ADD] real_estate: add actions, business logic, and property type

b5296de

- Completed Unit 9 actions and business logic - Added property type field

rugot-odoo force-pushed the 19.0-tutorial-rugot branch 2 times, most recently from bd2ac7b to 2b5dd2e Compare January 7, 2026 15:48

[ADD] real_estate: constraints, statusbar widget, and inline list views

fedc96f

- Added SQL constraints for data integrity - Implemented Python constraints - Configured statusbar widget in form views - Added inline list views for One2many fields

rugot-odoo force-pushed the 19.0-tutorial-rugot branch from 2b5dd2e to fedc96f Compare January 7, 2026 16:21

mash-odoo requested changes Jan 9, 2026

View reviewed changes

[ADD] real_estate: Create New Module #1098

Are you sure you want to change the base?

[ADD] real_estate: Create New Module #1098

Uh oh!

Conversation

rugot-odoo commented Jan 1, 2026

Uh oh!

robodoo commented Jan 1, 2026

Uh oh!

mash-odoo commented Jan 1, 2026

Uh oh!

rugot-odoo commented Jan 1, 2026

Uh oh!

mash-odoo left a comment

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!

Choose a reason for hiding this comment

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

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!

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

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!

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

rugot-odoo Jan 9, 2026 •

edited

Loading