Skip to content
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.

Sign up for GitHub

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

Jump to bottom

[7.0] Duplicated bank statement has unwanted links to journal entries of duplicates statement #611

Closed
NL66278 opened this issue Apr 13, 2017 · 1 comment
Closed

[7.0] Duplicated bank statement has unwanted links to journal entries of duplicates statement #611

NL66278 opened this issue Apr 13, 2017 · 1 comment

Comments

@NL66278
Copy link

NL66278 commented Apr 13, 2017

Impacted versions: 7.0 certainly, did not test (yet) on later

Steps to reproduce:

  • Have a bank statement with some confirmed transactions
  • Duplicate bank statement, and confirm transactions
  • Cancel transactions
    Now journal entries for duplicated bank statements have been removed as well.

Current behavior: See above

Expected behavior: New bank statement(lines) have no links to original
NL66278 added a commit to NL66278/odoo that referenced this issue Apr 13, 2017
@NL66278
[FIX] Issue OCA#611 - do not copy move_ids on duplicate of statement.
71e454d 
The overriden copy() for account.bank.statement.line is not called when the copy() for account.bank.statement is called.
By setting move_ids to [] in copy_data, this is active on direct copy of line, or through copy of complete statement.
@NL66278 NL66278 mentioned this issue Apr 13, 2017
Merged
StefanRijnhart added a commit that referenced this issue Jun 9, 2017
@StefanRijnhart
Merge pull request #612 from NL66278/7.0-issue#611-duplicate-bank-sta…
8c65239 
…tement

[7.0][FIX] Issue #611 - do not copy move_ids on duplicate of statement.
@pedrobaeza
Copy link
Member

Fixed in #612

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@NL66278 @pedrobaeza