Contributors mailing list archives
Re: Compute and Onchange after createby
DIXMIT Consulting SLU, Enric Tobella Alomar
Onchange might be hard to manage. I would recomend you to use a compute with store=True and readonly=False. This kind of fields are editable, and you can allways add the change there. In order to ensure the execution inside the ORM you just need to use the flush method.
El vie, 4 ago 2023 a las 16:42, Graeme Gellatly (<firstname.lastname@example.org>) escribió:
The only truly reliable ways for onchanges is the tests.Form class or an OCA module onchange_helper (something like that). But Form is dog slow, like 2 or 3 seconds sometimes and onchange_helper has its oddities too. For these new writable computed fields, my belief is that was kind of the point. Not the computation per se, but the very fact it has an inverse argument so in theory, both the computation and if written the inverse would be called. But tbh, I find them much harder to work with.On Sat, Aug 5, 2023 at 2:28 AM Fernando La Chica <email@example.com> wrote:I am building an API in Odoo 16.0. As we know, there are fields that can be computed (compute) and others that change their value (onchange) depending on the change in another one. Well, what I need to know is if there is a standard way for after creating the object ("model.create") to launch all these computations without having to worry about calling these methods
Enric Tobella Alomar
CEO & Founder