import : Odoo itgen_odoo_import
read only per partition
- Catalogue :
Odoo - Schéma :
base_import - Étiquette : itgen_odoo_import
Import de base
Permet uniquement de récupérer des données.
Résumé
Ce modèle sert à préparer le chargement des données provenant d'un fichier utilisateur.
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).
Colonnes de table
Les colonnes de la table import sont présentées ci-dessous. Chaque colonne possède un type de données SQL. Une nouvelle valeur non nulle doit être fournie pour chaque colonne requise à tout moment lors de l'insertion et de la mise à jour.
| Name | Type de données | Label | Required | Marks | Documentation |
|---|---|---|---|---|---|
create_ |
datetime |
Créé le | |||
create_ |
varchar2 |
||||
create_ |
varchar2 |
||||
display_ |
varchar2 |
Afficher le nom | |||
file |
varbinary |
File | Fichier à vérifier et/ou à importer, binaire brut (non base64) | ||
file_ |
varchar2 |
Nom de fichier | |||
file_ |
varchar2 |
Type de fichier | |||
id |
int32 |
ID | |||
res_ |
varchar2 |
Model | |||
write_ |
datetime |
Dernière mise à jour le | |||
write_ |
varchar2 |
||||
write_ |
varchar2 |
Notes de Version
Quels ont été les changements apportés à chaque version au niveau des tables, des colonnes, des attributs et des fonctionnalités du chauffeur :