2705.75

v 9.0 v 10.0 v 12.0 Third Party 1
Availability
Odoo Online
Odoo.sh
On Premise
Technical Name file_data_importer
LicenseSee License tab
Websitehttp://www.braintec-group.com
Versions 9.0 12.0 14.0 15.0 13.0 10.0
You bought this module and need support? Click here!
Availability
Odoo Online
Odoo.sh
On Premise
Technical Name file_data_importer
LicenseSee License tab
Websitehttp://www.braintec-group.com
Versions 9.0 12.0 14.0 15.0 13.0 10.0

File Data Importer

Import Information As Odoo Records

This module is meant to be used to import a set of information organized in rows (xls/csv format) where each row contains information about one existing or new record from a specific class of Odoo.
This is not an extension nor an alternative to Odoo's default import system. It simply provides a set of features to ease the import task without having to modify your raw data so Odoo's import system can understand it.
Primary keys are defined by the user with the information in the file so records can be retrieved in an unique way. If the record exists it is updated. If not, it is created.
Also, a single row can contain information about multiple records connected between them. Therefore, you can import more than one object per row and, for each of them, as many fields as you need.

Example: Import .xls File

This file contains a list of rows representing vehicles and the properties inside the vehicles. Each red circle represents a different object that is linked to one of the others in the same row.
For example, the first circle is the fleet.vehicle (the car) to be imported, the second circle is the driver (res.partner) and the third circle is a contact of the driver (res.partner as well). The blue lines indicate regular attributes (char/number) related to any of the previous objects (in this case, they are attributes of fleet vehicle).
  • 1. You can import both .xls(x) and .csv files.
  • 2. It is possible to specify a max. size to import the file by batches and avoid consuming too much resources.
  • 3. The file to be imported.
  • 4. Where the headers are starting, because not always the rows start at the beginning.
  • 5. This is where the information about how to map the rows with odoo classes is set.
  • 6. The odoo model represented by the set of columns defined at the right side.
  • 7. The odoo field(s) that will be used to identify the record in the system, because what you are importing may exist already.
  • 8. The columns from the file and the equivalent in odoo as a field from the specified model.
  • 9. This is a nested object that represents a relationship (many2one x2many) with the current object. In this case, it represents the driver.
  • In this case, it represents the driver.
  • 10. Two fields were selected to be used to identify a res.partner in the system, because just one of them is not enough to make it unique.
  • 11. This is where the binding parent-child is defined.
  • 12. The driver, itself, has a nested partner (the last red circle in the first image).
Imported records
  • 13. It is the license plate, the field used to identify the cars (fleet.vehicle) uniquely.
  • 14. It is the many2one to res.partner, the driver. All the blue fields are regular properties (char/number) from fleet.vehicle.
  • 16. It is a value that was not given in the file but was set by default in the import object.
  • 17. This date was specified as a number (internal representation of Microsoft Excel) but cast at runtime during the import process as specified in the import object.
  • 18. In the file it was just given "D" or "G", but a transformation has been also applied here to cast it to our needs.

All the nested objects are imported too

Video Tutorials On How To Use

Basic Features

Advanced Features

Update Records

Child Objects

Contact Us
  • For questions related to this application, please use the following email.
Odoo Proprietary License v1.0

This software and associated files (the "Software") may only be used (executed, modified, executed after modifications)
if you have purchased a valid license from the authors, typically via Odoo Apps,
or if you have received a written agreement from the authors of the Software (see the COPYRIGHT file).

You may develop Odoo modules that use the Software as a library
(typically by depending on it, importing it and using its resources),
but without copying any source code or material from the Software.
You may distribute those modules under the license of your choice,
provided that this license is compatible with the terms of the Odoo Proprietary License
(For example: LGPL, MIT, or proprietary licenses similar to this one).

It is forbidden to publish, distribute, sublicense, or sell copies of the Software or modified copies of the Software.

The above copyright notice and this permission notice must be included in all copies
or substantial portions of the Software.

THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED,
INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT.
IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY,
WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.

Please log in to comment on this module

  • The author can leave a single reply to each comment.
  • This section is meant to ask simple questions or leave a rating. Every report of a problem experienced while using the module should be addressed to the author directly (refer to the following point).
  • If you want to start a discussion with the author or have a question related to your purchase, please use the support page.