19.0 tutorials mrgor by mrgor-odoo · Pull Request #1362 · odoo/tutorials

mrgor-odoo · 2026-07-03T12:49:36Z

No description provided.

Initialize the estate module by adding the required module configuration files. This establishes the basic structure needed for future development and allows Odoo to recognize the module.

robodoo · 2026-07-03T12:49:39Z

Initialize the estate module by adding the required module configuration files. This establishes the basic structure needed for future development and allows Odoo to recognize the module.

Create the basic property model for the Real Estate module. This model allows storing essential property information and provides the base structure for adding more features. task = chapter 3 completed

Newly created models are inaccessible by default in Odoo. Define access rights so Internal Users can interact with the estate.property model and remove the missing access rules warning. Task Completed chapter 4

- Allow users to access and manage property records from the UI. - Improve data consistency by protecting important field values. - Prevent unwanted data from being copied to duplicate records. - Reduce manual work by providing default field values. - Prepare the property model for future business workflows by introducing state fields. Task Completed chapter 5

The default generated views are not suitable for a business application. A custom UI is required to improve data organization and allow users to efficiently manage and search property records as the application grows. Task Completed chapter 6

Introduce a dedicated property type model to improve how properties are organized and managed within the application. - Centralize the management of property types - Allow properties to be assigned reusable categories - Improve the user experience when organizing listings - Simplify property organization and maintenance

Improve property management by introducing buyer and salesperson relationships together with reusable property tags. Associate properties with buyers and salespersons, automatically assign the current user as the default salesperson, prevent buyer information from being copied during duplication, and introduce the Property Tag model with its views, menu, action, access rights, and a many2many relationship for assigning multiple tags to properties.

Allow properties to track offers from potential buyers without requiring a dedicated menu, keeping offer management within the property workflow. Introduce the Property Offer model with its views and access rights, link offers to properties through a many2one relationship, and expose them on the property form using a one2many field. Task Completed chapter 7

mash-odoo

Hello,
Good start on the task..
Here are a few comments and suggestions.. 🐣
Also please change your PR title and description!!

mash-odoo · 2026-07-28T08:32:15Z

+    _description = "Real Estate Property"
+    name = fields.Char(required=True)


Suggested change

_description = "Real Estate Property"

name = fields.Char(required=True)

_description = "Real Estate Property"

name = fields.Char(required=True)

mash-odoo · 2026-07-29T12:08:10Z

+
+
+class EstateProperty(models.Model):
+    _name = "estate.property"


Suggested change

_name = "estate.property"

_name = 'estate.property'

wrap the technical strings in single quotes and the strings which appear on UI and visible to customer in double quotes

mash-odoo · 2026-07-29T12:08:45Z

+    active = fields.Boolean(default=True)
+    state = fields.Selection(


Arrange all the fields alphabetically so that it's easier to locate it later

mash-odoo · 2026-07-29T12:09:11Z

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


Suggested change

selection=[

("north", "North"),

("south", "South"),

("east", "East"),

("west", "West"),

]

selection=[

('north', "North"),

('south', "South"),

('east', "East"),

('west', "West"),

]

mash-odoo · 2026-07-29T12:10:08Z

+    property_type_id = fields.Many2one("estate.property.type", string="Property Type")
+    buyer_id = fields.Many2one("res.partner", string="Buyer", copy=False)
+    salesperson_id = fields.Many2one(
+        "res.users", string="Salesperson", default=lambda self: self.env.user


Why do we need to use here lambda function?
Do we have any other approach here?

I used a lambda because the logic is only one line, so it keeps the code short and readable. Another approach would be to define a method like _default_salesperson() that returns self.env.user and use that method as the default. Both work, but I felt lambda was simpler here.

mash-odoo · 2026-07-29T12:13:36Z

+{
+    "name": "Real Estate",
+    "version": "1.0",
+    "author": "Mrunmayee",


When you are working for a company, you should keep the author name as Odoo S.A. or just skip writing it.

mash-odoo · 2026-07-29T12:13:50Z

+    "name": "Real Estate",
+    "version": "1.0",
+    "author": "Mrunmayee",
+    "depends": ["base"],


What's the purpose of depends?

depends specifies which modules my module relies on. Odoo uses it to ensure those modules are installed and loaded before installing or upgrading my module. In this case, I added base because my module uses the core Odoo framework, such as models.Model, field types, and models like res.users and res.partner.

mash-odoo · 2026-08-05T06:54:10Z

+    description = fields.Text()
+    postcode = fields.Char()
+    date_availability = fields.Date(
+        copy=False, default=lambda self: fields.Date.add(fields.Date.today(), months=3)


Can this be done in any other way?

Yes, another approach is to create a separate method, for example _default_date_availability(), which returns the default date, and then pass that method to default.

mash-odoo · 2026-08-05T06:54:55Z

+        "res.users", string="Salesperson", 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="Offers")


Where can I find the records of offers connected to a property?

The offers are stored in the estate.property.offer table. They are connected to a property using the property_id field. When I access offer_ids, Odoo automatically fetches all offer records whose property_id matches the current property.

mash-odoo · 2026-08-05T06:55:45Z

+                <filter
+                    string="Postcode"
+                    name="group_postcode"
+                    context="{'group_by':'postcode'}"/>


WDYM by context?

context passes extra information to Odoo. In this case, it tells Odoo to group the records by postcode.

- Follow Odoo coding conventions for string quoting - Reorder model fields alphabetically - Improve code consistency and readability - Apply requested review changes

The property total area should be derived automatically to ensure data consistency and avoid manual calculation. Added a computed field that calculates the total area from the living area and garden area, and displayed it in the property form view.

The property best offer should be computed automatically from the related offers to ensure it always reflects the highest available offer. Added the computed `best_price` field using the related `offer_ids.price` dependency and displayed it in the property form view.

[ADD] estate: 'add new modules'

607f91d

Initialize the estate module by adding the required module configuration files. This establishes the basic structure needed for future development and allows Odoo to recognize the module.

mrgor-odoo assigned mash-odoo Jul 3, 2026

[ADD] estate: 'add new modules'

ce43cf1

Initialize the estate module by adding the required module configuration files. This establishes the basic structure needed for future development and allows Odoo to recognize the module.

mrgor-odoo force-pushed the 19.0-tutorials-mrgor branch from 2c55e50 to ce43cf1 Compare July 3, 2026 13:12

[ADD] estate: create property model

7f8c9e9

Create the basic property model for the Real Estate module. This model allows storing essential property information and provides the base structure for adding more features. task = chapter 3 completed

mrgor-odoo force-pushed the 19.0-tutorials-mrgor branch 2 times, most recently from 8a0d18c to 4f1eeb0 Compare July 7, 2026 11:46

[ADD] estate: add access rights for estate.property

a9cc58d

Newly created models are inaccessible by default in Odoo. Define access rights so Internal Users can interact with the estate.property model and remove the missing access rules warning. Task Completed chapter 4

mrgor-odoo force-pushed the 19.0-tutorials-mrgor branch from 4f1eeb0 to a9cc58d Compare July 7, 2026 11:47

mrgor-odoo force-pushed the 19.0-tutorials-mrgor branch from 3113f4d to 707c862 Compare July 10, 2026 13:29

[IMP] estate: add basic property views

dfadfd1

The default generated views are not suitable for a business application. A custom UI is required to improve data organization and allow users to efficiently manage and search property records as the application grows. Task Completed chapter 6

mrgor-odoo force-pushed the 19.0-tutorials-mrgor branch 2 times, most recently from 6e79df5 to 904ee8f Compare July 28, 2026 11:18

mrgor-odoo force-pushed the 19.0-tutorials-mrgor branch 4 times, most recently from 9638607 to 56faa55 Compare July 30, 2026 13:29

mrgor-odoo force-pushed the 19.0-tutorials-mrgor branch 3 times, most recently from b36d639 to 32d3417 Compare July 31, 2026 11:35

mrgor-odoo force-pushed the 19.0-tutorials-mrgor branch from 32d3417 to dfdf6ed Compare July 31, 2026 11:39

mash-odoo requested changes Aug 5, 2026

View reviewed changes

[IMP] estate: address review comments

a96ee70

- Follow Odoo coding conventions for string quoting - Reorder model fields alphabetically - Improve code consistency and readability - Apply requested review changes

mrgor-odoo force-pushed the 19.0-tutorials-mrgor branch from 56cd7e0 to a96ee70 Compare August 5, 2026 11:48

[ADD] estate: compute total area

8a32018

The property total area should be derived automatically to ensure data consistency and avoid manual calculation. Added a computed field that calculates the total area from the living area and garden area, and displayed it in the property form view.

		_description = "Real Estate Property"
		name = fields.Char(required=True)



		class EstateProperty(models.Model):
		_name = "estate.property"

		active = fields.Boolean(default=True)
		state = fields.Selection(

Uh oh!

Conversation

mrgor-odoo commented Jul 3, 2026

Uh oh!

robodoo commented Jul 3, 2026

Uh oh!

mash-odoo left a comment • 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!

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

mash-odoo left a comment •

edited

Loading