Closed
Conversation
AaronHForgeFlow
force-pushed
the
13.0-l10n_es
branch
2 times, most recently
from
fa7f884 to
e5e14c4
Compare
* if l10n_es_account_invoice_sequence is installed use invoice number as move number
HviorForgeFlow
force-pushed
the
13.0-l10n_es
branch
from
e5e14c4 to
178821a
Compare
Contributor
|
Included in #2419. |
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
l10n_es_account_invoice_sequence introduced different numbering between invoices and account moves using a specific sequence selected in the journal. In v13 invoice number is lost. It is best to keep the sequence of the invoice in this case. We should trust that sequence, as long as all localization reports used that sequence.