[13.0][ADD] account_bank_statement_import_file_hook

[JaumeBforgeFlow]

No description provided.

[GuillemCForgeFlow]

LGTM! 👍🏽

[mariadforgeflow]

LVGTM!

[AaronHForgeFlow]

/ocabot merge nobump

[OCA-git-bot]

On my way to merge this fine PR!
Prepared branch 13.0-ocabot-merge-pr-595-by-AaronHForgeFlow-bump-nobump, awaiting test results.

[OCA-git-bot]

@AaronHForgeFlow your merge command was aborted due to failed check(s), which you can inspect on this commit of 13.0-ocabot-merge-pr-595-by-AaronHForgeFlow-bump-nobump.

After fixing the problem, you can re-issue a merge command. Please refrain from merging manually as it will most probably make the target branch red.

[pedrobaeza]

Wait, aborting. Why do you need to do such hooks? This is a very bad practice. What do you want to get?

[JaumeBforgeFlow]

@pedrobaeza, Odoo does the processing of the file in such a way that you are not able to tap into the logic, to modify it while having access to the ir.attachment record being processed. None of the functions called inside the for loop in the import_file() function are passed the attachment as a record.

Having this hook might be interesting in cases such as the one we are working with, where we want to link the resulting statement with the attachment.

[pedrobaeza]

I think you can override _parse_file method, that has as argument the decoded file content, and include in the returned dictionary these contents in a special key. Then override the create method of account.bank.statement, and if you find such key, pop it, call super, and then create the attachment.

[github-actions]

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.

[AaronHForgeFlow]

Hi, just reopening this

[AaronHForgeFlow]

sorry wrong PR