-
-
Notifications
You must be signed in to change notification settings - Fork 695
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
[13.0][MIG] account #2275
[13.0][MIG] account #2275
Conversation
1c2d880
to
3bffe77
Compare
c6ee621
to
13a4df8
Compare
ex tax invoices are showing the tax as an invoice line on historic invoices. |
yeah, and that's wrong? how should be handled correctly from your POV? |
@MiquelRForgeFlow can make a litlle text to explain the methodoly to merge account.move and account.invoice ? Thanks |
@MiquelRForgeFlow Sorry, I opened an issue with more detail that got closed before I added that 1 liner, which was that for this particular migration I could live with it.. Anyway, whether it is wrong or not I don't know. It certainly looks wrong, but I haven't done an actual invoice on v13 yet to know what looks right, but I imagine it should look the same as doing an invoice in v13. |
13a4df8
to
5968d42
Compare
@khaeusler thanks for your input. I will try to solve your case when having some time. |
5968d42
to
ae60003
Compare
Commit ae60003c91c9d524404d6de7ee074986f1e2cb0e shouldn't be here. |
1934534
to
8c5e499
Compare
2afe3c6
to
683e871
Compare
Hello everybody following this PR, I have added the relation between move lines and requisition lines and account tags. Could you do one last review? @etobella I have implemented the other way for grouped journal items. Could you check again? @nomadic-coding could you check again if your issues persist? |
683e871
to
0c1f9b6
Compare
@MiquelRForgeFlow @kos94ok-3D thanks for the fixes. Looks good now. Well done. I'll keep on testing. |
c71d877
to
b681862
Compare
b681862
to
af4b75d
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.
Tested with aggregated invoices and not and all works as expected
OK, let's merge this as a good base and we can improve later if we find more things. Thanks to all the involved people in developing and reviewing. |
I tried a v12 > v13 upgrade today. Seems all but account is working. I still don't get the correct invoices. On my v13-database the account_move and account_move_line I get, seems to me, incorrect or no values: account_move account_move_line Am I forgetting something? Is my v12-dbase not correct (seems to be, though)? Is it still work-in-progress? FYI, to get the latest OpenUpgrade installation I installed today: Btw. Thanks for all the work you put into it |
Sorry, but everything is working in our side, so you should have something incorrect in your end, or some non described steps to get to that problem, so unless you bring more information to shed some light, nothing can be done. |
Thank for your reply. I tried my method with a new database, and no invoices either. So it's definitely on my side. Can you see what's wrong with my current process? Deleted post partially: an incorrect method should not be found on the internet Any advice would be greatly appreciated! |
It should fall on data side, so I'm afraid I can't help you |
@BartvandenHout maybe you will find a clue in the logs of your migration |
Deleted post: wrong place for posting my method. I'll find a better place for it :-) |
Migration of
account
.--
I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr