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.

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

[IMP] account_statement_import_camt: multi account support #666

Open
wants to merge 1 commit into
base: 16.0
Choose a base branch
from

Conversation

gurneyalex
Copy link
Member

The module account_statement_import_file supports handling files containing informations related to multiple accounts, but this was not taken advantage of by account_statement_import_camt.

We update the structure returned by parser.parse() to use the expected format in case of multiple accounts encountered in CAMT file.

This has the side effect of fixing a bug in the previous implementation, when all the transactions in a CAMT file would be parsed as being on the same account (the one on the last statement found in the file), and possibly even more wrong, in the currency of the last statement).

@gurneyalex gurneyalex added this to the 16.0 milestone Feb 5, 2024
@gurneyalex gurneyalex force-pushed the 16.0-import-camt-multi_account branch from 204da98 to 8b55347 Compare February 5, 2024 18:01
The module account_statement_import_file supports handling files
containing informations related to multiple accounts, but this was not
taken advantage of by account_statement_import_camt.

We update the structure returned by parser.parse() to use the expected
format in case of multiple accounts encountered in CAMT file.

This has the side effect of fixing a bug in the previous implementation,
when all the transactions in a CAMT file would be parsed as being on the
same account (the one on the last statement found in the file), and
possibly even more wrong, in the currency of the last statement).
@gurneyalex gurneyalex force-pushed the 16.0-import-camt-multi_account branch from 6d62744 to 63932d5 Compare February 6, 2024 08:39
Copy link
Member

@StefanRijnhart StefanRijnhart left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Nice one!

Copy link

github-actions bot commented Sep 1, 2024

There hasn't been any activity on this pull request in the past 4 months, so it has been marked as stale and it will be closed automatically if no further activity occurs in the next 30 days.
If you want this PR to never become stale, please ask a PSC member to apply the "no stale" label.

@github-actions github-actions bot added the stale PR/Issue without recent activity, it'll be soon closed automatically. label Sep 1, 2024
@StefanRijnhart
Copy link
Member

@gurneyalex any chance of a rebase to resolve conflicts?

@StefanRijnhart StefanRijnhart removed the stale PR/Issue without recent activity, it'll be soon closed automatically. label Sep 2, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants