Hi, El 07/04/2013 20:18, <[email protected]> va escriure: > > Comment by [email protected]: > > = Background = > > In my country there is a standard statement file format used by all banks.
It makes sense :-) We have made a Python library (Retrofix, in Bibucket and Pypy) with the logic to read and write the files diferebt formats used here. Tryton uses it to extrcqt the data and generate the models. It leave the Tryton's code more clean and it is easier to share the effort of support the banking file formats. > = Changes to blueprint = > > I suggest to use a new model `account.statement.import` instead of `imported_attachment` (or binary field) on `account.statement`. The idea is precisely that account.statement was the account.statement.import model that you suggest. A "readonly" model generated by vank statement importation (well, what is "readonly" is the lines). What the user can change after imporation is the related account.move's. Last Friday we (Spanish localization team) had been discusing about how to select or generate tgis moves from the statement line (of course, with heuristic to help the users). I leave to Albert to explain better the conclusions and to analize the fields you propose for imported lines.
