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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Sembra un rollback di 0315ba5, @TheMule71 @michelerusti cosa ne pensate?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Ho visto anche la PR che ha portato da Many2one a Selection , ma secondo il mio parere ha più senso sia una many2one visto anche che nel caso di Selection, viene riportato errore se viene settato quel campo senza contesto active_model ....
Cioè gli attributi dell'entità del wizard, non dovrebbero essere strict rispetto al contesto ma il contesto dovrebbe solamente suggerire il report da utilizzare. Poi usando widget=selection anche la many2one diventa come selection e quindi trasparente per ,l'utente finale
Poi chi dovrà provvedere ad esportare le fatture, avrà sicuramente anche accesso al modello ir.actions.report quindi non dovrebbero esserci problemi di permessi d'accesso
Ovviamente parere mio tecnico, potrei anche sbagliarmi