-
-
Notifications
You must be signed in to change notification settings - Fork 702
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Migration 14.0 -> 15.0 Issue with Project, Tasks, timesheet, invoices #3604
Comments
The coverage of the modules with migration scripts is still low in the main branch, so the problems seems to be to migrate a DB with modules non covered. Please see such coverage in https://github.com/OCA/OpenUpgrade/blob/15.0/docsource/modules140-150.rst |
hey pedrobaeza, |
It seems there's a remaining domain with |
That´s what confuses me a bit... Checking the following now...
|
I confirm. |
hr_timesheet could also be the reason, maybe its missing here: #3306
|
The problem affects to the modules "project" & "timesheets" & Invoices
After upgrading a db from 14.0 to 15.0 i get the following problems.
relevant Result:
return field_cache[record._ids[0]]
KeyError: 11
odoo.exceptions.CacheMiss: 'project.project(11,).timesheet_count'
The above exception was the direct cause of the following exception:
ValueError: Invalid field project.project.allowed_internal_user_ids in leaf ('allowed_internal_user_ids', 'in', [6])
The same happens when trying to access the timesheet or the invoice view...
ValueError: Invalid field project.project.allowed_internal_user_ids in leaf ('allowed_internal_user_ids', 'in', [6])
Simply Updating the modules doesnt help..
In additipn... it seems like i do have a problem with the payment entries, as they dont seem to be linked to a payment method. Due to this i had to to delete all payments and unreconcile them before upgrading... Possible that this could lead to this behaviour? With the original data the logs tell me, that i have to define a payment method for my payments.... something is srewed up here...
Any hints for solving this would be highly appreciated
regards
Nils
The text was updated successfully, but these errors were encountered: