-
-
Notifications
You must be signed in to change notification settings - Fork 615
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
[16.0][MIG] pos_report_session_summary: Migration to version 16.0 #1229
[16.0][MIG] pos_report_session_summary: Migration to version 16.0 #1229
Conversation
Updated by "Update PO files to match POT (msgmerge)" hook in Weblate. Translation: pos-15.0/pos-15.0-pos_report_session_summary Translate-URL: https://translation.odoo-community.org/projects/pos-15-0/pos-15-0-pos_report_session_summary/
… 'str' object has no attribute 'decimal_places' when printing session summaryossible to print the report. This pr fixes the error: 'str' object has no attribute 'decimal_places' when printing session summary
/ocabot migration pos_report_session_summary |
/ocabot migration pos_report_session_summary |
@carlos-lopez-tecnativa @pedrobaeza |
@anajuaristi I think what you propose is great; however, the detail is that we would now only use |
If I'm not wrong, when you close the session, you get full details, isn't it? So that's a limitation on how Odoo works now. |
@pedrobaeza while the session is open, In previous versions, Odoo created |
Well, I didn't understand you correctly then the previous one. We obviously need to show everything. The problem I understood is that there's certain information duplicated when the session is closed. We don't want duplicates nor missing information. If we have to sacrifice that the information is not complete until the session is closed, then that's something that can be assumed (but put it on the ROADMAP). |
@pedrobaeza, let me know if, for this report, we should exclude account.bank.statement.line and if all data should be sourced from pos.payment. @anajuaristi, what do you think? Remember that these fields in pos.session can't be used, and amounts must be recomputed only in the reports to show the summary. For context, refer to the Odoo code here: https://github.com/odoo/odoo/blob/ead5c4f365c6cb981b55f5ee26906e42fa4d449d/addons/point_of_sale/models/pos_session.py#L70-L89 |
If pos.payment includes everything, then let's use it. I'm just talking out of what you comment though. Anyway, I insist that the goal is to have a summary of all the payments, no matter the source. If this needs to be limited after the session is closed, then limit it. |
8831d21
to
ebcccff
Compare
@pedrobaeza @anajuaristi |
@anajuaristi, could you please review again? |
👍 About this " pos.payment does not include all the necessary information (e.g., Cash In/Out transactions do not generate a pos.payment)..." p.d: sorry for delay answering, I just come back from holidays |
Right now it's the case, so merging: /ocabot merge nobump |
What a great day to merge this nice PR. Let's do it! |
Congratulations, your PR was merged at 7b82787. Thanks a lot for contributing to OCA. ❤️ |
@Tecnativa TT49806
Supersedes #1190