Over one year in development and now we are pleased to announce a new release of our ea_import with tons of new features and improvements.
At the same time, we would like to announce a new method of collaborating with the community.
So first things first – what is new in the ea_import?
- More verbose error messages are given when CSV data is incompatible with the target model.
- Button to add/remove a menu action in the target model, that when called displays a wizard to the operator enabling a CSV upload and processing of the import job.
- Improvements in the way of processing CSV files, so more compatibility with different formats and languages introduced.
- Improvements in logging.
- Added ability to run a python function post import of data.
- Added ability to fetch data from MySQL databases.
- Added ability to export CSV data from a target model/models : A SQL query defines the output produced in a CSV file. When enabling the sidebar action, this works as a print button, but instead of a report it will return the CSV file. The export supports parsing of active_ids in the SQL query.
So all in all, our ea_import module now can successfully replace the standard OpenERP import/export CSV functionality for companies and OpenERP partners that are serious about their ERP implementations.
We would love to have more time to write manuals and instructions on how to use the tool, however we have been very busy with the current projects and therefore we will do this later and we can only offer commercial support at this time.
Similarly, we would love to interact more with the community, but again – we give priority to our projects, so we can meet deadlines, and we are sorry for not accepting merge proposals from the community on launchpad or publishing our work in real-time. As a company we value quality of code, so we release our work when we feel it is ready.
However, we believe we can improve on that and we came up with a new model that we would like to work with the community:
We publish our stable releases on github when we feel they are ready.
We publish the milestones, so issues can be assigned to these and tracked.
Any bugs must be reported on gihub.
Any improvements must be described on gihub as a new issue and we may create milestones from them.
If anyone would like to contribute this must happen in the following way:
Before starting contributing with your code or time, have a look on open issues and if no one is assigned to it, then add a note that you would like to be assigned. Ideally the request should contain the timeframe and/or a short explanation of what you are going to do.
If you would like to introduce some fixes or certain features that have not been reported, then please create a new ticket, describe the problem or feature, and request that you would like to write the code. We will review and allocate that ticket to you.
Substantial contributions will be added to the credits list.
So to kick start the new method, we have creates 3 milestones:
1 – add FTP files fetching – Enapps assigned – work in progress due mid-May
- fetch file from FTP folders
- process file
- If successful import, delete the file from FTP
2 – CSV export using objects – unassigned
- Similar to SQL export functionality we must be able to generate an export template built from objects data.
3 – Perfect CSV import functionality – unassigned
- Verbose error message for any scenario, so non-technical operators can be guided what is wrong with their data
Oh and the most important part – the module. Enjoy!