-
-
Notifications
You must be signed in to change notification settings - Fork 248
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
[12.0][l10n_br_fiscal] fix property migrations #1890
Conversation
Hi @renatonlima, |
e2a799f
to
1ec1d82
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.
Inseto aniquilado @@
@marcelsavegnago @renatonlima @netosjb eu sugiro de usar esse workaround para destravar o repo ate a OCA tomar uma posiçao ou arrumar uma soluçao para esse QUnitSuite O que vcs acham? Apenas para destravar os PRs travados da 12 mesmo por enquanto... |
bb4f8a0
to
a5f85da
Compare
a5f85da
to
7e3876a
Compare
/ocabot merge minor |
What a great day to merge this nice PR. Let's do it! |
Congratulations, your PR was merged at cd6c5f4. Thanks a lot for contributing to OCA. ❤️ |
resolve esse bug #1862 e o mesmo tipo de bug com a migração do campo fiscal_type.
Basicamente no script de pre-migration, o update ainda nao rodou no banco mas os campos Python dos objetos já foram carregados e nisso nao tem mais esses campos icms_origin ou fiscal_type para usar um domain Odoo. Eu usar um SELECT então.
cc @vanderleiromera @renatonlima