[FIX] Rename wizard AbstractModel #1168
Open
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
The original name existing with only underscores is giving errors when upgrading to v17. This change has been discussed in OCA#1101
FernandoRomera
approved these changes
Jun 4, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
The original name existing with only underscores is giving errors when upgrading to v17.
File "/tmp/tmpeyhz1_ak/migrations/util/helpers.py", line 140, in _validate_model
raise SleepyDeveloperError("
{}seems to be a table name instead of model name".format(model))odoo.upgrade.util.exceptions.SleepyDeveloperError:
account_financial_report_abstract_wizardseems to be a table name instead of model nameThis change has been discussed in #1101
Upgrades to v17 should work. I created a support ticket for this and Odoo should have fixed this one for all customers.
But it's better to be safe then sorry for next version migrations to fix this problem in front.