mirror of
https://github.com/odoo/documentation.git
synced 2025-12-12 07:29:27 +07:00
[I18N] *: re-export pot files
As per usual, leave off developer.pot and contributing.pot since we don't translate them (not useful, can't really contribute to/dev in Odoo without knowing English)
This commit is contained in:
Tiffany Chang (tic)
File diff suppressed because it is too large
Load Diff
@@ -8,7 +8,7 @@ msgid ""
|
||||
msgstr ""
|
||||
"Project-Id-Version: Odoo 17.0\n"
|
||||
"Report-Msgid-Bugs-To: \n"
|
||||
"POT-Creation-Date: 2025-10-16 14:19+0000\n"
|
||||
"POT-Creation-Date: 2025-12-09 13:40+0000\n"
|
||||
"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
|
||||
"Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
|
||||
"Language-Team: LANGUAGE <LL@li.org>\n"
|
||||
@@ -903,83 +903,83 @@ msgstr ""
|
||||
msgid "Export and import data"
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/applications/essentials/export_import_data.rst:8
|
||||
#: ../../content/applications/essentials/export_import_data.rst:5
|
||||
msgid "In Odoo, it is sometimes necessary to export or import data for running reports, or for data modification. This document covers the export and import of data into and out of Odoo."
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/applications/essentials/export_import_data.rst:12
|
||||
#: ../../content/applications/essentials/export_import_data.rst:9
|
||||
msgid "Sometimes, users run into a 'time out' error, or a record does not process, due to its size. This can occur with large exports, or in cases where the import file is too large. To circumvent this limitation surrounding the size of the records, process exports or imports in smaller batches."
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/applications/essentials/export_import_data.rst:19
|
||||
#: ../../content/applications/essentials/export_import_data.rst:16
|
||||
msgid "Export data from Odoo"
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/applications/essentials/export_import_data.rst:21
|
||||
msgid "When working with a database, it is sometimes necessary to export data in a distinct file. Doing so can aid in reporting on activities, although, Odoo provides a precise and easy reporting tool with each available application."
|
||||
#: ../../content/applications/essentials/export_import_data.rst:18
|
||||
msgid "When working with a database, it is sometimes necessary to export data in a distinct file. Doing so can aid in reporting on activities, although, Odoo provides a precise reporting tool with each available application."
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/applications/essentials/export_import_data.rst:25
|
||||
msgid "With Odoo, the values can be exported from any field in any record. To do so, activate the list view (|list|), on the items that need to be exported, then select the records that should be exported. To select a record, tick the checkbox next to the corresponding record. Finally, click on |actions|, then :guilabel:`Export`."
|
||||
#: ../../content/applications/essentials/export_import_data.rst:22
|
||||
msgid "With Odoo, the values can be exported from any field in any record. To do so, activate the list view :icon:`fa-list` :guilabel:`(List)` icon, on the items that need to be exported, and then select the records that should be exported. To select a record, tick the checkbox next to the corresponding record. Finally, click the :guilabel:`Action` button, and select :icon:`fa-upload` :guilabel:`(Export)`."
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/applications/essentials/export_import_data.rst:-1
|
||||
msgid "View of the different things to enable/click to export data."
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/applications/essentials/export_import_data.rst:34
|
||||
msgid "When clicking on :guilabel:`Export`, an :guilabel:`Export Data` pop-over window appears, with several options for the data to export:"
|
||||
#: ../../content/applications/essentials/export_import_data.rst:31
|
||||
msgid "When clicking on :icon:`fa-upload` :guilabel:`Export`, a :guilabel:`Export Data` pop-over window appears, with several options for the data to export:"
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/applications/essentials/export_import_data.rst:-1
|
||||
msgid "Overview of options to consider when exporting data in Odoo.."
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/applications/essentials/export_import_data.rst:41
|
||||
msgid "With the :guilabel:`I want to update data (import-compatable export)` option ticked, the system only shows the fields that can be imported. This is helpful in the case where the :ref:`existing records need to be updated <essentials/update-data>`. This works like a filter. Leaving the box unticked, gives many more field options because it shows all the fields, not just the ones that can be imported."
|
||||
#: ../../content/applications/essentials/export_import_data.rst:37
|
||||
msgid "With the :guilabel:`I want to update data (import-compatable export)` option ticked, the system only shows the fields that can be imported. This is helpful in the case where the :ref:`existing records need to be updated <essentials/update-data>`. This works like a filter. Leaving the box unticked, gives many more field options because it shows all the fields, not only the ones that can be imported."
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/applications/essentials/export_import_data.rst:46
|
||||
#: ../../content/applications/essentials/export_import_data.rst:42
|
||||
msgid "When exporting, there is the option to export in two formats: `.csv` and `.xls`. With `.csv`, items are separated by a comma, while `.xls` holds information about all the worksheets in a file, including both content and formatting."
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/applications/essentials/export_import_data.rst:45
|
||||
msgid "These are the items that can be exported. Use the :icon:`fa-chevron-right` :guilabel:`(Show sub-fields)` icon to display more sub-field options. Use the :guilabel:`Search` bar to find specific fields. To use the :guilabel:`Search` option more efficiently, click on all the :icon:`fa-chevron-right` :guilabel:`(Show sub-fields)` icon to display all fields."
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/applications/essentials/export_import_data.rst:49
|
||||
msgid "These are the items that can be exported. Use the :guilabel:`> (right arrow)` icon to display more sub-field options. Use the :guilabel:`Search` bar to find specific fields. To use the :guilabel:`Search` option more efficiently, click on all the :guilabel:`> (right arrows)` to display all fields."
|
||||
msgid "The :icon:`fa-plus` :guilabel:`(Select field)` icon button is present to add fields to the :guilabel:`Fields to export` list."
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/applications/essentials/export_import_data.rst:53
|
||||
msgid "The :guilabel:`+ (plus sign)` icon button is present to add fields to the :guilabel:`Fields to export` list."
|
||||
#: ../../content/applications/essentials/export_import_data.rst:51
|
||||
msgid "The :icon:`fa-sort` :guilabel:`(Sort)` icon to the left of the selected fields can be used to move the fields up and down, to change the order in which they are displayed in the exported file. Drag-and-drop using the :icon:`fa-sort` :guilabel:`(Sort)` icon."
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/applications/essentials/export_import_data.rst:55
|
||||
msgid "The :guilabel:`↕️ (up-down arrow)` to the left of the selected fields can be used to move the fields up and down, to change the order in which they are displayed in the exported file. Drag-and-drop using the :guilabel:`↕️ (up-down arrow)` icon."
|
||||
#: ../../content/applications/essentials/export_import_data.rst:54
|
||||
msgid "The :icon:`fa-trash` :guilabel:`(Remove field)` icon is used to remove fields. Click the :icon:`fa-trash` :guilabel:`(Remove field)` icon to remove the field."
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/applications/essentials/export_import_data.rst:58
|
||||
msgid "The :guilabel:`🗑️ (trash can)` icon is used to remove fields. Click on the :guilabel:`🗑️ (trash can)` icon to remove the field."
|
||||
#: ../../content/applications/essentials/export_import_data.rst:56
|
||||
msgid "For recurring reports, it is helpful to save export presets. Select all the needed fields, and click on the template drop-down menu. Once there, click on :guilabel:`New template`, and give a unique name to the export template. Click the :icon:`fa-floppy-o` :guilabel:`(floppy drive)` icon to save the configuration. The next time the same list needs to be exported, select the related template that was previously saved from the drop-down menu."
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/applications/essentials/export_import_data.rst:60
|
||||
msgid "For recurring reports, it is helpful to save export presets. Select all the needed fields, and click on the template drop-down menu. Once there, click on :guilabel:`New template`, and give a unique name to the export just created. Click the :guilabel:`💾 (floppy drive)` icon to save the configuration. The next time the same list needs to be exported, select the related template that was previously saved from the drop-down menu."
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/applications/essentials/export_import_data.rst:67
|
||||
#: ../../content/applications/essentials/export_import_data.rst:63
|
||||
msgid "It is helpful to know the field's external identifier. For example, :guilabel:`Related Company` in the export user interface is equal to *parent_id* (external identifier). This is helpful because then, the only data exported is what should be modified and re-imported."
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/applications/essentials/export_import_data.rst:74
|
||||
#: ../../content/applications/essentials/export_import_data.rst:70
|
||||
msgid "Import data into Odoo"
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/applications/essentials/export_import_data.rst:76
|
||||
#: ../../content/applications/essentials/export_import_data.rst:72
|
||||
msgid "Importing data into Odoo is extremely helpful during implementation, or in times where data needs to be :ref:`updated in bulk <essentials/update-data>`. The following documentation covers how to import data into an Odoo database."
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/applications/essentials/export_import_data.rst:81
|
||||
#: ../../content/applications/essentials/export_import_data.rst:77
|
||||
msgid "Imports are permanent and **cannot** be undone. However, it is possible to use filters (`created on` or `last modified`) to identify records changed or created by the import."
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/applications/essentials/export_import_data.rst:85
|
||||
#: ../../content/applications/essentials/export_import_data.rst:81
|
||||
msgid "Activating :ref:`developer mode <developer-mode>` changes the visible import settings in the left menu. Doing so reveals an :menuselection:`Advanced` menu. Included in this advanced menu are two options: :guilabel:`Track history during import` and :guilabel:`Allow matching with subfields`."
|
||||
msgstr ""
|
||||
|
||||
@@ -987,35 +987,35 @@ msgstr ""
|
||||
msgid "Advanced import options when developer mode is activated."
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/applications/essentials/export_import_data.rst:93
|
||||
#: ../../content/applications/essentials/export_import_data.rst:88
|
||||
msgid "If the model uses openchatter, the :guilabel:`Track history during import` option sets up subscriptions and sends notifications during the import, but leads to a slower import."
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/applications/essentials/export_import_data.rst:96
|
||||
#: ../../content/applications/essentials/export_import_data.rst:91
|
||||
msgid "Should the :guilabel:`Allow matching with subfields` option be selected, then all subfields within a field are used to match under the :guilabel:`Odoo Field` while importing."
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/applications/essentials/export_import_data.rst:100
|
||||
#: ../../content/applications/essentials/export_import_data.rst:95
|
||||
msgid "Get started"
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/applications/essentials/export_import_data.rst:102
|
||||
#: ../../content/applications/essentials/export_import_data.rst:97
|
||||
msgid "Data can be imported on any Odoo business object using either Excel (`.xlsx`) or :abbr:`CSV (Comma-separated Values)` (`.csv`) formats. This includes: contacts, products, bank statements, journal entries, and orders."
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/applications/essentials/export_import_data.rst:106
|
||||
msgid "Open the view of the object to which the data should be imported/populated, and click on :menuselection:`⚙️ (Action) --> Import records`."
|
||||
#: ../../content/applications/essentials/export_import_data.rst:101
|
||||
msgid "Open the view of the object to which the data should be imported/populated, click on :icon:`fa-cog` :guilabel:`(Action)` icon, and in the drop-down menu select :icon:`fa-upload` :guilabel:`(Import records)`."
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/applications/essentials/export_import_data.rst:-1
|
||||
msgid "Action menu revealed with the import records option highlighted."
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/applications/essentials/export_import_data.rst:113
|
||||
#: ../../content/applications/essentials/export_import_data.rst:108
|
||||
msgid "After clicking :guilabel:`Import records`, Odoo reveals a separate page with templates that can be downloaded and populated with the company's own data. Such templates can be imported in one click, since the data mapping is already done. To download a template click :guilabel:`Import Template for Customers` at the center of the page."
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/applications/essentials/export_import_data.rst:119
|
||||
#: ../../content/applications/essentials/export_import_data.rst:114
|
||||
msgid "When importing a :abbr:`CSV (Comma-separated Values)` file, Odoo provides :guilabel:`Formatting` options. These options do **not** appear when importing the proprietary Excel file type (`.xls`, `.xlsx`)."
|
||||
msgstr ""
|
||||
|
||||
@@ -1023,31 +1023,31 @@ msgstr ""
|
||||
msgid "Formatting options presented when a CVS file is imported in Odoo."
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/applications/essentials/export_import_data.rst:127
|
||||
#: ../../content/applications/essentials/export_import_data.rst:121
|
||||
msgid "Make necessary adjustments to the *Formatting* options, and ensure all columns in the :guilabel:`Odoo field` and :guilabel:`File Column` are free of errors. Finally, click :guilabel:`Import` to import the data."
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/applications/essentials/export_import_data.rst:132
|
||||
#: ../../content/applications/essentials/export_import_data.rst:126
|
||||
msgid "Adapt a template"
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/applications/essentials/export_import_data.rst:134
|
||||
#: ../../content/applications/essentials/export_import_data.rst:128
|
||||
msgid "Import templates are provided in the import tool of the most common data to import (contacts, products, bank statements, etc.). Open them with any spreadsheet software (*Microsoft Office*, *OpenOffice*, *Google Drive*, etc.)."
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/applications/essentials/export_import_data.rst:138
|
||||
#: ../../content/applications/essentials/export_import_data.rst:132
|
||||
msgid "Once the template is downloaded, proceed to follow these steps:"
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/applications/essentials/export_import_data.rst:140
|
||||
#: ../../content/applications/essentials/export_import_data.rst:134
|
||||
msgid "Add, remove, and sort columns to best fit the data structure."
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/applications/essentials/export_import_data.rst:141
|
||||
#: ../../content/applications/essentials/export_import_data.rst:135
|
||||
msgid "It is strongly advised to **not** remove the :guilabel:`External ID` (ID) column (see why in the next section)."
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/applications/essentials/export_import_data.rst:143
|
||||
#: ../../content/applications/essentials/export_import_data.rst:137
|
||||
msgid "Set a unique ID to every record by dragging down the ID sequencing in the :guilabel:`External ID` (ID) column."
|
||||
msgstr ""
|
||||
|
||||
@@ -1055,7 +1055,7 @@ msgstr ""
|
||||
msgid "An animation of the mouse dragging down the ID column, so each record has a unique ID."
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/applications/essentials/export_import_data.rst:151
|
||||
#: ../../content/applications/essentials/export_import_data.rst:144
|
||||
msgid "When a new column is added, Odoo may not be able to map it automatically, if its label does not fit any field within Odoo. However, new columns can be mapped manually when the import is tested. Search the drop-down menu for the corresponding field."
|
||||
msgstr ""
|
||||
|
||||
@@ -1063,63 +1063,63 @@ msgstr ""
|
||||
msgid "Drop-down menu expanded in the initial import screen on Odoo."
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/applications/essentials/export_import_data.rst:159
|
||||
#: ../../content/applications/essentials/export_import_data.rst:151
|
||||
msgid "Then, use this field's label in the import file to ensure future imports are successful."
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/applications/essentials/export_import_data.rst:162
|
||||
msgid "Another useful way to find out the proper column names to import is to export a sample file using the fields that should be imported. This way, if there is not a sample import template, the names are accurate."
|
||||
#: ../../content/applications/essentials/export_import_data.rst:154
|
||||
msgid "Another useful way to find out the proper column names to import is to export a sample file using the fields to be imported. This way, if there is not a sample import template, the names are accurate."
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/applications/essentials/export_import_data.rst:170
|
||||
#: ../../content/applications/essentials/export_import_data.rst:162
|
||||
msgid "Import from another application"
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/applications/essentials/export_import_data.rst:172
|
||||
msgid "The :guilabel:`External ID` (ID) is a unique identifier for the line item. Feel free to use one from previous software to facilitate the transition to Odoo."
|
||||
#: ../../content/applications/essentials/export_import_data.rst:164
|
||||
msgid "The :guilabel:`External ID` (ID) is a unique identifier for a line item. It is possible to use an :guilabel:`External ID` (ID) from previous software to facilitate the transition to Odoo."
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/applications/essentials/export_import_data.rst:175
|
||||
#: ../../content/applications/essentials/export_import_data.rst:167
|
||||
msgid "Setting an ID is not mandatory when importing, but it helps in many cases:"
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/applications/essentials/export_import_data.rst:177
|
||||
#: ../../content/applications/essentials/export_import_data.rst:169
|
||||
msgid ":ref:`Update imports <essentials/update-data>`: import the same file several times without creating duplicates."
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/applications/essentials/export_import_data.rst:179
|
||||
#: ../../content/applications/essentials/export_import_data.rst:171
|
||||
msgid ":ref:`Import relation fields <export_import_data/relation-fields>`."
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/applications/essentials/export_import_data.rst:181
|
||||
#: ../../content/applications/essentials/export_import_data.rst:173
|
||||
msgid "To recreate relationships between different records, the unique identifier from the original application should be used to map it to the :guilabel:`External ID` (ID) column in Odoo."
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/applications/essentials/export_import_data.rst:184
|
||||
#: ../../content/applications/essentials/export_import_data.rst:176
|
||||
msgid "When another record is imported that links to the first one, use **XXX/ID** (XXX/External ID) for the original unique identifier. This record can also be found using its name."
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/applications/essentials/export_import_data.rst:188
|
||||
#: ../../content/applications/essentials/export_import_data.rst:180
|
||||
msgid "It should be noted that conflicts occur if two (or more) records have the same *External ID*."
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/applications/essentials/export_import_data.rst:191
|
||||
#: ../../content/applications/essentials/export_import_data.rst:183
|
||||
msgid "Field missing to map column"
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/applications/essentials/export_import_data.rst:193
|
||||
#: ../../content/applications/essentials/export_import_data.rst:185
|
||||
msgid "Odoo heuristically tries to find the type of field for each column inside the imported file, based on the first ten lines of the files."
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/applications/essentials/export_import_data.rst:196
|
||||
#: ../../content/applications/essentials/export_import_data.rst:188
|
||||
msgid "For example, if there is a column only containing numbers, only the fields with the *integer* type are presented as options."
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/applications/essentials/export_import_data.rst:199
|
||||
#: ../../content/applications/essentials/export_import_data.rst:191
|
||||
msgid "While this behavior might be beneficial in most cases, it is also possible that it could fail, or the column may be mapped to a field that is not proposed by default."
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/applications/essentials/export_import_data.rst:202
|
||||
#: ../../content/applications/essentials/export_import_data.rst:194
|
||||
msgid "If this happens, check the :guilabel:`Show fields of relation fields (advanced) option`, then a complete list of fields becomes available for each column."
|
||||
msgstr ""
|
||||
|
||||
@@ -1127,359 +1127,359 @@ msgstr ""
|
||||
msgid "Searching for the field to match the tax column."
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/applications/essentials/export_import_data.rst:210
|
||||
#: ../../content/applications/essentials/export_import_data.rst:201
|
||||
msgid "Change data import format"
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/applications/essentials/export_import_data.rst:213
|
||||
#: ../../content/applications/essentials/export_import_data.rst:204
|
||||
msgid "Odoo can automatically detect if a column is a date, and tries to guess the date format from a set of most commonly used date formats. While this process can work for many date formats, some date formats are not recognizable. This can cause confusion, due to day-month inversions; it is difficult to guess which part of a date format is the day, and which part is the month, in a date, such as `01-03-2016`."
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/applications/essentials/export_import_data.rst:219
|
||||
#: ../../content/applications/essentials/export_import_data.rst:210
|
||||
msgid "When importing a :abbr:`CSV (Comma-separated Values)` file, Odoo provides :guilabel:`Formatting` options."
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/applications/essentials/export_import_data.rst:222
|
||||
#: ../../content/applications/essentials/export_import_data.rst:213
|
||||
msgid "To view which date format Odoo has found from the file, check the :guilabel:`Date Format` that is shown when clicking on options under the file selector. If this format is incorrect, change it to the preferred format using *ISO 8601* to define the format."
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/applications/essentials/export_import_data.rst:227
|
||||
msgid "*ISO 8601* is an international standard, covering the worldwide exchange, along with the communication of date and time-related data. For example, the date format should be `YYYY-MM-DD`. So, in the case of July 24th 1981, it should be written as `1981-07-24`."
|
||||
#: ../../content/applications/essentials/export_import_data.rst:218
|
||||
msgid "*ISO 8601* is an international standard, covering the worldwide exchange, along with the communication of date and time-related data. For example, the date format should be `YYYY-MM-DD`. In the case of July 24th 1981, it should be written as `1981-07-24`."
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/applications/essentials/export_import_data.rst:232
|
||||
#: ../../content/applications/essentials/export_import_data.rst:223
|
||||
msgid "When importing Excel files (`.xls`, `.xlsx`), consider using *date cells* to store dates. This maintains locale date formats for display, regardless of how the date is formatted in Odoo. When importing a :abbr:`CSV (Comma-separated Values)` file, use Odoo's :guilabel:`Formatting` section to select the date format columns to import."
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/applications/essentials/export_import_data.rst:238
|
||||
#: ../../content/applications/essentials/export_import_data.rst:229
|
||||
msgid "Import numbers with currency signs"
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/applications/essentials/export_import_data.rst:240
|
||||
#: ../../content/applications/essentials/export_import_data.rst:231
|
||||
msgid "Odoo fully supports numbers with parenthesis to represent negative signs, as well as numbers with currency signs attached to them. Odoo also automatically detects which thousand/decimal separator is used. If a currency symbol unknown to Odoo is used, it might not be recognized as a number, and the import crashes."
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/applications/essentials/export_import_data.rst:246
|
||||
#: ../../content/applications/essentials/export_import_data.rst:237
|
||||
msgid "When importing a :abbr:`CSV (Comma-separated Values)` file, the :guilabel:`Formatting` menu appears on the left-hand column. Under these options, the :guilabel:`Thousands Separator` can be changed."
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/applications/essentials/export_import_data.rst:250
|
||||
#: ../../content/applications/essentials/export_import_data.rst:241
|
||||
msgid "Examples of supported numbers (using 'thirty-two thousand' as the figure):"
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/applications/essentials/export_import_data.rst:252
|
||||
#: ../../content/applications/essentials/export_import_data.rst:243
|
||||
msgid "32.000,00"
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/applications/essentials/export_import_data.rst:253
|
||||
#: ../../content/applications/essentials/export_import_data.rst:244
|
||||
msgid "32000,00"
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/applications/essentials/export_import_data.rst:254
|
||||
#: ../../content/applications/essentials/export_import_data.rst:245
|
||||
msgid "32,000.00"
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/applications/essentials/export_import_data.rst:255
|
||||
#: ../../content/applications/essentials/export_import_data.rst:246
|
||||
msgid "-32000.00"
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/applications/essentials/export_import_data.rst:256
|
||||
#: ../../content/applications/essentials/export_import_data.rst:247
|
||||
msgid "(32000.00)"
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/applications/essentials/export_import_data.rst:257
|
||||
#: ../../content/applications/essentials/export_import_data.rst:248
|
||||
msgid "$ 32.000,00"
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/applications/essentials/export_import_data.rst:258
|
||||
#: ../../content/applications/essentials/export_import_data.rst:249
|
||||
msgid "(32000.00 €)"
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/applications/essentials/export_import_data.rst:260
|
||||
#: ../../content/applications/essentials/export_import_data.rst:251
|
||||
msgid "Example that will not work:"
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/applications/essentials/export_import_data.rst:262
|
||||
#: ../../content/applications/essentials/export_import_data.rst:253
|
||||
msgid "ABC 32.000,00"
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/applications/essentials/export_import_data.rst:263
|
||||
#: ../../content/applications/essentials/export_import_data.rst:254
|
||||
msgid "$ (32.000,00)"
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/applications/essentials/export_import_data.rst:266
|
||||
#: ../../content/applications/essentials/export_import_data.rst:257
|
||||
msgid "A :guilabel:`() (parenthesis)` around the number indicates that the number is a negative value. The currency symbol **must** be placed within the parenthesis for Odoo to recognize it as a negative currency value."
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/applications/essentials/export_import_data.rst:271
|
||||
#: ../../content/applications/essentials/export_import_data.rst:262
|
||||
msgid "Import preview table not displayed correctly"
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/applications/essentials/export_import_data.rst:273
|
||||
#: ../../content/applications/essentials/export_import_data.rst:264
|
||||
msgid "By default, the import preview is set on commas as field separators, and quotation marks as text delimiters. If the :abbr:`CSV (Comma-separated Values)` file does not have these settings, modify the :guilabel:`Formatting` options (displayed under the :guilabel:`Import` :abbr:`CSV (Comma-separated Values)` file bar after selecting the :abbr:`CSV (Comma-separated Values)` file)."
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/applications/essentials/export_import_data.rst:279
|
||||
#: ../../content/applications/essentials/export_import_data.rst:270
|
||||
msgid "If the :abbr:`CSV (Comma-separated Values)` file has a tabulation as a separator, Odoo does **not** detect the separations. The file format options need to be modified in the spreadsheet application. See the following :ref:`Change CSV file format <export_import_data/change-csv>` section."
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/applications/essentials/export_import_data.rst:287
|
||||
#: ../../content/applications/essentials/export_import_data.rst:278
|
||||
msgid "Change CSV file format in spreadsheet application"
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/applications/essentials/export_import_data.rst:289
|
||||
#: ../../content/applications/essentials/export_import_data.rst:280
|
||||
msgid "When editing and saving :abbr:`CSV (Comma-separated Values)` files in spreadsheet applications, the computer's regional settings are applied for the separator and delimiter. Odoo suggests using *OpenOffice* or *LibreOffice*, as both applications allow modifications of all three options (from *LibreOffice* application, go to :menuselection:`'Save As' dialog box --> Check the box 'Edit filter settings' --> Save`)."
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/applications/essentials/export_import_data.rst:295
|
||||
#: ../../content/applications/essentials/export_import_data.rst:286
|
||||
msgid "Microsoft Excel can modify the encoding when saving (:menuselection:`'Save As' dialog box --> 'Tools' drop-down menu --> Encoding tab`)."
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/applications/essentials/export_import_data.rst:299
|
||||
#: ../../content/applications/essentials/export_import_data.rst:290
|
||||
msgid "Difference between Database ID and External ID"
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/applications/essentials/export_import_data.rst:301
|
||||
#: ../../content/applications/essentials/export_import_data.rst:292
|
||||
msgid "Some fields define a relationship with another object. For example, the country of a contact is a link to a record of the 'Country' object. When such fields are imported, Odoo has to recreate links between the different records. To help import such fields, Odoo provides three mechanisms."
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/applications/essentials/export_import_data.rst:306
|
||||
#: ../../content/applications/essentials/export_import_data.rst:297
|
||||
msgid "**Only one** mechanism should be used per field that is imported."
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/applications/essentials/export_import_data.rst:308
|
||||
#: ../../content/applications/essentials/export_import_data.rst:299
|
||||
msgid "For example, to reference the country of a contact, Odoo proposes three different fields to import:"
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/applications/essentials/export_import_data.rst:310
|
||||
#: ../../content/applications/essentials/export_import_data.rst:301
|
||||
msgid ":guilabel:`Country`: the name or code of the country"
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/applications/essentials/export_import_data.rst:311
|
||||
#: ../../content/applications/essentials/export_import_data.rst:302
|
||||
msgid ":guilabel:`Country/Database ID`: the unique Odoo ID for a record, defined by the ID PostgreSQL column"
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/applications/essentials/export_import_data.rst:313
|
||||
#: ../../content/applications/essentials/export_import_data.rst:304
|
||||
msgid ":guilabel:`Country/External ID`: the ID of this record referenced in another application (or the `.XML` file that imported it)"
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/applications/essentials/export_import_data.rst:316
|
||||
#: ../../content/applications/essentials/export_import_data.rst:307
|
||||
msgid "For the country of Belgium, for example, use one of these three ways to import:"
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/applications/essentials/export_import_data.rst:318
|
||||
#: ../../content/applications/essentials/export_import_data.rst:309
|
||||
msgid ":guilabel:`Country`: `Belgium`"
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/applications/essentials/export_import_data.rst:319
|
||||
#: ../../content/applications/essentials/export_import_data.rst:310
|
||||
msgid ":guilabel:`Country/Database ID`: `21`"
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/applications/essentials/export_import_data.rst:320
|
||||
#: ../../content/applications/essentials/export_import_data.rst:311
|
||||
msgid ":guilabel:`Country/External ID`: `base.be`"
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/applications/essentials/export_import_data.rst:322
|
||||
#: ../../content/applications/essentials/export_import_data.rst:313
|
||||
msgid "According to the company's need, use one of these three ways to reference records in relations. Here is an example when one or the other should be used, according to the need:"
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/applications/essentials/export_import_data.rst:325
|
||||
#: ../../content/applications/essentials/export_import_data.rst:316
|
||||
msgid "Use :guilabel:`Country`: this is the easiest way when data comes from :abbr:`CSV (Comma-separated Values)` files that have been created manually."
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/applications/essentials/export_import_data.rst:327
|
||||
#: ../../content/applications/essentials/export_import_data.rst:318
|
||||
msgid "Use :guilabel:`Country/Database ID`: this should rarely be used. It is mostly used by developers as the main advantage is to never have conflicts (there may be several records with the same name, but they always have a unique Database ID)"
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/applications/essentials/export_import_data.rst:330
|
||||
#: ../../content/applications/essentials/export_import_data.rst:321
|
||||
msgid "Use :guilabel:`Country/External ID`: use *External ID* when importing data from a third-party application."
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/applications/essentials/export_import_data.rst:333
|
||||
#: ../../content/applications/essentials/export_import_data.rst:324
|
||||
msgid "When *External IDs* are used, import :abbr:`CSV (Comma-separated Values)` files with the :guilabel:`External ID` (ID) column defining the *External ID* of each record that is imported. Then, a reference can be made to that record with columns, like `Field/External ID`. The following two :abbr:`CSV (Comma-separated Values)` files provide an example for products and their categories."
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/applications/essentials/export_import_data.rst:338
|
||||
#: ../../content/applications/essentials/export_import_data.rst:329
|
||||
msgid ":download:`CSV file for categories <export_import_data/External_id_3rd_party_application_product_categories.csv>`"
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/applications/essentials/export_import_data.rst:340
|
||||
#: ../../content/applications/essentials/export_import_data.rst:331
|
||||
msgid ":download:`CSV file for Products <export_import_data/External_id_3rd_party_application_products.csv>`"
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/applications/essentials/export_import_data.rst:346
|
||||
#: ../../content/applications/essentials/export_import_data.rst:337
|
||||
msgid "Import relation fields"
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/applications/essentials/export_import_data.rst:348
|
||||
#: ../../content/applications/essentials/export_import_data.rst:339
|
||||
msgid "An Odoo object is always related to many other objects (e.g. a product is linked to product categories, attributes, vendors, etc.). To import those relations, the records of the related object need to be imported first, from their own list menu."
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/applications/essentials/export_import_data.rst:352
|
||||
#: ../../content/applications/essentials/export_import_data.rst:343
|
||||
msgid "This can be achieved by using either the name of the related record, or its ID, depending on the circumstances. The ID is expected when two records have the same name. In such a case add `/ ID` at the end of the column title (e.g. for product attributes: `Product Attributes / Attribute / ID`)."
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/applications/essentials/export_import_data.rst:357
|
||||
#: ../../content/applications/essentials/export_import_data.rst:348
|
||||
msgid "Options for multiple matches on fields"
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/applications/essentials/export_import_data.rst:359
|
||||
#: ../../content/applications/essentials/export_import_data.rst:350
|
||||
msgid "If, for example, there are two product categories with the child name `Sellable` (e.g. `Misc. Products/Sellable` & `Other Products/Sellable`), the validation is halted, but the data may still be imported. However, Odoo recommends that the data is not imported because it will all be linked to the first `Sellable` category found in the *Product Category* list (`Misc. Products/Sellable`). Odoo, instead, recommends modifying one of the duplicate's values, or the product category hierarchy."
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/applications/essentials/export_import_data.rst:366
|
||||
#: ../../content/applications/essentials/export_import_data.rst:357
|
||||
msgid "However, if the company does not wish to change the configuration of product categories, Odoo recommends making use of the *External ID* for this field, 'Category'."
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/applications/essentials/export_import_data.rst:370
|
||||
#: ../../content/applications/essentials/export_import_data.rst:361
|
||||
msgid "Import many2many relationship fields"
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/applications/essentials/export_import_data.rst:372
|
||||
#: ../../content/applications/essentials/export_import_data.rst:363
|
||||
msgid "The tags should be separated by a comma, without any spacing. For example, if a customer needs to be linked to both tags: `Manufacturer` and `Retailer` then 'Manufacturer,Retailer' needs to be encoded in the same column of the :abbr:`CSV (Comma-separated Values)` file."
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/applications/essentials/export_import_data.rst:376
|
||||
msgid ":download:`CSV file for Manufacturer, Retailer <export_import_data/m2m_customers_tags.csv>`"
|
||||
#: ../../content/applications/essentials/export_import_data.rst:367
|
||||
msgid ":download:`CSV file for Manufacturer, Retailer <export_import_data/m2m-customers-tags.csv>`"
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/applications/essentials/export_import_data.rst:379
|
||||
#: ../../content/applications/essentials/export_import_data.rst:370
|
||||
msgid "Import one2many relationships"
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/applications/essentials/export_import_data.rst:381
|
||||
#: ../../content/applications/essentials/export_import_data.rst:372
|
||||
msgid "If a company wants to import a sales order with several order lines, a specific row **must** be reserved in the :abbr:`CSV (Comma-separated Values)` file for each order line. The first order line is imported on the same row as the information relative to order. Any additional lines need an additional row that does not have any information in the fields relative to the order."
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/applications/essentials/export_import_data.rst:378
|
||||
msgid "A company imports quotations using a :abbr:`CSV (Comma-separated Values)` file, based on demo data:"
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/applications/essentials/export_import_data.rst:381
|
||||
msgid ":download:`File for some quotations <export_import_data/o2m-quotations-order-lines.csv>`"
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/applications/essentials/export_import_data.rst:383
|
||||
msgid "A company imports purchase orders with their respective purchase order lines using a :abbr:`CSV (Comma-separated Values)` file:"
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/applications/essentials/export_import_data.rst:386
|
||||
msgid "As an example, here is a :abbr:`CSV (Comma-separated Values)` file of some quotations that can be imported, based on demo data:"
|
||||
msgid ":download:`Purchase orders with their respective purchase order lines <export_import_data/o2m-purchase-order-lines.csv>`"
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/applications/essentials/export_import_data.rst:389
|
||||
msgid ":download:`File for some Quotations <export_import_data/purchase.order_functional_error_line_cant_adpat.csv>`"
|
||||
msgid "A company imports customers and their respective contacts using a :abbr:`CSV (Comma-separated Values)` file:"
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/applications/essentials/export_import_data.rst:392
|
||||
msgid "The following :abbr:`CSV (Comma-separated Values)` file shows how to import purchase orders with their respective purchase order lines:"
|
||||
msgid ":download:`Customers and their respective contacts <export_import_data/o2m-customers-contacts.csv>`"
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/applications/essentials/export_import_data.rst:395
|
||||
msgid ":download:`Purchase orders with their respective purchase order lines <export_import_data/o2m_purchase_order_lines.csv>`"
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/applications/essentials/export_import_data.rst:398
|
||||
msgid "The following :abbr:`CSV (Comma-separated Values)` file shows how to import customers and their respective contacts:"
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/applications/essentials/export_import_data.rst:401
|
||||
msgid ":download:`Customers and their respective contacts <export_import_data/o2m_customers_contacts.csv>`"
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/applications/essentials/export_import_data.rst:405
|
||||
#: ../../content/applications/essentials/export_import_data.rst:397
|
||||
msgid "Import records several times"
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/applications/essentials/export_import_data.rst:407
|
||||
#: ../../content/applications/essentials/export_import_data.rst:399
|
||||
msgid "If an imported file contains one of the columns: :guilabel:`External ID` or :guilabel:`Database ID`, records that have already been imported are modified, instead of being created. This is extremely useful as it allows users to import the same :abbr:`CSV (Comma-separated Values)` file several times, while having made some changes in between two imports."
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/applications/essentials/export_import_data.rst:412
|
||||
#: ../../content/applications/essentials/export_import_data.rst:404
|
||||
msgid "Odoo takes care of creating or modifying each record, depending if it is new or not."
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/applications/essentials/export_import_data.rst:414
|
||||
#: ../../content/applications/essentials/export_import_data.rst:406
|
||||
msgid "This feature allows a company to use the *Import/Export tool* in Odoo to modify a batch of records in a spreadsheet application."
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/applications/essentials/export_import_data.rst:418
|
||||
#: ../../content/applications/essentials/export_import_data.rst:410
|
||||
msgid "Value not provided for a specific field"
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/applications/essentials/export_import_data.rst:420
|
||||
msgid "If all fields are not set in the CSV file, Odoo assigns the default value for every non-defined field. But, if fields are set with empty values in the :abbr:`CSV (Comma-separated Values)` file, Odoo sets the empty value in the field, instead of assigning the default value."
|
||||
#: ../../content/applications/essentials/export_import_data.rst:412
|
||||
msgid "If all fields are not set in the CSV file, Odoo assigns the default value for every non-defined field. However, if fields are set with empty values in the :abbr:`CSV (Comma-separated Values)` file, Odoo sets the empty value in the field, instead of assigning the default value."
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/applications/essentials/export_import_data.rst:425
|
||||
#: ../../content/applications/essentials/export_import_data.rst:417
|
||||
msgid "Export/import different tables from an SQL application to Odoo"
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/applications/essentials/export_import_data.rst:427
|
||||
#: ../../content/applications/essentials/export_import_data.rst:419
|
||||
msgid "If data needs to be imported from different tables, relations need to be recreated between records belonging to different tables. For instance, if companies and people are imported, the link between each person and the company they work for needs to be recreated."
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/applications/essentials/export_import_data.rst:431
|
||||
#: ../../content/applications/essentials/export_import_data.rst:423
|
||||
msgid "To manage relations between tables, use the `External ID` facilities of Odoo. The `External ID` of a record is the unique identifier of this record in another application. The `External ID` must be unique across all records of all objects. It is a good practice to prefix this `External ID` with the name of the application or table. (like, 'company_1', 'person_1' - instead of '1')"
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/applications/essentials/export_import_data.rst:436
|
||||
#: ../../content/applications/essentials/export_import_data.rst:428
|
||||
msgid "As an example, suppose there is an SQL database with two tables that are to be imported: companies and people. Each person belongs to one company, so the link between a person and the company they work for must be recreated."
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/applications/essentials/export_import_data.rst:440
|
||||
#: ../../content/applications/essentials/export_import_data.rst:432
|
||||
msgid "Test this example, with a :download:`sample of a PostgreSQL database <export_import_data/database_import_test.sql>`."
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/applications/essentials/export_import_data.rst:443
|
||||
#: ../../content/applications/essentials/export_import_data.rst:435
|
||||
msgid "First, export all companies and their *External ID*. In PSQL, write the following command:"
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/applications/essentials/export_import_data.rst:449
|
||||
#: ../../content/applications/essentials/export_import_data.rst:441
|
||||
msgid "This SQL command creates the following :abbr:`CSV (Comma-separated Values)` file:"
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/applications/essentials/export_import_data.rst:458
|
||||
#: ../../content/applications/essentials/export_import_data.rst:450
|
||||
msgid "To create the :abbr:`CSV (Comma-separated Values)` file for people linked to companies, use the following SQL command in PSQL:"
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/applications/essentials/export_import_data.rst:465
|
||||
#: ../../content/applications/essentials/export_import_data.rst:457
|
||||
msgid "It produces the following :abbr:`CSV (Comma-separated Values)` file:"
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/applications/essentials/export_import_data.rst:475
|
||||
#: ../../content/applications/essentials/export_import_data.rst:467
|
||||
msgid "In this file, Fabien and Laurence are working for the Bigees company (`company_1`), and Eric is working for the Organi company. The relation between people and companies is done using the *External ID* of the companies. The *External ID* is prefixed by the name of the table to avoid a conflict of ID between people and companies (`person_1` and `company_1`, who shared the same ID 1 in the original database)."
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/applications/essentials/export_import_data.rst:481
|
||||
#: ../../content/applications/essentials/export_import_data.rst:473
|
||||
msgid "The two files produced are ready to be imported in Odoo without any modifications. After having imported these two :abbr:`CSV (Comma-separated Values)` files, there are four contacts and three companies (the first two contacts are linked to the first company). Keep in mind to first import the companies, and then the people."
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/applications/essentials/export_import_data.rst:489
|
||||
#: ../../content/applications/essentials/export_import_data.rst:481
|
||||
msgid "Update data in Odoo"
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/applications/essentials/export_import_data.rst:491
|
||||
#: ../../content/applications/essentials/export_import_data.rst:483
|
||||
msgid "Existing data can be updated in bulk through a data import, as long as the :ref:`External ID <essentials/external-id>` remains consistent."
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/applications/essentials/export_import_data.rst:495
|
||||
#: ../../content/applications/essentials/export_import_data.rst:487
|
||||
msgid "Prepare data export"
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/applications/essentials/export_import_data.rst:497
|
||||
msgid "To update data through an import, first navigate to the data to be updated, and select the |list| to activate list view. On the far-left side of the list, tick the checkbox for any record to be updated. Then, click |actions|, and select :icon:`fa-upload` :guilabel:`Export` from the drop-down menu."
|
||||
#: ../../content/applications/essentials/export_import_data.rst:489
|
||||
msgid "To update data through an import, first navigate to the data to be updated, and select the :icon:`oi-view-list` :guilabel:`(List)` icon to activate list view. On the far-left side of the list, tick the checkbox for any record to be updated. Then, click :guilabel:`Actions` button, and select :icon:`fa-upload` :guilabel:`(Export)` from the drop-down menu."
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/applications/essentials/export_import_data.rst:502
|
||||
#: ../../content/applications/essentials/export_import_data.rst:494
|
||||
msgid "On the resulting :guilabel:`Export Data` pop-up window, tick the checkbox labeled, :guilabel:`I want to update data (import-compatible export)`. This automatically includes the *External ID* in the export. Additionally, it limits the :guilabel:`Fields to export` list to **only** include fields that are able to be imported."
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/applications/essentials/export_import_data.rst:508
|
||||
#: ../../content/applications/essentials/export_import_data.rst:500
|
||||
msgid "The :guilabel:`External ID` field does **not** appear in the :guilabel:`Fields to export` list unless it is manually added, but it is still included in the export. However, if the :guilabel:`I want to update data (import-compatible export)` checkbox is ticked, it is included in the export."
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/applications/essentials/export_import_data.rst:512
|
||||
#: ../../content/applications/essentials/export_import_data.rst:504
|
||||
msgid "Select the required fields to be included in the export using the :ref:`options <export-data>` on the pop-up window, then click :guilabel:`Export`."
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/applications/essentials/export_import_data.rst:516
|
||||
#: ../../content/applications/essentials/export_import_data.rst:508
|
||||
msgid "Import updated data"
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/applications/essentials/export_import_data.rst:518
|
||||
#: ../../content/applications/essentials/export_import_data.rst:510
|
||||
msgid "After exporting, make any necessary changes to the data file. When the file is ready, it can be :ref:`imported <import-data>` by following the same process as a normal data import."
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/applications/essentials/export_import_data.rst:522
|
||||
#: ../../content/applications/essentials/export_import_data.rst:514
|
||||
msgid "When updating data, it is extremely important that the *External ID* remain consistent, as this is how the system identifies a record. If an ID is altered, or removed, the system may add a duplicate record, instead of updating the existing one."
|
||||
msgstr ""
|
||||
|
||||
|
||||
File diff suppressed because it is too large
Load Diff
@@ -8,7 +8,7 @@ msgid ""
|
||||
msgstr ""
|
||||
"Project-Id-Version: Odoo 17.0\n"
|
||||
"Report-Msgid-Bugs-To: \n"
|
||||
"POT-Creation-Date: 2025-11-18 10:55+0000\n"
|
||||
"POT-Creation-Date: 2025-12-09 13:40+0000\n"
|
||||
"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
|
||||
"Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
|
||||
"Language-Team: LANGUAGE <LL@li.org>\n"
|
||||
@@ -5568,7 +5568,7 @@ msgid "Odoo is not certified in several countries, including France, Germany, an
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/applications/general/iot/devices/scale.rst:14
|
||||
msgid "To connect a scale to the IoT system, use a USB cable. In some cases, you may need a serial-to-US adapter to complete the connection. If the scale is `compatible with an IoT system <https://www.odoo.com/page/iot-hardware>`_, no additional setup is required; the scale is automatically detected as soon as it is connected. If the scale is not detected, reboot the IoT box or :ref:`restart the Windows virtual IoT service <iot/windows_iot/restart>` and :ref:`update the scale's drivers <iot_updating_iot/handlers>`."
|
||||
msgid "To connect a scale to the IoT system, use a USB cable. In some cases, you may need a serial-to-USB adapter to complete the connection. If the scale is `compatible with an IoT system <https://www.odoo.com/page/iot-hardware>`_, no additional setup is required; the scale is automatically detected as soon as it is connected. If the scale is not detected, reboot the IoT box or :ref:`restart the Windows virtual IoT service <iot/windows_iot/restart>` and :ref:`update the scale's drivers <iot_updating_iot/handlers>`."
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/applications/general/iot/devices/scale.rst:22
|
||||
|
||||
@@ -8,7 +8,7 @@ msgid ""
|
||||
msgstr ""
|
||||
"Project-Id-Version: Odoo 17.0\n"
|
||||
"Report-Msgid-Bugs-To: \n"
|
||||
"POT-Creation-Date: 2025-11-18 10:55+0000\n"
|
||||
"POT-Creation-Date: 2025-12-09 13:40+0000\n"
|
||||
"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
|
||||
"Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
|
||||
"Language-Team: LANGUAGE <LL@li.org>\n"
|
||||
@@ -49,7 +49,7 @@ msgstr ""
|
||||
#: ../../content/applications/sales/crm/acquire_leads/lead_mining.rst:13
|
||||
#: ../../content/applications/sales/crm/optimize/gamification.rst:10
|
||||
#: ../../content/applications/sales/crm/optimize/partner_autocomplete.rst:25
|
||||
#: ../../content/applications/sales/crm/track_leads/lead_scoring.rst:60
|
||||
#: ../../content/applications/sales/crm/track_leads/lead_scoring.rst:59
|
||||
#: ../../content/applications/sales/crm/track_leads/resellers.rst:9
|
||||
#: ../../content/applications/sales/point_of_sale/combos.rst:16
|
||||
#: ../../content/applications/sales/point_of_sale/configuration.rst:6
|
||||
@@ -1771,7 +1771,7 @@ msgid "Add Custom Filters pop-up window with custom filters configured for expec
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/applications/sales/crm/performance/expected_revenue_report.rst:118
|
||||
#: ../../content/applications/sales/crm/performance/forecast_report.rst:85
|
||||
#: ../../content/applications/sales/crm/performance/forecast_report.rst:87
|
||||
#: ../../content/applications/sales/crm/track_leads/unattended_leads_report.rst:145
|
||||
#: ../../content/applications/sales/members/members_analysis.rst:39
|
||||
msgid "View results"
|
||||
@@ -1948,34 +1948,34 @@ msgid "Prorated revenue"
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/applications/sales/crm/performance/forecast_report.rst:52
|
||||
msgid "At the top of the column for each month on the :guilabel:`Forecast` reporting page, to the right of the progress bar, is a sum of the prorated revenue for that time frame."
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/applications/sales/crm/performance/forecast_report.rst:55
|
||||
msgid "The prorated revenue is calculated using the formula below:"
|
||||
msgid "The prorated revenue is the :guilabel:`Expected Revenue` amount that is displayed at the top of the column for each month on the :guilabel:`Forecast` reporting page. This value is situated to the right of the progress bar. The calculation for :guilabel:`Expected Revenue` is the total of the prorated revenue specific to that particular time frame."
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/applications/sales/crm/performance/forecast_report.rst:57
|
||||
msgid "The prorated revenue is calculated using the formula below:"
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/applications/sales/crm/performance/forecast_report.rst:59
|
||||
msgid "\\text{Expected Revenue} \\times \\text{Probability} = \\text{Prorated Revenue}"
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/applications/sales/crm/performance/forecast_report.rst:61
|
||||
#: ../../content/applications/sales/crm/performance/forecast_report.rst:63
|
||||
msgid "As opportunities are moved from one column to another, the column's revenue is automatically updated to reflect the change."
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/applications/sales/crm/performance/forecast_report.rst:65
|
||||
#: ../../content/applications/sales/crm/performance/forecast_report.rst:67
|
||||
msgid "A forecast report for June includes two opportunities:"
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/applications/sales/crm/performance/forecast_report.rst:67
|
||||
#: ../../content/applications/sales/crm/performance/forecast_report.rst:69
|
||||
msgid "The first opportunity, `Global Solutions`, has an expected revenue of `$3,800`, and a probability of `90%`. This results in a prorated revenue of `$3,420`."
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/applications/sales/crm/performance/forecast_report.rst:70
|
||||
#: ../../content/applications/sales/crm/performance/forecast_report.rst:72
|
||||
msgid "The second opportunity, `Quote for 600 Chairs`, has an expected revenue of `$22,500`, and a probability of `20%`. This results in a prorated revenue of `$4,500`."
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/applications/sales/crm/performance/forecast_report.rst:73
|
||||
#: ../../content/applications/sales/crm/performance/forecast_report.rst:75
|
||||
msgid "The combined prorated revenue of the opportunities is `$7,920`, which is listed at the top of the column for the month."
|
||||
msgstr ""
|
||||
|
||||
@@ -1983,11 +1983,11 @@ msgstr ""
|
||||
msgid "An example of the prorated revenue for one month of the forecast report."
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/applications/sales/crm/performance/forecast_report.rst:81
|
||||
#: ../../content/applications/sales/crm/performance/forecast_report.rst:83
|
||||
msgid "For more information on how probability is assigned to opportunities, see :doc:`../track_leads/lead_scoring`"
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/applications/sales/crm/performance/forecast_report.rst:87
|
||||
#: ../../content/applications/sales/crm/performance/forecast_report.rst:89
|
||||
msgid "Click the :icon:`fa-area-chart` :guilabel:`(area chart)` icon to change to graph view. Then, click the corresponding icon at the top of the report to switch to a :icon:`fa-bar-chart` :guilabel:`(bar chart)`, :icon:`fa-line-chart` :guilabel:`(line chart)`, or :icon:`fa-pie-chart` :guilabel:`(pie chart)`."
|
||||
msgstr ""
|
||||
|
||||
@@ -1995,11 +1995,11 @@ msgstr ""
|
||||
msgid "A pie chart view of the Forecast report."
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/applications/sales/crm/performance/forecast_report.rst:96
|
||||
#: ../../content/applications/sales/crm/performance/forecast_report.rst:98
|
||||
msgid "Click the |pivot| to change to the pivot view, or the |list| to change to the list view."
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/applications/sales/crm/performance/forecast_report.rst:99
|
||||
#: ../../content/applications/sales/crm/performance/forecast_report.rst:101
|
||||
#: ../../content/applications/sales/members/members_analysis.rst:49
|
||||
msgid "The :ref:`pivot view <reporting/using-pivot>` can be used to view and analyze data in a more in-depth manner. Multiple measures can be selected, and data can be viewed by month, and by opportunity stage."
|
||||
msgstr ""
|
||||
@@ -2008,7 +2008,7 @@ msgstr ""
|
||||
msgid "A sample of the forecast report in the pivot view."
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/applications/sales/crm/performance/forecast_report.rst:108
|
||||
#: ../../content/applications/sales/crm/performance/forecast_report.rst:110
|
||||
msgid "To save this report as a *favorite*, see :ref:`search/favorites`."
|
||||
msgstr ""
|
||||
|
||||
@@ -3742,7 +3742,7 @@ msgid "Assign leads with predictive lead scoring"
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/applications/sales/crm/track_leads/lead_scoring.rst:5
|
||||
msgid "The Odoo *CRM* app can automatically assign leads/opportunities to sales teams and salespeople. A standard practice is to assign leads based on the probability of winning each lead. Companies can prioritize the leads that are more likely to result in successful deals by quickly assigning them to the appropriate salespeople."
|
||||
msgid "The Odoo **CRM** app can automatically assign leads/opportunities to sales teams and salespeople. A standard practice is to assign leads based on the probability of winning each lead. Companies can prioritize the leads that are more likely to result in successful deals by quickly assigning them to the appropriate salespeople."
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/applications/sales/crm/track_leads/lead_scoring.rst:10
|
||||
@@ -3754,7 +3754,7 @@ msgid "Predictive lead scoring"
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/applications/sales/crm/track_leads/lead_scoring.rst:16
|
||||
msgid "Predictive lead scoring is a machine-learning model that uses historical data from Odoo *CRM* to score open leads/opportunities."
|
||||
msgid "Predictive lead scoring is a machine-learning model that uses historical data from Odoo **CRM** to score open leads/opportunities."
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/applications/sales/crm/track_leads/lead_scoring.rst:19
|
||||
@@ -3813,83 +3813,83 @@ msgstr ""
|
||||
msgid "The probability of success displayed on the opportunity form."
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/applications/sales/crm/track_leads/lead_scoring.rst:54
|
||||
#: ../../content/applications/sales/crm/track_leads/lead_scoring.rst:53
|
||||
msgid "When an opportunity moves to the next stage, its probability of success automatically increases according to the predictive lead scoring algorithm."
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/applications/sales/crm/track_leads/lead_scoring.rst:62
|
||||
msgid "Predictive lead scoring is always active in Odoo *CRM*. However, the variables used to calculate the probability of success can be customized in the settings."
|
||||
#: ../../content/applications/sales/crm/track_leads/lead_scoring.rst:61
|
||||
msgid "Predictive lead scoring is always active in Odoo **CRM**. However, the variables used to calculate the probability of success can be customized in the settings."
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/applications/sales/crm/track_leads/lead_scoring.rst:65
|
||||
#: ../../content/applications/sales/crm/track_leads/lead_scoring.rst:64
|
||||
msgid "To customize the variables used by predictive lead scoring, go to :menuselection:`CRM --> Configuration --> Settings`. Under :guilabel:`Predictive Lead Scoring`, click on the :guilabel:`Update Probabilities` button."
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/applications/sales/crm/track_leads/lead_scoring.rst:69
|
||||
msgid "Then, click on the drop-down menu to choose which variables the predictive lead scoring feature will take into account."
|
||||
#: ../../content/applications/sales/crm/track_leads/lead_scoring.rst:68
|
||||
msgid "Then, click on the drop-down menu to choose which variables the predictive lead scoring feature takes into account."
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/applications/sales/crm/track_leads/lead_scoring.rst:-1
|
||||
msgid "The Update Probabilities window in the Predictive Lead Scoring settings."
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/applications/sales/crm/track_leads/lead_scoring.rst:76
|
||||
#: ../../content/applications/sales/crm/track_leads/lead_scoring.rst:74
|
||||
msgid "Any number of the following variables can be activated:"
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/applications/sales/crm/track_leads/lead_scoring.rst:78
|
||||
#: ../../content/applications/sales/crm/track_leads/lead_scoring.rst:76
|
||||
msgid ":guilabel:`State`: the geographical state from which the opportunity originates"
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/applications/sales/crm/track_leads/lead_scoring.rst:79
|
||||
#: ../../content/applications/sales/crm/track_leads/lead_scoring.rst:77
|
||||
msgid ":guilabel:`Country`: the geographical country from which the opportunity originates"
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/applications/sales/crm/track_leads/lead_scoring.rst:80
|
||||
#: ../../content/applications/sales/crm/track_leads/lead_scoring.rst:78
|
||||
msgid ":guilabel:`Phone Quality`: whether or not a phone number is listed for the opportunity"
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/applications/sales/crm/track_leads/lead_scoring.rst:81
|
||||
#: ../../content/applications/sales/crm/track_leads/lead_scoring.rst:79
|
||||
msgid ":guilabel:`Email Quality`: whether or not an email address is listed for the opportunity"
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/applications/sales/crm/track_leads/lead_scoring.rst:82
|
||||
#: ../../content/applications/sales/crm/track_leads/lead_scoring.rst:80
|
||||
msgid ":guilabel:`Source`: the source of an opportunity (e.g. search engine, social media)"
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/applications/sales/crm/track_leads/lead_scoring.rst:83
|
||||
#: ../../content/applications/sales/crm/track_leads/lead_scoring.rst:81
|
||||
msgid ":guilabel:`Language`: the spoken language specified on the opportunity"
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/applications/sales/crm/track_leads/lead_scoring.rst:84
|
||||
#: ../../content/applications/sales/crm/track_leads/lead_scoring.rst:82
|
||||
msgid ":guilabel:`Tags`: the tags placed on the opportunity"
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/applications/sales/crm/track_leads/lead_scoring.rst:87
|
||||
#: ../../content/applications/sales/crm/track_leads/lead_scoring.rst:85
|
||||
msgid "The variables `Stage` and `Team` are always in effect. `Stage` refers to the CRM pipeline stage that an opportunity is in. `Team` refers to the sales team that is assigned to an opportunity. Predictive lead scoring *always* takes into account these two variables, regardless of which optional variables are selected."
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/applications/sales/crm/track_leads/lead_scoring.rst:92
|
||||
msgid "Next, click on the date field next to the option :guilabel:`Consider leads created as of the:` to select the date from which predictive lead scoring will begin its calculations."
|
||||
#: ../../content/applications/sales/crm/track_leads/lead_scoring.rst:90
|
||||
msgid "Next, click on the date field next to the option :guilabel:`Consider leads created as of the:` to select the date from which predictive lead scoring begins its calculations."
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/applications/sales/crm/track_leads/lead_scoring.rst:95
|
||||
#: ../../content/applications/sales/crm/track_leads/lead_scoring.rst:93
|
||||
msgid "Lastly, click :guilabel:`Confirm` to save changes."
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/applications/sales/crm/track_leads/lead_scoring.rst:98
|
||||
#: ../../content/applications/sales/crm/track_leads/lead_scoring.rst:96
|
||||
msgid "Change the probability manually"
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/applications/sales/crm/track_leads/lead_scoring.rst:100
|
||||
#: ../../content/applications/sales/crm/track_leads/lead_scoring.rst:98
|
||||
msgid "An opportunity's probability of success can be changed manually on the opportunity form. Click on the probability number to edit it."
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/applications/sales/crm/track_leads/lead_scoring.rst:104
|
||||
msgid "Manually changing the probability removes the automatic probability updates for that opportunity. The probability will no longer update automatically as the opportunity moves through each stage of the pipeline."
|
||||
#: ../../content/applications/sales/crm/track_leads/lead_scoring.rst:102
|
||||
msgid "Manually changing the probability removes the automatic probability updates for that opportunity. The probability no longer automatically updates as the opportunity moves through each stage of the pipeline."
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/applications/sales/crm/track_leads/lead_scoring.rst:108
|
||||
#: ../../content/applications/sales/crm/track_leads/lead_scoring.rst:106
|
||||
msgid "To reactivate automatic probability, click on the gear icon next to the probability percentage."
|
||||
msgstr ""
|
||||
|
||||
@@ -3897,67 +3897,67 @@ msgstr ""
|
||||
msgid "The gear icon used to reactivate automatic probability on an opportunity form."
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/applications/sales/crm/track_leads/lead_scoring.rst:115
|
||||
#: ../../content/applications/sales/crm/track_leads/lead_scoring.rst:112
|
||||
msgid "Assign leads based on probability"
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/applications/sales/crm/track_leads/lead_scoring.rst:117
|
||||
msgid "Odoo *CRM* can assign leads/opportunities to sales teams and salespeople based on specified rules. Create assignment rules based on the leads' probability of success to prioritize those that are more likely to result in deals."
|
||||
#: ../../content/applications/sales/crm/track_leads/lead_scoring.rst:114
|
||||
msgid "Odoo **CRM** can assign leads/opportunities to sales teams and salespeople based on specified rules. Create assignment rules based on the leads' probability of success to prioritize those that are more likely to result in leads and opportunities."
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/applications/sales/crm/track_leads/lead_scoring.rst:122
|
||||
#: ../../content/applications/sales/crm/track_leads/lead_scoring.rst:119
|
||||
msgid "Configure rule-based assignment"
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/applications/sales/crm/track_leads/lead_scoring.rst:124
|
||||
#: ../../content/applications/sales/crm/track_leads/lead_scoring.rst:121
|
||||
msgid "To activate *rule-based assignment*, navigate to :menuselection:`CRM --> Configuration --> Settings`, and activate :guilabel:`Rule-Based Assignment`."
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/applications/sales/crm/track_leads/lead_scoring.rst:127
|
||||
msgid "The rule-based assignment feature can be set to run :guilabel:`Manually`, meaning an Odoo user must manually trigger the assignment, or :guilabel:`Repeatedly`, meaning Odoo will automatically trigger the assignment according to the chosen time period."
|
||||
#: ../../content/applications/sales/crm/track_leads/lead_scoring.rst:124
|
||||
msgid "The rule-based assignment feature can be set to run :guilabel:`Manually`, meaning an Odoo user must manually trigger the assignment, or :guilabel:`Repeatedly`, meaning Odoo automatically triggers the assignment according to the chosen time period."
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/applications/sales/crm/track_leads/lead_scoring.rst:131
|
||||
msgid "To set up automatic lead assignment, select :guilabel:`Repeatedly` for the :guilabel:`Running` section. Then, customize how often Odoo will trigger the automatic assignment in the :guilabel:`Repeat every` section."
|
||||
#: ../../content/applications/sales/crm/track_leads/lead_scoring.rst:128
|
||||
msgid "To configure automatic lead assignment, select :guilabel:`Repeatedly` for the :guilabel:`Running` section. The frequency of this automatic assignment is customized within the :guilabel:`Repeat every` section. Enter a specific number and select a corresponding time period to establish the desired interval. Time periods range from :guilabel:`Minutes` to :guilabel:`Weeks`."
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/applications/sales/crm/track_leads/lead_scoring.rst:-1
|
||||
msgid "The Rule-Based Assignment setting in CRM settings."
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/applications/sales/crm/track_leads/lead_scoring.rst:139
|
||||
msgid "If rule-based assignment is set to run :guilabel:`Repeatedly`, the assignment can still be triggered manually using the circular arrow icon in the :guilabel:`Rule-Based Assignment` settings (or using the :guilabel:`Assign Leads` button on the sales team configuration page)."
|
||||
#: ../../content/applications/sales/crm/track_leads/lead_scoring.rst:136
|
||||
msgid "If :guilabel:`rule-based assignment` is set to run :guilabel:`Repeatedly`, the assignment can still be triggered manually using the circular arrow icon in the :guilabel:`Rule-Based Assignment` settings, or using the :guilabel:`Assign Leads` button on the sales team configuration page. Once a lead has been assigned to a salesperson via this rule, the leads are automatically converted into an opportunity by the system."
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/applications/sales/crm/track_leads/lead_scoring.rst:144
|
||||
#: ../../content/applications/sales/crm/track_leads/lead_scoring.rst:143
|
||||
msgid "Configure assignment rules"
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/applications/sales/crm/track_leads/lead_scoring.rst:146
|
||||
msgid "Next, configure the *assignment rules* for each sales team and/or salesperson. These rules determine which leads Odoo assigns to which people. To get started, navigate to :menuselection:`CRM --> Configuration --> Sales Teams`, and select a sales team."
|
||||
#: ../../content/applications/sales/crm/track_leads/lead_scoring.rst:145
|
||||
msgid "Next, configure the *assignment rules* for each sales team or salesperson. These rules determine which leads Odoo assigns to which people. To get started, navigate to :menuselection:`CRM --> Configuration --> Sales Teams`, and select a sales team."
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/applications/sales/crm/track_leads/lead_scoring.rst:150
|
||||
#: ../../content/applications/sales/crm/track_leads/lead_scoring.rst:149
|
||||
msgid "On the sales team configuration form, under :guilabel:`Assignment Rules`, click on :guilabel:`Edit Domain` to configure the rules that Odoo uses to determine lead assignment for this sales team. The rules can include anything that may be relevant for this company or team, and any number of rules can be added."
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/applications/sales/crm/track_leads/lead_scoring.rst:155
|
||||
msgid "Click :guilabel:`Add Filter` to start creating assignment rules. Click on the :guilabel:`+` sign on the right of the assignment rule to add another line. Click on the :guilabel:`x` symbol to remove the line."
|
||||
#: ../../content/applications/sales/crm/track_leads/lead_scoring.rst:154
|
||||
msgid "Click :guilabel:`Add Filter` to start creating assignment rules. Click on the :icon:`fa-plus-circle` sign on the right of the assignment rule to add another line. Click on the :guilabel:`x` symbol to remove the line."
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/applications/sales/crm/track_leads/lead_scoring.rst:159
|
||||
#: ../../content/applications/sales/crm/track_leads/lead_scoring.rst:158
|
||||
msgid "To create an assignment rule based on an opportunity's probability of success, click on the far left drop-down menu of an assignment rule line, and select :guilabel:`Probability`."
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/applications/sales/crm/track_leads/lead_scoring.rst:162
|
||||
#: ../../content/applications/sales/crm/track_leads/lead_scoring.rst:161
|
||||
msgid "From the middle drop-down menu, select the desired equation symbol—most likely the symbol for *greater than*, *less than*, *greater than or equal to*, or *less than or equal to*."
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/applications/sales/crm/track_leads/lead_scoring.rst:165
|
||||
#: ../../content/applications/sales/crm/track_leads/lead_scoring.rst:164
|
||||
msgid "In the far right space, enter the desired number value of the probability. Finally, click :guilabel:`Save` to save changes."
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/applications/sales/crm/track_leads/lead_scoring.rst:169
|
||||
#: ../../content/applications/sales/crm/track_leads/lead_scoring.rst:168
|
||||
msgid "To configure an assignment rule such that a sales team receives leads that have a probability of success of 20% or greater, create a :guilabel:`Domain` line that reads: `Probability >= 20`."
|
||||
msgstr ""
|
||||
|
||||
@@ -3965,16 +3965,16 @@ msgstr ""
|
||||
msgid "Sales team domain set to probability greater than or equal to twenty percent."
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/applications/sales/crm/track_leads/lead_scoring.rst:176
|
||||
#: ../../content/applications/sales/crm/track_leads/lead_scoring.rst:174
|
||||
msgid "Separate assignment rules can also be configured for individual team members. From the sales team configuration page, click on a team member in the :guilabel:`Members` tab, then edit the :guilabel:`Domain` section. Click :guilabel:`Save` to save changes."
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/applications/sales/crm/track_leads/lead_scoring.rst:180
|
||||
#: ../../content/applications/sales/crm/track_leads/lead_scoring.rst:178
|
||||
msgid "If automatic lead assignment is configured in the settings, both the sales team and individual team members have the option to :guilabel:`Skip auto assignment`. Check this box to omit a particular sales team or salesperson from being assigned leads automatically by Odoo's rule-based assignment feature. If :guilabel:`Skip auto assignment` is activated, the sales team or salesperson can still be assigned leads manually."
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/applications/sales/crm/track_leads/lead_scoring.rst:186
|
||||
msgid "To manually assign leads to this sales team, click on the :guilabel:`Assign Leads` button at the top of the sales team configuration page. This will assign any leads that are currently unassigned and match this team's specified domain."
|
||||
#: ../../content/applications/sales/crm/track_leads/lead_scoring.rst:184
|
||||
msgid "To manually assign leads to this sales team, click on the :guilabel:`Assign Leads` button at the top of the sales team configuration page. This assigns any leads that are currently unassigned and match this team's specified domain."
|
||||
msgstr ""
|
||||
|
||||
#: ../../content/applications/sales/crm/track_leads/marketing_attribution.rst:3
|
||||
|
||||
Reference in New Issue
Block a user