odoo / technical-training-solutions

Odoo

Odoo is a suite of web based open source business apps.

The main Odoo Apps include an Open Source CRM, Website Builder, eCommerce, Warehouse Management, Project Management, Billing & Accounting, Point of Sale, Human Resources, Marketing, Manufacturing, ...

Odoo Apps can be used as stand-alone applications, but they also integrate seamlessly so you get a full-featured Open Source ERP when you install several Apps.

Getting started with Odoo

For a standard installation please follow the Setup instructions from the documentation.

To learn the software, we recommend the Odoo eLearning, or Scale-up, the business game. Developers can start with the developer tutorials

technical-training-solutions's Issues

best practices - avoid delegate

@sts-odoo
Could we remove this? We're teaching employees and partners to use the delegate keyword, which is despised by the R&D because:

• it is too discrete (good luck noticing a delegate true among 35 fields compared to noticing an inherits declaration)
• it is unclear what happens if more than one delegate is present (e.g. delegate true on 2 models with a name field: which name will be read? I assume it's the one from the first field with the delegate true, but i honestly have no clue. I know this is a chtarbé use-case but it is present in sale_coupon)

Could we switch to inherits instead pleaz?

Also, do a grep for delegate=True : 3 results
inherits: 100+ results -_-

cc @Feyensv

technical-training-solutions/library/models/book.py

Line 24 in 5df059e

book_id = fields.Many2one('library.book', string="Book", required=True, ondelete="cascade", delegate=True)

Possible error in estate.property.offer:action_accept

technical-training-solutions/estate/models/estate_property_offer.py

Lines 85 to 91 in a3b24b6

	return self.mapped("property_id").write(
	{
	"state": "offer_accepted",
	"selling_price": self.price,
	"buyer_id": self.partner_id.id,
	}
	)

If you are accepting several offers at once, won't this code set the buyer_id and selling_price of the first offer of the record_set to all the corresponding properties, even those whose accepted offer is from a different buyer_id and/or at a different selling_price?

Solution gives a Many2many where tutorial asks for a One2many

technical-training-solutions/estate/models/estate_property_type.py

Line 28 in a3b24b6

offer_ids = fields.Many2many("estate.property.offer", string="Offers", compute="_compute_offer")

This field is defined as a Many2many; however the tutorial specifies it as follows:

Add the field offer_ids on estate.property.type which is the One2many inverse of the field defined at the previous step.