[17.0][IMP] l10n_es_igic: tax names changed #4076
Merged
Conversation
This file contains hidden or 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
EmilioPascual
approved these changes
Mar 17, 2025
|
This PR has the |
|
@etobella te parece bien? |
etobella
approved these changes
Mar 18, 2025
Christian-RB
force-pushed
the
17.0-imp-l10n_es_igic
branch
from
4b669dc to
f563a95
Compare
|
What a great day to merge this nice PR. Let's do it! |
|
Congratulations, your PR was merged at 21b98c6. Thanks a lot for contributing to OCA. ❤️ |
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.
Hemos detectado algunos problemas intentando asignar el plan contable de canarias a algunos clientes que ya presentaban un plan contable de península. Por lo que hemos podido comprobar, debido a que los impuestos de península y canarias convivien en la misma contabilidad (al menos en esta versión), al ejecutar el account chart update o bien detecta constantemente el mismo impuesto para xml ids distintos o bien nos da un error de que no pueden existir múltiples impuestos con el mismo
name.Por esto considero que lo mejor sería cambiar los nombres de los impuestos evitando así esta problemática.
@BinhexTeam