-
-
Notifications
You must be signed in to change notification settings - Fork 250
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
[RFC] Avaliar a possibilidade buscar os dados fiscais através de partner_id.commercial_partner_id #2071
Comments
Realmente @marcelsavegnago , para quem não usa o l10n_br_sale_stock ou o l10n_br_purchase_stock, esse problema pode ser serio. Eu fiz um PR para resolver isso #2075 |
There hasn't been any activity on this issue in the past 6 months, so it has been marked as stale and it will be closed automatically if no further activity occurs in the next 30 days. |
Resolvido no #2520 |
@marcelsavegnago conseguiu validar se o #2520 resolve ? |
@antoniospneto não testei mas é isso ai |
There hasn't been any activity on this issue in the past 6 months, so it has been marked as stale and it will be closed automatically if no further activity occurs in the next 30 days. |
Podemos fechar esse? |
Hoje todos os dados fiscais inclusive os calculos dos impostos dependem diretamente do partner_id.campox , y ou z
Acho que pode ser interessante mudar para partner_id.commercial_partner_id.campox, y ou z
Nativamente se o parceiro tem um parent_id o comercial_partner_id é o parent_id e se nao tem o parent_id o comercial_partner_id é ele mesmo
https://github.com/odoo/odoo/blob/a362257ef49a7e074ff2badd5f969777cb2d9585/odoo/addons/base/models/res_partner.py#L293
Essa mudança vai além do fiscal e mexe tbm no nfe e outros
Referências enviadas pelo Raphael
https://www.slideshare.net/RaphalValyi/openerp-contact-id-solution-to-the-contacts-issue-in-v7
https://github.com/OCA/sale-workflow/tree/14.0/sale_commercial_partner
https://github.com/OCA/purchase-workflow/tree/14.0/purchase_commercial_partner
The text was updated successfully, but these errors were encountered: