- Mailing Lists
- Contributors
- Compute and Onchange after create
Archives
- By thread 1419
-
By date
- August 2019 59
- September 2019 118
- October 2019 165
- November 2019 97
- December 2019 35
- January 2020 58
- February 2020 204
- March 2020 121
- April 2020 172
- May 2020 50
- June 2020 158
- July 2020 85
- August 2020 94
- September 2020 193
- October 2020 277
- November 2020 100
- December 2020 159
- January 2021 38
- February 2021 87
- March 2021 146
- April 2021 73
- May 2021 90
- June 2021 86
- July 2021 123
- August 2021 50
- September 2021 68
- October 2021 66
- November 2021 74
- December 2021 75
- January 2022 98
- February 2022 77
- March 2022 68
- April 2022 31
- May 2022 59
- June 2022 87
- July 2022 141
- August 2022 38
- September 2022 73
- October 2022 152
- November 2022 39
- December 2022 50
- January 2023 93
- February 2023 49
- March 2023 106
- April 2023 47
- May 2023 69
- June 2023 92
- July 2023 64
- August 2023 103
- September 2023 91
- October 2023 101
- November 2023 94
- December 2023 46
- January 2024 75
- February 2024 79
- March 2024 104
- April 2024 63
- May 2024 40
- June 2024 160
- July 2024 80
- August 2024 70
- September 2024 62
- October 2024 121
- November 2024 117
- December 2024 89
- January 2025 59
- February 2025 104
- March 2025 96
- April 2025 107
- May 2025 52
- June 2025 72
- July 2025 60
- August 2025 81
- September 2025 124
- October 2025 63
- November 2025 22
Contributors
Compute and Onchange after create
by Fernando La Chica - 04:26 - 4 Aug 2023
Follow-Ups
-
Re: Compute and Onchange after create
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.Kind regards,El vie, 4 ago 2023 a las 16:42, Graeme Gellatly (<notifications@odoo-community.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 <notifications@odoo-community.org> 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_______________________________________________
Mailing-List: https://odoo-community.org/groups/contributors-15
Post to: mailto:contributors@odoo-community.org
Unsubscribe: https://odoo-community.org/groups?unsubscribe
_______________________________________________
Mailing-List: https://odoo-community.org/groups/contributors-15
Post to: mailto:contributors@odoo-community.org
Unsubscribe: https://odoo-community.org/groups?unsubscribe
--Enric Tobella AlomarCEO & Founder
by Enric Tobella Alomar - 04:47 - 4 Aug 2023 -
Re: Compute and Onchange after create
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 <notifications@odoo-community.org> 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_______________________________________________
Mailing-List: https://odoo-community.org/groups/contributors-15
Post to: mailto:contributors@odoo-community.org
Unsubscribe: https://odoo-community.org/groups?unsubscribe
by Graeme Gellatly - 04:42 - 4 Aug 2023 -
Re: Compute and Onchange after create
What I usually do is to create a specific method to be used by the API.
It will create the record and then call the relevant onchanges.
I find that often there is more than that, and this pattern is convenient:
You may also need to set some sane defaults, run specific checks, do some data conversion cleaning, or even some automation.
On 04/08/2023 15:28, Fernando La Chica 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_______________________________________________
Mailing-List: https://odoo-community.org/groups/contributors-15
Post to: mailto:contributors@odoo-community.org
Unsubscribe: https://odoo-community.org/groups?unsubscribe
--
DANIEL REIS
MANAGING PARTNERM: +351 919 991 307
E: dreis@OpenSourceIntegrators.com
A: Avenida da República 3000, Estoril Office B, 3º Escr.34, 2649-517 Cascais
by Daniel Reis - 04:35 - 4 Aug 2023