-
-
Notifications
You must be signed in to change notification settings - Fork 507
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
[9.0][MIG] l10n_es_aeat_mod349: Migration to 9.0 #435
Merged
Merged
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
pedrobaeza
force-pushed
the
9.0-l10n_es_aeat_mod349
branch
4 times, most recently
from
January 30, 2017 21:23
7fb899f
to
2fe45a0
Compare
pedrobaeza
force-pushed
the
9.0-l10n_es_aeat_mod349
branch
2 times, most recently
from
February 23, 2017 10:23
39d49b1
to
abd2e81
Compare
* Pylint * Use new API [skip ci]
* Mejora del rendimiento. * Apuntes contables como fuente de datos. El motor del informe se construye a partir de apuntes contables, y la información de facturas se consulta cuando se necesita. De este modo aseguramos que los resultados serán consistentes con los otros modelos de AEAT, que también toman como fuente de datos los apuntes contables. Así evitamos posibles inconsistencias. * Nuevo informe Qweb, que sustituye al antiguo RML * Correcciones para exporación a formato BOE. Permite importar el modelo a la web de hacienda. * Permite borrar operaciones que no se quiere declarar. El usuario puede eliminar las operaciones que no desee incluir en la presentación. Esto será especialmente útil en el caso de presentaciones complementarias. * En declaraciones normales y complementarias se excluyen automáticamente operaciones ya presentadas anteriormente. * Script de migración para tener en cuenta los cambios en el modelo de datos.
pedrobaeza
force-pushed
the
9.0-l10n_es_aeat_mod349
branch
2 times, most recently
from
January 29, 2018 21:00
097339c
to
1a4cefa
Compare
pedrobaeza
changed the title
[MIG] l10n_es_aeat_mod349: Migration to 9.0
[9.0][MIG] l10n_es_aeat_mod349: Migration to 9.0
Jan 30, 2018
* Save in account.move.line directly the 349 export key via a selection field, so you are not bound to a map line record instead of mapping changes. * Field renamings for better understanding. * Map data with command `4` instead of `6` for allowing custom mappings. * Added constraint for avoiding duplicated mapping lines with the same operation key. * Fix tests asserts and code * Fix refund records computation * Complete behavior for imported move lines declarations * Switch certain fields to computed ones, for avoiding extra code that can be handled easily with ORM, but without performance penalty thanks to norecompute ORM option. * Remove useless check for invalid characters, as export now removes them
pedrobaeza
force-pushed
the
9.0-l10n_es_aeat_mod349
branch
from
January 30, 2018 01:37
1a4cefa
to
84e81f5
Compare
Últimas pruebas en producción de la refactorización realizadas, así que fusiono. |
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.
@Tecnativa