[ADD] estate: estate_property model added#1151
Draft
maram-odoo wants to merge 9 commits intoodoo:19.0from
Draft
Conversation
|
|
maram-odoo
force-pushed
the
19.0-real-estate-tutorial-maram
branch
2 times, most recently
from
e4df9e5 to
db23fc9
Compare
Chapter 4: Security - A Brief Introduction This commit adds proper access control for the `estate.property` model by introducing an entry in `ir.model.access.csv`.
maram-odoo
force-pushed
the
19.0-real-estate-tutorial-maram
branch
3 times, most recently
from
ba36ffb to
da3ebde
Compare
Chapter 5 and 7:UI to play and Relations Between Models added window action and menuitem for estate_property to make visible app in apps section added form view and list view because the default view is never acceptable for a business application relational field are added like property offer, property tag,property tag and their model and views are created and added in security file.
Chapter 5: Finally, Some UI To Play With 1-previously at availability date field python built-in date.today function was added but its odoo has its own Date.today function so added it and fixed that 2-default search filter and default group by is introduced in estate property view
Chapter 5: Finally, Some UI To Play With 1-removed unnecessary imports and depends(crm)
bit-odoo
reviewed
Feb 10, 2026
bit-odoo
left a comment
bit-odoo
left a comment
There was a problem hiding this comment.
Hello @maram-odoo
Great work!
Can you please improve all your commit message titles and PR title accroding to guidelines?
Thanks
estate/models/estate_property.py
Outdated
Comment on lines
1
to
2
| from odoo import fields, models | ||
| from datetime import timedelta |
There was a problem hiding this comment.
Please read this coding guidelines documentation https://www.odoo.com/documentation/19.0/contributing/development/coding_guidelines.html#imports
estate/views/estate_menus.xml
Outdated
| action="estate_property_type_action" /> | ||
| </menuitem> | ||
| </menuitem> | ||
| </odoo> No newline at end of file |
| </form> | ||
| </field> | ||
| </record> | ||
| </odoo> No newline at end of file |
| <field name="res_model">estate.property.tag</field> | ||
| <field name="view_mode">list,form</field> | ||
| </record> | ||
| </odoo> No newline at end of file |
| </list> | ||
| </field> | ||
| </record> | ||
| <record id="estate_property_tag_view_form" model="ir.ui.view"> |
There was a problem hiding this comment.
Leave one space before it for better readability.
maram-odoo
force-pushed
the
19.0-real-estate-tutorial-maram
branch
2 times, most recently
from
617c590 to
78a890c
Compare
…and filter improved Chapter 8: Computed Fields And Onchanges computed field like total area added and according method is added for calculating total area by adding living area and garden area. same best offer field added that automatically assign max offer price from all recived offer. some filter and group by added and styling and readability is improved.
maram-odoo
force-pushed
the
19.0-real-estate-tutorial-maram
branch
from
78a890c to
e390172
Compare
Chapter 8: Computed Fields And Onchanges inverse method implemented for computed field validity and date_deadline by help of timedelta and fields Date today method
maram-odoo
force-pushed
the
19.0-real-estate-tutorial-maram
branch
from
ea66837 to
b12a4f3
Compare
…methods Chapter 8: Computed Fields And Onchanges fixed date_availability default value 3-months by relativedelta instead of time delta because timedelta only calculates days but we need months. fixed compute method and inverse method for date deadline by using create date or today date,because if it is only today date than it will again recompile if we change validity. onchange decorator introduce in garden field to auto filling value of garden area and garden Orientation.
…eption handling Chapter 9: Ready For Some Action? Added the buttons ‘Cancel’ and ‘Sold’ to the estate.property model. A cancelled property cannot be set as sold, and a sold property cannot be cancelled by help of usererror. Added the buttons ‘Accept’ and ‘Refuse’ to the estate.property.offer model. When an offer is accepted, selling price automatically set as offer price for the corresponding property. also added the security rights and groups for estate property.
…er accepted Chapter 9: Ready For Some Action? added return to all button methods also aded functionality to setting buyer after offer accepted
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
[ADD] estate: estate_property model added
In the estate_property.py file, a new class EstateProperty is created to manage real estate properties in Odoo. It inherits from models.Model. The model is identified by _name = "estate.property".
The class includes fields such as name, postcode, and date_availability. It also has price-related fields like expected_price and selling_price. Property details are stored using fields like bedrooms, living_area, and facades. The garage and garden fields indicate whether these features exist, while garden_area and garden_orientation(selection field) store additional garden details.