Add Estate Property Model by radhr-odoo · Pull Request #1229 · odoo/tutorials

radhr-odoo · 2026-04-03T13:01:14Z

Created the estate.property model with required fields and attributes, with the reference of crm_recurring_plan.
Chapters 1 to 3 completed, and the Estate module has been created with the estate_property model.

Changes

Added estate.property model
Defined fields and attributes

Added a new estate module, enabled it as an application, and configured it to be installable.

Add estate property model with necessary fields and attribute definitions, referencing crm_recurring_plan

robodoo · 2026-04-03T13:01:17Z

Added id.model.access.csv added to security folder in estate module. Given read, write, update and unlink option.

Added security to module by given read, write, update and unlink permission on given module

Added simple window action estate view in views folder with proper model and structure

Added root menu, first level menu and action menus in estate module

Improved by adding state and active field which set the record visibility and with no duplication of state.

In estate property module list view added using estate_property_view xml file by using list tags

In estate property module form view added using estate_property_view xml file by using sheet and pages tags. It also contains HTML tags

bit-odoo

Hello @radhr-odoo
Good Start!

Module name is wrong in these commits 534af8a , ed52d4e , d329065, 646f8a0

At the end of the commit message, please mention which chapter's code you pushed in that commit.

Thanks

bit-odoo · 2026-04-08T06:25:21Z

estate/views/estate_menu.xml

@@ -0,0 +1,9 @@
+<odoo>
+    <!-- Here id = unique id in DB, name = "what will be shown on screen" -->


Writing a comment is good, but no need to write a comment here. It's only required when there is complex computation, etc.

bit-odoo · 2026-04-08T06:25:41Z

estate/models/estate_property.py

+    garden_area = fields.Integer(string="Garden_area")
+    garden_orientation = fields.Selection(string="Garden Orientation", selection=[("north", "North"), ("east", "East"), ("west", "West"), ("south", "South")])
+
+    # If it is false then newly created record won't be appear. but record is created when active is set true record will appear.


Writing a comment is good, but no need to write a comment here. It's only required when there is complex computation, etc.

bit-odoo · 2026-04-08T06:25:52Z

estate/models/estate_property.py

+
+    # If it is false then newly created record won't be appear. but record is created when active is set true record will appear.
+    active = fields.Boolean("Active", default=True)
+    # State can get selected and as copy is set False in duplicate it cannot get copied


Writing a comment is good, but no need to write a comment here. It's only required when there is a complex computation, etc.

bit-odoo · 2026-04-08T06:26:19Z

estate/models/estate_property.py

+    # If it is false then newly created record won't be appear. but record is created when active is set true record will appear.
+    active = fields.Boolean("Active", default=True)
+    # State can get selected and as copy is set False in duplicate it cannot get copied
+    state = fields.Selection(string="state", selection=[("new", "New"), ("offer received", "Offer Received"), ("accepted", "Accepted"), ("sold", "Sold"), ("cancelled", "Cancelled")], default="new", copy=False)


You can use Ruff to format this.

bit-odoo · 2026-04-08T06:27:00Z

estate/__manifest__.py

+    'application': True,
+    'data': [
+        'security/ir.model.access.csv',
+


unneccary space.

Added filter for state wise filtering and also added group by for postcode. chapter 6 : Basic Views

Linked 2 models estate_property and estate_property_type using Many2one function on property_id connected with estate.property.type, linked buyer with res.partner and sales person with res.user.

Model linked to get more clarity while using both models and share linked data. Chapter 7: Relation between model

Added property tags (Many2Many) to enhance property classification and flexibility. Enables users to quickly filter and identify properties based on features like cozy, renovated, etc.Improves searchability and overall user experience. Chapter 7: Relations between model : Many2many

Allows users to view and manage all buyer offers in one place, making it easier to compare prices and track offer status. Improves decision-making and overall property management experience. Chapter 7: Relations between model : One2many

Enables users to access and use estate management features directly within the system. Simplifies setup so users can quickly start managing property-related tasks without additional configuration. Chapter 1: Architecture Overview

Allows users to store and manage detailed property information in a structured way. Improves tracking of property-related activities by linking them with recurring plans, making workflows more organized and efficient. Chapter 2: A NEW MODEL

Enables users to maintain structured property records with all necessary details in one place. Improves workflow efficiency by connecting properties with suggestion from recurring plans for better tracking and management. Chapter 3: Model and some basic fields

Ensures users have appropriate access to estate data based on their roles. Improves data security and prevents unauthorized actions while allowing smooth and controlled interactions with the system. Chapter 4: Security : A brief introduction

Provides users with controlled access to perform necessary actions like viewing, editing, and deleting data. Ensures a secure and reliable experience by preventing unauthorized operations while maintaining usability. Chapter 4: Security : A brief

Allows users to easily access and navigate estate data through a dedicated interface. Improves usability by providing a clear and structured view for managing records. Chapter 5: Finally some UI to play with.