Repository navigation
Conversation
tafaRU
requested changes
Oct 1, 2026
eLBati
force-pushed
the
l10n_it_edi_extension-self-inv
branch
from
October 2, 2026 12:36
9a85e1e to
323f1d8
Compare
tafaRU
requested changes
Oct 2, 2026
| with the reason in its e-invoicing warning. | ||
| When a move raises an error, it stays unsent | ||
| with the reason in the final notification. | ||
| In both cases, the other moves are sent anyway. |
Member
There was a problem hiding this comment.
Quest'ultima frase non mi è molto chiara. Come dev'essere interpretata? Che nei due casi precedenti vengono comunque inviate allo SdI?
Ti propongo un'altra versione di docstring:
"""Send the selected self-invoices to the SdI.
Each move is sent with `action_l10n_it_edi_send`.
A move that cannot be sent does not stop the others:
the moves already sent stay sent and the next ones are still tried.
The reason is shown in the e-invoicing warning of the move
(failed export checks, error returned by the SdI)
or in the final notification (errors raised while sending).
Everything runs in the same transaction: if the whole request fails
(e.g. worker time limit), the moves already sent are rolled back
although the SdI has received them.
"""
Cosa ne pensi?
Member
Author
There was a problem hiding this comment.
Grazie, modificato.
Riguardo alla transazione unica, ho modificato: ogni autofattura viene committata subito dopo l'invio
Core l10n_it_edi only sends self-invoices (e.g. TD17 for reverse charge) one at a time, with the "Send to SDI" button of the vendor bill form. Add the "Send self-invoices to SDI" button to the header of the vendor bills list view: each selected self-invoice that can be sent goes through action_l10n_it_edi_send, like the form button, in its own savepoint. A self-invoice that fails the export checks or raises an error does not prevent the others from being sent. Each self-invoice is committed right after being sent, like core e-invoicing localizations do (e.g. l10n_ro_edi, l10n_my_edi): if the request is interrupted, Odoo still knows which self-invoices the SdI has received. Assisted-by: Claude Opus 5.5
TD29 communications are sent with the same button as self-invoices: include them in the "Send self-invoices to SDI" button of the vendor bills list view. Assisted-by: Claude Opus 5.5
eLBati
force-pushed
the
l10n_it_edi_extension-self-inv
branch
from
October 6, 2026 12:38
323f1d8 to
67e8179
Compare
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
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.
Con il modulo standard
l10n_it_edile autofatture (es. TD17, TD18, TD19 per il reverse charge) si possono inviare allo SdI solo una alla volta, con il pulsante "Invia a SDI" della fattura fornitore:action_l10n_it_edi_sendlavora su un solo record e il wizard "Invia e stampa" accetta solo documenti di vendita.l10n_it_edi_extensionnel metodo
_l10n_it_edi_ext_is_self_invoice_to_send, che altri moduli possono estendere.action_l10n_it_edi_send, quindi con gli stessi controlli, lo stesso XML e lo stesso canale di invio del pulsante (proxy Odoo, oppure PEC conl10n_it_edi_pec).annullare gli invii già fatti.
l10n_it_edi_td29Relazione con altre PR
l10n_it_edi_rc_generate_xml_only) sovrascriveaction_l10n_it_edi_send. L'invio massivo passa dallo stesso metodo, quindi usa anche l'XML già generato._l10n_it_edi_ext_is_self_invoice_to_send, così che azione e pulsante restino coerenti.