[16.0][account] Missing field and field information for account #4281
Labels
Comments
|
Are there any new findings on this? We would like to upgrade our odoo15, but we are failing at the same point with our production instance as with the fresh installation described above. |
|
What is the state of the module account_payment ? |
|
What do you mean by "state of the module"? Where can I check this? The only thing I can find is an In addition, I cannot find the fields mentioned in the error messages ( |
|
amount_available_for_refund in in account in 15.0 |
|
First of all, "account" was installed in 15.0 and "account_payment" was uninstalled. After an update to 16.0, the state for "account_payment" remained uninstalled, although auto_install was set to true. I then installed this in the odoo15 installation and updated to odoo16 again. Then the state here is "installed" and the error messages no longer appear. I wasn't aware that another module had to be installed tor run the upgrade successfully. Although an upgrade of the app via the App Store still fails (Field "amount_available_for_refund" does not exist in model "account.payment"). But I don't think this is absolutely necessary as the app itself seems to work. Thank you. |
|
Although I can now at least call up the "Invoicing" app again, I still receive errors in various other places for missing field information or entire fields after upgrading to odoo16: Invoicing -> Configuration -> Journals: Update app account: Update module "account_payment": I've installed module "Payment - Account / Invoice Online Payment Patch", because patch sounds like some troubleshooting but still no changes. Is there a list or detailed instructions for "account" somewhere on what may need to be set, installed or uninstalled for the invoicing app upgrade process to run successfully? Unfortunately, I don't know what to do. On the migration page (#3681) there is a tick next to "account" and also next to "account_payment", which indicates to me that the upgrade process is complete. |
|
It seems you are not executing correctly the upgrade. There should be traces in the migration log about the migration queries. |
|
Thank you very much! Where exactly can I find this upgrade log file? I only see the upgrade_analysis.txt files for many individual modules (openupgrade_scripts/scripts/). For account_payment, for example, the following is shown there: and for the module account: Odoo is running in a docker compose environment with the postgres and im starting the upgrade with the command |
|
The command with the |
|
Okay, in addition to many INFO statements where a "creating or updating database tables" is executed, I also see some errors from Postgres, e.g. However, the whole upgrade process then aborts in the end after prompting the following message I really don't understand what else I need to do as the odoo15 installation is completely empty to test the upgrade process, uses the latest docker image of version 15 and only has account and account_payment installed. |
|
I think |
|
Hi @mholthausen thank you for reporting this issue. I faced the same error today a JS Uncaught Promise with the following : I used OpenUpgrade on a fresh 15.0 database with only purchase installed. The issue here was that account_payment module was not installed on v16.0. The solution is here to install account_payment module. I am not sure why the account_payment would not auto_install though ? Any idea @pedrobaeza ? |
|
In theory the module should be installed if there's a dependency chain, but if no module depends on it, that's why it's not installed, even due to the auto_install property. |
|
@remi-filament thanks for coming back to this issue. I did that, installed account_payment in v15. The original error (that I could no longer call up invoicing) has been fixed. But now all the other error messages and warnings that I have documented here appear. |
|
@mholthausen as Pedro mentioned in a previous comment, it seems that you are not running OpenUpgrade properly. Basically, you need to run through the following steps :
|
@pedrobaeza thanks for your answer, would it then be necessary to take extra action in OpenUpgrade migration scripts to force install this account_payment module ? I see a number of scenarios, but not sure which one fits better OpenUpgrade strategy :
I would be in favor of the last option, since more transparent to migration user, but am not sure how it was done in the past on OpenUpgrade (assuming that this problem already existed on previous migrations for other modules) ? |
|
Option 3 may be the way. |
|
Well, i'm pretty lost. let's try to sum up : In V15 :
There is no module that depends on account_payment (in CE and EE). So except explicit installation, In V16 :*** : Changes, regarding V15.
In that version The following modules depends on My point of view
|
|
I proposed a fix in #4310 Thanks for your analysis @legalsylvain it is even worse if you look at the workaround they implemented in module account_payment_invoice_online_payment_patch with commit odoo/odoo@acd0f46 Basically, in v16 without this patch if you want to disable online payment on invoice, it would uninstall account_payment and therefore all dependencies (mainly sale) so they introduced the patch module to be able to disable online payment without uninstalling account_payment... |
|
Rest of procedure doubts, please use the Discussions section. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Module
account (account.move and account.payment)
Describe the bug
I have installed a fresh odoo15 and installed the app "account". After the upgrade to odoo16 I get the following error when I try to open the view of the Invoicong app in odoo:
I tried to run an upgrade of the app "account" from the App view. But during this process, I get the following error
(it says: the field "amount_available_for_refund" does not exist in model "account.payment"):
To Reproduce
Affected versions: 16.0
Steps to reproduce the behavior:
Expected behavior
I would expect the app account (without any modules or data) to be accessible after the upgrade without error messages, or at least that the app can be upgraded without errors and can then be used again.
The text was updated successfully, but these errors were encountered: