Skip to Content
Meniu
Trebuie să fiți înregistrat pentru a interacționa cu comunitatea.
Această întrebare a fost marcată
2 Răspunsuri
1497 Vizualizări

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


Imagine profil
Abandonează
Cel mai bun răspuns

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

Imagine profil
Abandonează
Autor

Thank you, but I get a KeyError "invoice_id"

Autor

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.

Cel mai bun răspuns

One2many fields aren't actually stored on the database table

Imagine profil
Abandonează
Autor

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')

Autor

The wrong invoice is saved now, when I add INV...0012 to INV...003, INV...003 is saved.

Related Posts Răspunsuri Vizualizări Activitate
1
iul. 25
2432
2
iul. 25
7897
2
iul. 25
4304
2
iul. 25
4041
2
iun. 25
2658