[17.0][MIG] l10n_es_payment_order_confirming_aef: Migration to 17.0 #3749
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
[UPD] Update l10n_es_payment_order_confirming_aef.pot [UPD] README.rst
[UPD] Update l10n_es_payment_order_confirming_aef.pot [UPD] README.rst [UPD] README.rst
Translated using Weblate (Spanish) Currently translated at 100.0% (17 of 17 strings) Translation: l10n-spain-16.0/l10n-spain-16.0-l10n_es_payment_order_confirming_aef Translate-URL: https://translation.odoo-community.org/projects/l10n-spain-16-0/l10n-spain-16-0-l10n_es_payment_order_confirming_aef/es/
…number The field `ref` in the account.move.line doesn't always contain the same value as the account.move, and what we want is the invoice number, so let's use the move one in any case. Co-Authored-By: Pedro M. Baeza <[email protected]>
… es obligatoria pero Bankinter si la pide [BOT] post-merge updates
Bankinter is actually using the processing date indicated in the file for their planning and using the first line payment date causes that the files generated don't work with that bank. As harmless for the rest of the banks, let's use the date where the file is generated for this data. Closes OCA#3425 [BOT] post-merge updates
Force the invoice to use the partner bank account indicated for the test for having a correct result no matter the upstream code. [BOT] post-merge updates [BOT] post-merge updates
…mesa El dato relativo a la modalidad de la reserva se estaba definiendo vacío, es posible definirlo ahora según las diferentes opciones existentes según la documentación del archivo de confirming. TT49479
…ón correcta Se debe especificar la cuenta bancaria en la posición correcta (103) por lo que se debe utilizar ljust() para rellenar espacios al final de la cuenta bancaria. En la documentación se identifica: "Los campos alfanuméricos se alinearán a la izquierda (“Nombre“) completándose con espacios por la derecha". TT49550 [UPD] Update l10n_es_payment_order_confirming_aef.pot [BOT] post-merge updates Update translation files Updated by "Update PO files to match POT (msgmerge)" hook in Weblate. Translation: l10n-spain-16.0/l10n-spain-16.0-l10n_es_payment_order_confirming_aef Translate-URL: https://translation.odoo-community.org/projects/l10n-spain-16-0/l10n-spain-16-0-l10n_es_payment_order_confirming_aef/
…ing payment method in bank journal [UPD] Update l10n_es_payment_order_confirming_aef.pot [BOT] post-merge updates Update translation files Updated by "Update PO files to match POT (msgmerge)" hook in Weblate. Translation: l10n-spain-16.0/l10n-spain-16.0-l10n_es_payment_order_confirming_aef Translate-URL: https://translation.odoo-community.org/projects/l10n-spain-16-0/l10n-spain-16-0-l10n_es_payment_order_confirming_aef/
Co-authored-by: david-s73
|
/ocabot migration l10n_es_payment_order_confirming_aef |
|
This PR looks fantastic, let's merge it! |
|
Congratulations, your PR was merged at f9c0d93. 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.
Superseed #3653
Migration to 17.0
@Tecnativa TT50082