-
-
Notifications
You must be signed in to change notification settings - Fork 386
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][ADD] account_reconcile_payment_order #722
base: 16.0
Are you sure you want to change the base?
Conversation
54e2dff
to
0ed72e5
Compare
df4bec8
to
10a5cd4
Compare
10a5cd4
to
e890dc7
Compare
I even added a post init hook in order to generate data. @alexis-via WDYT about it? |
I told Alexis my take on this, and I don't think we should go this way. My idea is to enable groups on the list view, and adding a button on the group headers to add the entire group lines in the current reconciliation. For payment orders, we will only need to group by the proper fields (and maybe add a related stored field in aml). This is also more versatile for other kind of mass additions. |
@pedrobaeza You are suggesting something like this? |
I checked your proposal and it might work partially, but there are some related issues: It is not filtering properly. I mean, when you press the button, you are not getting data from all the childs, you are processing the data of the record. Let's put an examples
Also, we will not be able to split data properly on a payment order if multiple dates exist. So, IMO, it is not feasible using only standard odoo functionality 🤔 BTW, it looked as expected (I made the test using Journal, but you can see how it would look like): |
I understand the issue you have found, but I think we can provide a combination:
With all of this, we will have enough tools for doing reconciliation in batches. A small glue module providing the fields to group will be the only need on that matter. |
@alexis-via I think you will enjoy this one 😉
Still some work to do on documentation, but we have something to start