-
-
Notifications
You must be signed in to change notification settings - Fork 554
[18.0][IMP] l10n_es_aeat_mod347: Field Not in mod347 in partner converted to company dependent #4334
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
base: 18.0
Are you sure you want to change the base?
[18.0][IMP] l10n_es_aeat_mod347: Field Not in mod347 in partner converted to company dependent #4334
Conversation
607a8ab
to
882338c
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Gracias @Andrii9090 por la migración de esta funcionalidad, durante la migración en #4256 se olvido incluir este commit.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Revisado Funcionalmente
Un contacto que marcas como no incluir en el 347 en una compañía en las otras no queda marcado
Gracias @EmilioPascual @Andrii9090
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Ver comentario inline.
|
||
def migrate(cr, version): | ||
env = api.Environment(cr, SUPERUSER_ID, {}) | ||
openupgrade.convert_to_company_dependent( |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Esto debe detectar si viene de 16.0, donde ya está convertido a dependiente de la compañía, y entonces daría error.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Correcto.
@Andrii9090 debes usar parse_version
importandolo desde odoo.tools
Algo parecido a:
from odoo.tools import parse_version
...
def migrate(cr, version):
if parse_version(version) == parse_version(16.0):
return
....
Además, debería también comprobarse en el pre-migration
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Bueno, mejor que con eso de la versión, que además, puedes venir de la 17, no de la 16, se debería comprobar por datos. Por ejemplo, si existe la columna en la BD.
Faltaría también el fw-port de la 17, ¿no? |
Se intentará, pero a veces el tiempo no da para más y al final toca priorizar. |
El fw-port de la 17 debe ser igual que el de la 18, y ésta no se puede aceptar sin tener la anterior. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Revisado Funcionalmente
Un contacto que marcas como no incluir en el 347 en una compañía en las otras no queda marcado 👌.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Gracias @Andrii9090 por migrar esta funcionalidad 😄. Testeado funcionalmente y todo correcto.

Gracias @Andrii9090 !! |
This is a straightforward cherry-pick of commit 217854a
MT-10026 @moduon @rafaelbn @yajo @EmilioPascual @u0f please review if you want 😄