-
-
Notifications
You must be signed in to change notification settings - Fork 307
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
[FIX] Precisione decimale non usata durante l'importazione della fattura elettronica #4446
[FIX] Precisione decimale non usata durante l'importazione della fattura elettronica #4446
Conversation
7e96f5d
to
9a4f961
Compare
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.
Test funzionale: OK
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.
bug
STEPS
- importo xml con 3 decimali
- la fattura viene importata correttamente
- modifica data di registrazione (o conto contropartita)
ATTESO
gli importi dovrebbero rimanere corretti
RISULTATO
alla modifica di data registrazione (o conto contropartita) vengono ricalcolati gli importi
Allego video
Screencast.2024-11-21.14.43.38.mp4
Giusto: quando gli importi vengono ricalcolati, si usa la precisione globale non quella temporanea impostata durante l'importazione. Secondo me è un problema dovuto a queste precisioni temporanee in sé, non alla PR specifica. Comunque ci sta segnalarlo qui, grazie 😄 magari ne parliamo domattina |
A questo punto vedo 2 strade:
Un approccio per il ricalcolo: #2874 |
Ok grazie, vedo come fare |
89c5ed6
to
6ba5e5b
Compare
This comment was marked as resolved.
This comment was marked as resolved.
/ocabot rebase |
Congratulations, PR rebased to 16.0. |
6ba5e5b
to
83528df
Compare
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.
Test funzionale: OK
/ocabot merge minor |
What a great day to merge this nice PR. Let's do it! |
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.
LGTM
This PR has the |
@TheMule71 your merge command was aborted due to failed check(s), which you can inspect on this commit of 16.0-ocabot-merge-pr-4446-by-TheMule71-bump-minor. After fixing the problem, you can re-issue a merge command. Please refrain from merging manually as it will most probably make the target branch red. |
3 giorni fa era tutto 🟢 |
Otherwise, if another precision is used during import and an exception is raised, the system precision becomes the precision set during import. Co-authored-by: Simone Rubino <[email protected]>
When price precision is increased during import, the price of the created lines should have been computed using the new precision
Congratulations, PR rebased to 16.0. |
83528df
to
7b3db28
Compare
`message_dict` contains values used to track the message, but we use it to create a `mail.message` so the extra values have to be removed because they are not fields of `mail.message`.
/ocabot merge minor |
On my way to merge this fine PR! |
Congratulations, your PR was merged at f0fa0e2. Thanks a lot for contributing to OCA. ❤️ |
Risolve #4445 per
16.0
.Sostituisce #3843 per risolvere #3843 (review).
Non ho incluso un test perché il codice che imposta la precisione decimale quando eseguito nei test solleva l'errore:
Stack
Ho aggiunto un commit per correggere l'errore nei test https://github.com/OCA/l10n-italy/actions/runs/12313495777/job/34367636978#step:8:1717:
Stack
Dovuto al commit odoo/odoo@43041df che è solo in
16.0
.