Odoo is the world's easiest all-in-one management software.
It includes hundreds of business apps:
I have a M2O relation to account.move on a custom model:
invoice_id = fields.Many2one('account.move', string="Related invoices", ondelete='cascade', store=True)
and a O2M relation from account.move to my custom model:
rel_invoices = fields.One2many('inv.relations', 'id', string='Related Invoices', store=True)
But when I try to add related invoices, they are not saved.
How can I fix this?
Thank you
Hi,
Can you try change field definition like below and check
rel_invoices = fields.One2many('inv.relations', 'invoice_id', string='Related Invoices', store=True)Hope it helps
Thank you, but I get a KeyError "invoice_id"
I don't have the KeyError anymore, but the wrong invoice is saved. When I add INV...0012 to INV...003, INV...003 is saved.
One2many fields aren't actually stored on the database table
Thank you, can u suggest a workaround?
you should set inverse_name as your many2one field in your custom module, don't add store ..
rel_invoices = fields.One2many(string='Related Invoices', comodel_name='inv.relations', inverse_name='invoice_id')
The wrong invoice is saved now, when I add INV...0012 to INV...003, INV...003 is saved.
Create an account today to enjoy exclusive features and engage with our awesome community!
Регистрация| Related Posts | Ответы | Просмотры | Активность | |
|---|---|---|---|---|
|
1
июл. 25
|
2473 | ||
|
2
июл. 25
|
7922 | ||
|
2
июл. 25
|
4346 | ||
|
2
июл. 25
|
4079 | ||
|
2
июн. 25
|
2671 |
1. Use the live chat to ask your questions.
2. The operator answers within a few minutes.
