-
Dear, I hope you are fine. The complete log output, got it from running OpenUpgrade 14to15, is in attach, I also query into my DB sigmaBEdb.tmp and I checked inside the table hr_employee. Any idea on how to resolve this issue, it would be greatly appreciated. 2024-10-21 08:17:07,628 119563 ERROR sigmaBEdb.tmp odoo.sql_db: bad query: INSERT INTO "hr_employee" ("id", "active", "address_home_id", "address_id", "certificate", "color", "company_id", "create_date", "create_uid", "department_id", "employee_type", "marital", "name", "resource_calendar_id", "resource_id", "user_id", "work_email", "work_permit_scheduled_activity", "write_date", "write_uid") VALUES (nextval('hr_employee_id_seq'), true, 54, 1, 'other', 0, 1, '2024-10-21 08:17:05.011787', 1, 1, 'employee', 'single', 'Gabriele', 3, 54, 2, '[email protected]', false, '2024-10-21 08:17:05.011787', 1) RETURNING id |
Beta Was this translation helpful? Give feedback.
Replies: 2 comments
-
well pretty much what the error message says: It tries to create an employee with the admin user as user, but you seem to already have such an employee with a different or no xmlid. Probably you deleted the employee that v14 created for the admin user, and then created a new employee with the admin user as user some time afterwards. (same error should happen if you say Easiest way to fix your data is to create an xmlid |
Beta Was this translation helpful? Give feedback.
-
Hello @hbrunn I just wish to thank for your fast response and share my solution inspired from your reply: with "developer mode" look for the Employee (with name Gabriele) and change its XML ID. The 2 pictures shows what I did , without write into hr_data.xml, this modification let me |
Beta Was this translation helpful? Give feedback.
well pretty much what the error message says: It tries to create an employee with the admin user as user, but you seem to already have such an employee with a different or no xmlid.
Probably you deleted the employee that v14 created for the admin user, and then created a new employee with the admin user as user some time afterwards. (same error should happen if you say
-i hr
in you v14 installation)Easiest way to fix your data is to create an xmlid
hr.employee_admin
pointing to your employee that has the admin user as user.