Navigation: Schema: base_import > Tables

import

Base Import

Catalog: Odoo

Schema: base_import

Documentation:

This model is used to prepare the loading of data coming from a user file.

Here is the process that is followed:

#. The user selects a file to import.

#. File parsing and mapping suggestion (see "parse_preview" method)

#. Extract the current model's importable fields tree (see :meth:`get_fields_tree`).

#. Read the file (see :meth:`_read_file`) and extract header names and file

length (used for batch import).

#. Extract headers types from the data preview (10 first line of the file)

(see :meth:`_extract_headers_types`).

#. Try to find for each header a field to map with (see :meth:`_get_mapping_suggestions`)

- First check the previously saved mappings between the header name

and one of the model's fields.

- If no mapping found, try an exact match comparison using fields

technical names, labels and user language translated labels.

- If nothing found, try a fuzzy match using word distance between

header name and fields tachnical names, labels and user language

translated labels. Keep only the closest match.

#. Prepare examples for each columns using the first non null value from each column.

#. Send the info back to the UI where the user can modify the suggested mapping.

#. Execute the import: There are two import mode with uses the same process. (see :meth:`execute_import`)

#. Test import: Try to import but rollback the transaction. This allows

the check errors during the import process and allow the user to

choose import options for the different encountered errors.

#. Real import: Try to import the file using the configured mapping and

the eventual "error mapping options". If import encounters blocking

errors, the transaction is rollbacked and the user is allowed to

choose import options for the different errors.

- Get file data and fields to import into (see :meth:`_convert_import_data`).

- Parse date, float and binary data (see :meth:`_parse_import_data`).

- Handle multiple mapping -> concatenate char/text/many2many columns

mapped on the same field (see :meth:`_handle_multi_mapping`).

- Handle fallback values for boolean and selection fields, in case

input data does not match any allowed values (see :meth:`_handle_fallback_values`).

- Load data (see ir.model "load" method).

- Rollback transaction if test mode or if encountered error.

- Save mapping if any import is successful to ease later mapping suggestions.

- Return import result to the UI (success or errors if any).

The data in this table is partitioned per value of the column.

This is a read-only table. The Odoo API may not support changing the data or the Invantive SQL driver for Odoo does not cover it. In the latter case, please use the table NativePlatformScalarRequests to upload data to the Odoo API.

Table Columns

The columns of the table import are shown below. Each column has an SQL data type.

Name	Data Type	Label	Required	Documentation
create_date	datetime	Created on	☐
create_uid_label	string		☐
create_uid	string		☐
display_name	string	Display Name	☐
file_name	string	File Name	☐
file_type	string	File Type	☐
file	byte[]	File	☐	File to check and/or import, raw binary (not base64)
id	int32	ID	☐
res_model	string	Model	☐
write_date	datetime	Last Updated on	☐
write_uid_label	string		☐
write_uid	string		☐

01-03-2023 15:29 Version 22.1.135-BETA+3826

Important Safety and Usage Information

Intended Use and Limitations: This software, developed by Invantive, is designed to support a variety of business and information technology data processing functions, such as accounting, financial reporting an sales reporting. It is important to note that this software is not designed, tested, or approved for use in environments where malfunction or failure could lead to life-threatening situations or severe physical or environmental damage. This includes, but is not limited to:

Nuclear facilities: The software should not be used for operations or functions related to the control, maintenance, or operation of nuclear facilities.
Defense and Military Applications: This software is not suitable for use in defense-related applications, including but not limited to weaponry control, military strategy planning, or any other aspects of national defense.
Aviation: The software is not intended for use in the operation, navigation, or communication systems of any aircraft or air traffic control environments.
Healthcare and Medicine Production: This software should not be utilized for medical device operation, patient data analysis for critical health decisions, pharmaceutical production, or medical research where its failure or malfunction could impact patient health.
Chemical and Hazardous Material Handling: This software is not intended for the management, control, or operational aspects of chemical plants or hazardous material handling facilities. Any malfunction in software used in these settings could result in dangerous chemical spills, explosions, or environmental disasters.
Transportation and Traffic Control Systems: The software should not be used for the control, operation, or management of transportation systems, including railway signal controls, subway systems, or traffic light management. Malfunctions in such critical systems could lead to severe accidents and endanger public safety.
Energy Grid and Utility Control Systems: This software is not designed for the control or operation of energy grid systems, including electrical substations, renewable energy control systems, or water utility control systems. The failure of software in these areas could lead to significant power outages, water supply disruptions, or other public utility failures, potentially endangering communities and causing extensive damage.
Other High-Risk Environments: Any other critical infrastructure and environments where a failure of the software could result in significant harm to individuals or the environment.

User Responsibility: Users must ensure that they understand the intended use of the software and refrain from deploying it in any setting that falls outside of its designed purpose. It is the responsibility of the user to assess the suitability of the software for their intended application, especially in any scenarios that might pose a risk to life, health, or the environment.

Disclaimer of Liability: Invantive disclaims any responsibility for damage, injury, or legal consequences resulting from the use or misuse of this software in prohibited or unintended applications.

Please enable JavaScript to view this site.

Odoo API Data Model

import

Table Columns

Important Safety and Usage Information