|
1.
|
|
|
Get all possible values
|
|
|
module: base_import
openerp-web
|
|
|
|
(no translation yet)
|
|
Suggestions: |
|
|
Obtenir toutes les valeurs possibles
|
|
|
French
base-import in OpenERP Community Backports (Addons) 7.0
by
Christophe Simonis (OpenERP)
|
|
|
|
Located in
code:addons/base_import/static/src/js/import.js:451
|
|
2.
|
|
|
Need to import data from an other application?
|
|
|
module: base_import
openerp-web
|
|
|
|
(no translation yet)
|
|
Suggestions: |
|
|
Besoin d'importer des données d'une autre application ?
|
|
|
French
base-import in OpenERP Community Backports (Addons) 7.0
by
Christophe Simonis (OpenERP)
|
|
|
|
Located in
code:addons/base_import/static/src/xml/import.xml:71
|
|
3.
|
|
|
When you use External IDs, you can import CSV files
with the "External ID" column to define the External
ID of each record you import. Then, you will be able
to make a reference to that record with columns like
"Field/External ID". The following two CSV files give
you an example for Products and their Categories.
|
|
|
module: base_import
openerp-web
|
|
|
represents a line break.
Start a new line in the equivalent position in the translation.
|
|
|
represents a space character.
Enter a space in the equivalent position in the translation.
|
|
|
|
(no translation yet)
|
|
Suggestions: |
|
|
Lorsque vous utilisez des identifiants externes, vous pouvez importer des fichiers CSV
avec la colonne "Id. externe" pour définir l'identifiant externe
de chaque enregistrement que vous importez. Ensuite, vous pourrez
faire référence à cet enregistrement avec des colonnes comme
"Champ / Id. externe". Les deux fichiers CVS suivants vous donnent
un exemple des produits et leurs catégories.
|
|
|
French
base-import in OpenERP Community Backports (Addons) 7.0
by
Christophe Simonis (OpenERP)
|
|
|
|
Located in
code:addons/base_import/static/src/xml/import.xml:163
|
|
4.
|
|
|
How to export/import different tables from an SQL
application to OpenERP?
|
|
|
module: base_import
openerp-web
|
|
|
represents a line break.
Start a new line in the equivalent position in the translation.
|
|
|
represents a space character.
Enter a space in the equivalent position in the translation.
|
|
|
|
(no translation yet)
|
|
Suggestions: |
|
|
Comment exporter/importer différentes tables d'une
application SQL vers OpenERP ?
|
|
|
French
base-import in OpenERP Community Backports (Addons) 7.0
by
Christophe Simonis (OpenERP)
|
|
|
|
Located in
code:addons/base_import/static/src/xml/import.xml:271
|
|
5.
|
|
|
Relation Fields
|
|
|
module: base_import
openerp-web
|
|
|
|
(no translation yet)
|
|
Suggestions: |
|
|
Champs relationnels
|
|
|
French
base-import in OpenERP Community Backports (Addons) 7.0
by
Christophe Simonis (OpenERP)
|
|
|
|
Located in
code:addons/base_import/static/src/js/import.js:331
|
|
6.
|
|
|
Country/Database ID: the unique OpenERP ID for a
record, defined by the ID postgresql column
|
|
|
module: base_import
openerp-web
|
|
|
represents a line break.
Start a new line in the equivalent position in the translation.
|
|
|
represents a space character.
Enter a space in the equivalent position in the translation.
|
|
|
|
(no translation yet)
|
|
Suggestions: |
|
|
Pays/Id. base de données : l'identifiant unique OpenERP d'un
enregistrement, défini par la colonne postgresql "ID".
|
|
|
French
base-import in OpenERP Community Backports (Addons) 7.0
by
Christophe Simonis (OpenERP)
|
|
|
|
Located in
code:addons/base_import/static/src/xml/import.xml:142
|
|
7.
|
|
|
Use
Country/Database ID: You should rarely use this
notation. It's mostly used by developers as it's main
advantage is to never have conflicts (you may have
several records with the same name, but they always
have a unique Database ID)
|
|
|
module: base_import
openerp-web
|
|
|
represents a line break.
Start a new line in the equivalent position in the translation.
|
|
|
represents a space character.
Enter a space in the equivalent position in the translation.
|
|
|
|
(no translation yet)
|
|
Suggestions: |
|
|
Utiliser
Pays/id. base de données : Vous devriez rarement utiliser cette
notation. Elle est en général utilisée par les développeurs : son principal
avantage est de ne jamais avoir de conflits (vous pouvez avoir
plusieurs enregistrements avec le même nom, mais ils ont toujours
un identifiant de base de données unique)
|
|
|
French
base-import in OpenERP Community Backports (Addons) 7.0
by
Christophe Simonis (OpenERP)
|
|
|
|
Located in
code:addons/base_import/static/src/xml/import.xml:155
|
|
8.
|
|
|
For the country
Belgium, you can use one of these 3 ways to import:
|
|
|
module: base_import
openerp-web
|
|
|
represents a line break.
Start a new line in the equivalent position in the translation.
|
|
|
represents a space character.
Enter a space in the equivalent position in the translation.
|
|
|
|
(no translation yet)
|
|
Suggestions: |
|
|
Pour le pays
Belgique, vous avez le choix entre 3 possibilités d'import :
|
|
|
French
base-import in OpenERP Community Backports (Addons) 7.0
by
Christophe Simonis (OpenERP)
|
|
|
|
Located in
code:addons/base_import/static/src/xml/import.xml:146
|
|
9.
|
|
|
company_1,Bigees,True
|
|
|
module: base_import
openerp-web
|
|
|
|
(no translation yet)
|
|
Suggestions: |
|
|
company_1,Bigees,True
|
|
|
French
base-import in OpenERP Community Backports (Addons) 7.0
by
Christophe Simonis (OpenERP)
|
|
|
|
Located in
code:addons/base_import/static/src/xml/import.xml:303
|
|
10.
|
|
|
base_import.tests.models.m2o
|
|
|
module: base_import
|
|
|
|
(no translation yet)
|
|
Suggestions: |
|
|
base_import.tests.models.m2o
|
|
|
French
base-import in OpenERP Community Backports (Addons) 7.0
by
Christophe Simonis (OpenERP)
|
|
|
|
Located in
model:ir.model,name:base_import.model_base_import_tests_models_m2o
|