Skip to Content
This question has been flagged
6 Replies
2775 Views
Avatar
Bruno gomez

hello,

First of all, thank you for helping the community and I hope you can help me. (I'm quite new, although I'm still studying)
I have been using Odoo in my business for almost two years with a version 14 community and some OCA module, which has worked correctly for me.
I have decided to update version 14 to 17, for which I have been able to update to version 15 and now I am updating to 16, always using OCA openupgrade.

My problem is that when migrating the database from v15 to v16 using the openupgrade-v16 script it shows me the following error:

2024-03-09 17:43:06,201 31738 DEBUG odoopsitec 
odoo.tools.convert: while parsing 
/opt/odoo/odoo/addons/product/views/res_partner_views.xml:3

La vista heredada no puede tener 'grupos' definidos en el registro. Use 
los atributos de 'grupos' dentro de la definición de la vista

I have reviewed the res_partner_views.xml file and its content is as follows: 

 
        res.partner.product.property.form.inherit
        res.partner
        
        
            
                
                

                    
Pricelists are managed on

I have made different modifications to this file without success. I have searched on Google and although I have not found much information, I have been able to investigate a possible solution, which has not worked for me and I always have this message in the migration.

Could you guide me?
Thank you so much


Avatar
Discard
Bruno gomez
Author

Good afternoon Cybrosys,

I appreciate your response, but it doesn't solve anything. It tells me some links to do the migration, when I am already doing the database migration and in the process I encounter an error.

I have already browsed Google and carried out dozens of tests, I am trying to find a solution to my specific problem.

I do not have custom modules or custom fields in the tables, so I do not understand why it shows me a view error and there are no instructions on how to correct it.

What would have to be done to correct the inherited view group?

Thank you very much in advance.
All the best

Avatar
kasra hosseinpourshad
Best Answer

could you solve it?? 

I faced SIMILAR ERROR WHILE I WAS TRYING TO UPGRADE MY PROJECT MODULE

RPC_ERROR

Odoo Server Error

Traceback (most recent call last):

  File "/usr/lib/python3/dist-packages/odoo/https://dnsp2.noorano.net/web/assets/2cccd8d/web.assets_web_dark.min.js:2888:13)

Avatar
Discard
Avatar
Lansana Barry Sow
Best Answer

Greetings,


I had the same error, but in the end I checked and saw that it was wrong with the versions of the modules commits. You have to update all the commits of all the modules including the Openupgrade to the latest commit of the repository.


Another thing I also realized is to work with a recent database without error, not with a database with a migration in the middle that gave an error.


I hope these tips can be helpful to you.

Avatar
Discard
Avatar
German
Best Answer

Hi Bruno,

Did you find the solution?

Avatar
Discard
Avatar
Cybrosys Techno Solutions Pvt.Ltd
Best Answer

Hi,

Please refer the below forum answer

https://www.odoo.com/sk_SK/forum/pomoc-1/odoo-15-to-odoo-16-migration-using-openupgrade-213907


Hope it helps


Avatar
Discard
Avatar
Bruno gomez
Author Best Answer

Good morning Alex,


Thank you very much for your response, what you mentioned is what indicates the error, I searched Google yesterday and found similar cases that indicated that change.


but how can I solve it?

but I have not changed the view and I have not made groups either.


This is the complete error

odoo.tools.convert.ParseError: while parsing /opt/odoo/odoo/addons/product/views/res_partner_views.xml:3
La vista heredada no puede tener 'grupos' definidos en el registro. Use los atributos de 'grupos' dentro de la definición de la vista

View error context:
'-no context-'


I have not modified the xml file res_partnet_views.xml, it is the original

greetings

Avatar
Discard
Nur Mubin

Hi Bruno, have you solved this issue? I got the same issue also when i try to upgrade from v15 to v17. It would be nice if you can share your experience related to this issue.

Thanks

Bruno gomez
Author

Good Nur,

If I could solve it and learn why it was happening, it was soooo simple. But certainly not thanks to the "odoo community", who on all occasions have dedicated themselves to repeating to me what the error said without further guidance.

So, I contacted a professional dedicated to odoo and I solved it.
Of course, what we have learned is that you should not depend on the odoo community and you must have professional support to have odoo and with this, it is best not to use the community and make use of the licensing system that already gives you support and upgrades. If not, it will be much more expensive.

I speak from my experience, each person finds their way.

All the best

Stéphan Sainléger

Hi Bruno!
I am encountering exactly the same issue on a migration from 15.0 to 16.0, and I feel the same frustration not finding any clue about the way to resolve it.
Would you mind sharing how you did solve this? It would be very helpful and improve the Odoo community capacity to assist each other :-)
Thanks
Best regards

Bruno gomez
Author

good morning stephan,

The important thing is to check which views have the group problem, as indicated by the error. To do this, in debug mode, go to the technical menu in settings and to the views option.

There create a custom filter that is "Groups" + "is established" and review these views, which are the ones that generate this error in the migration.

It worked for me to eliminate these views to be able to go from v14 to v15. In your case, review and try solutions.

If you can do it, it's ok, if not, I can give you the contact of a certified Odoo technician who helped me a lot.

Community: this is a helpful answer, what you do is translate and Google already does that.

All the best

Avatar
Alex Hathaway
Best Answer

As of version 16 groups cannot be defined in inheritance view. You will need to push the groups restriction down to the field or make it a base view

Avatar
Discard