- Mailing Lists
- Contributors
- Re: XML errors when upgrading modules, because of fields in unrelated modules
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
Re: XML errors when upgrading modules, because of fields in unrelated modules
Re: XML errors when upgrading modules, because of fields in unrelated modules
Re: XML errors when upgrading modules, because of fields in unrelated modules
Hi Moises,
I haven't found this to be easy reproductible.
The particular case I encountered today went away after I ran a "-u base" (that I really din't like to do).
On your questions:
1) Yes, In this case both inherited from "base.view_company_form".
2) No (see 1)
3) No groups set on model on view
4) Yes. View on Module 1 does not have a default priority (16 was assigned) and View in Module 2 has priority=100. This looked good to me.
5) Yes, tons of them, between core addons and other OCA modules :-)
I can give it a try at stripping the modules down and reproducing.
Thanks Moises
/Daniel
On 25/11/22 14:22, Moises Lopez wrote:
Hi Daniel
I have a few question related to reproduce the case
1) Do The third view is inherited from original one?
1. id=original2. id=inh_a inherit=original3. id=inh_b inherit=original
--2) Do The third view is inherited from 2nd one?
1. id=original2. id=inh_a inherit=original3. id=inh_b inherit=inh_a
3) Do the original field has "groups"?
4) Do the inherited views has "priority"?
5) Are there other views inheriting the same view?
Could you share the both modules with minimal code and the odoo-bin command to reproduce it, please?
Moisés López CalderónMobile: (+521) 477-752-22-30Twitter: @moylop260Twitter: @vauxoo_______________________________________________
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 DIRECTORM: +351 919 991 307
E: dreis@OpenSourceIntegrators.com
A: Avenida da República 3000, Estoril Office B, #34
_______________________________________________
Mailing-List: https://odoo-community.org/groups/contributors-15
Post to: mailto:contributors@odoo-community.org
Unsubscribe: https://odoo-community.org/groups?unsubscribe
by Michael Tietz - 07:20 - 25 Nov 2022
Reference
-
XML errors when upgrading modules, because of fields in unrelated modules
Hello,
I've been finding this weird issue for a while, but decided to take some tome to write about it.
I've seen frequently the case where:
1. A custom module adds a field to a model and view. For example. to res.company.
2. Later, another (unrelated) custom module also adds a new field to that same model (model and view).
When installing or upgrading that second module, I see errors loading the XML with the form view.
The error says that the field added by module 1 is missing in the view.
But a) module 1 is installed an the field exists and b) the XML for the view in module 2 doesn't have any reference to that "missing" field!
I found this frequently in Odoo 14.
Honestly I'm not sure if it if also happens in other versions.
Has anyone else experienced this?
Thank you
--
DANIEL REIS
MANAGING DIRECTORM: +351 919 991 307
E: dreis@OpenSourceIntegrators.com
A: Avenida da República 3000, Estoril Office B, #34
by Daniel Reis - 02:30 - 25 Nov 2022


