invantive documentation
Forum di supporto InvantiveAccedi / Registrati

import: Odoo itgen_odoo_import

read only per partition

  • Catalogo: Odoo
  • Schema: base_import
  • Etichetta: itgen_odoo_import

Base Import

È possibile solo recuperare i dati.

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).

Colonne della tabella

Di seguito sono riportate le colonne della tabella import. Ogni colonna ha un tipo di dati SQL. Un nuovo valore non nullo deve essere fornito per ogni colonna richiesta in ogni momento durante l'inserimento e l'aggiornamento.

Name Tipo di dati Label Required Marks Documentation
create_date datetime Creato il
create_uid varchar2
create_uid_label varchar2
display_name varchar2 Nome visualizzato
file varbinary File File to check and/or import, raw binary (not base64)
file_name varchar2 Nome del file
file_type varchar2 Tipo di file
id int32 ID
res_model varchar2 Model
write_date datetime Last Updated on
write_uid varchar2
write_uid_label varchar2

Note di rilascio

Cosa è cambiato, versione per versione, nelle tabelle, nelle colonne, negli attributi e nelle funzionalità del driver: