Files
documentation/locale/vi/LC_MESSAGES/essentials.po
T

1653 lines
59 KiB
Plaintext
Raw Normal View History

# SOME DESCRIPTIVE TITLE.
# Copyright (C) Odoo S.A.
# This file is distributed under the same license as the Odoo package.
# FIRST AUTHOR <EMAIL@ADDRESS>, YEAR.
#
# Translators:
# Wil Odoo, 2024
# Thi Huong Nguyen, 2024
#
#, fuzzy
msgid ""
msgstr ""
"Project-Id-Version: Odoo 16.0\n"
"Report-Msgid-Bugs-To: \n"
"POT-Creation-Date: 2024-03-21 15:48+0000\n"
"PO-Revision-Date: 2024-04-04 12:31+0000\n"
"Last-Translator: Thi Huong Nguyen, 2024\n"
"Language-Team: Vietnamese (https://app.transifex.com/odoo/teams/41243/vi/)\n"
"MIME-Version: 1.0\n"
"Content-Type: text/plain; charset=UTF-8\n"
"Content-Transfer-Encoding: 8bit\n"
"Language: vi\n"
"Plural-Forms: nplurals=1; plural=0;\n"
#: ../../content/applications/essentials.rst:3
msgid "Odoo essentials"
msgstr ""
#: ../../content/applications/essentials/activities.rst:3
msgid "Activities"
msgstr "Hoạt động"
#: ../../content/applications/essentials/activities.rst:5
msgid ""
"*Activities* are follow-up tasks tied to a record in an Odoo database. "
"Activities can be scheduled on any page of the database that contains a "
"chatter thread, kanban view, list view, or activities view of an "
"application."
msgstr ""
#: ../../content/applications/essentials/activities.rst:10
msgid "Schedule activities"
msgstr ""
#: ../../content/applications/essentials/activities.rst:12
msgid ""
"One way that activities are created is by clicking the :guilabel:`Schedule "
"Activity` button, located at the top of the *chatter* on any record. On the "
"pop-up window that appears, select an :guilabel:`Activity Type` from the "
"drop-down menu."
msgstr ""
#: ../../content/applications/essentials/activities.rst:17
msgid ""
"Individual applications have a list of *Activity Types* dedicated to that "
"application. For example, to view and edit the activities available for the "
"*CRM* application, go to :menuselection:`CRM app --> Configuration --> "
"Activity Types`."
msgstr ""
#: ../../content/applications/essentials/activities.rst:21
msgid ""
"Enter a title for the activity in the :guilabel:`Summary` field, located in "
"the :guilabel:`Schedule Activity` pop-up window."
msgstr ""
#: ../../content/applications/essentials/activities.rst:24
msgid ""
"To assign the activity to a different user, select a name from the "
":guilabel:`Assigned to` drop-down menu. Otherwise, the user creating the "
"activity is automatically assigned."
msgstr ""
#: ../../content/applications/essentials/activities.rst:27
msgid ""
"Lastly, feel free to add any additional information in the optional "
":guilabel:`Log a note...` field."
msgstr ""
#: ../../content/applications/essentials/activities.rst:30
msgid ""
"The :guilabel:`Due Date` field on the :guilabel:`Schedule Activity` pop-up "
"window auto-populates based on the configuration settings for the selected "
":guilabel:`Activity Type`. However, this date can be changed by selecting a "
"day on the calendar in the :guilabel:`Due Date` field."
msgstr ""
#: ../../content/applications/essentials/activities.rst:34
msgid "Lastly, click one of the following buttons:"
msgstr ""
#: ../../content/applications/essentials/activities.rst:36
msgid ""
":guilabel:`Schedule`: adds the activity to the chatter under "
":guilabel:`Planned activities`."
msgstr ""
#: ../../content/applications/essentials/activities.rst:37
msgid ""
":guilabel:`Mark as Done`: adds the details of the activity to the chatter "
"under :guilabel:`Today`. The activity is not scheduled, it is automatically "
"marked as completed."
msgstr ""
#: ../../content/applications/essentials/activities.rst:39
msgid ""
":guilabel:`Done \\& Schedule Next`: adds the task under :guilabel:`Today` "
"marked as done, and opens a new activity window."
msgstr ""
#: ../../content/applications/essentials/activities.rst:41
msgid ":guilabel:`Discard`: discards any changes made on the pop-up window."
msgstr ""
#: ../../content/applications/essentials/activities.rst-1
#: ../../content/applications/essentials/activities.rst-1
msgid "View of CRM leads and the option to schedule an activity."
msgstr ""
#: ../../content/applications/essentials/activities.rst:47
msgid ""
"Depending on the activity type, the :guilabel:`Schedule` button may be "
"replaced by a :guilabel:`Save` button, or an :guilabel:`Open Calendar` "
"button."
msgstr ""
#: ../../content/applications/essentials/activities.rst:50
msgid ""
"Scheduled activities are added to the chatter for the record under "
":guilabel:`Planned activities`."
msgstr ""
#: ../../content/applications/essentials/activities.rst:55
msgid ""
"Activities can also be scheduled from the kanban, list, or activities view "
"of an application."
msgstr ""
#: ../../content/applications/essentials/activities.rst:59
msgid "Kanban view"
msgstr ""
#: ../../content/applications/essentials/activities.rst:61
msgid ""
"Select a record on which to schedule an activity. Click on the :guilabel:`🕘 "
"(clock)` icon, then :guilabel:`Schedule An Activity`, and proceed to fill "
"out the pop-up form."
msgstr ""
#: ../../content/applications/essentials/activities.rst:0
msgid ""
"Kanban view of the CRM pipeline and the option to schedule an activity."
msgstr ""
#: ../../content/applications/essentials/activities.rst:67
msgid "List view"
msgstr "Xem danh sách"
#: ../../content/applications/essentials/activities.rst:69
msgid ""
"Select a record on which to schedule an activity. Click on the :guilabel:`🕘 "
"(clock)` icon, then :guilabel:`Schedule An Activity`. If the record already "
"has an activity scheduled, the clock icon may be replaced by a :guilabel:`📞 "
"(phone)` or an :guilabel:`✉️ (envelope)` icon."
msgstr ""
#: ../../content/applications/essentials/activities.rst:0
msgid "List view of the CRM pipeline and the option to schedule an activity."
msgstr ""
#: ../../content/applications/essentials/activities.rst:76
msgid "Activity view"
msgstr "Xem hoạt động"
#: ../../content/applications/essentials/activities.rst:78
msgid ""
"To open the activity view for an application, select the :guilabel:`🕘 "
"(clock)` icon from the menu bar anywhere in the database. Select any "
"application from the drop-down menu, and click the :guilabel:`🕘 (clock)` "
"icon for the desired app."
msgstr ""
#: ../../content/applications/essentials/activities.rst:0
msgid ""
"Activity menu drop down with focus on where to open activity view for CRM."
msgstr ""
#: ../../content/applications/essentials/activities.rst:85
msgid ""
"Select a record on which to schedule an activity. Move across the row to "
"find the desired activity type, then click the :guilabel:` (plus sign)`."
msgstr ""
#: ../../content/applications/essentials/activities.rst:0
msgid ""
"Activity view of the CRM pipeline and the option to schedule an activity."
msgstr ""
#: ../../content/applications/essentials/activities.rst:92
msgid ""
"Activity colors, and their relation to an activity's due date, is consistent"
" throughout Odoo, regardless of the activity type, or the view."
msgstr ""
#: ../../content/applications/essentials/activities.rst:95
msgid ""
"Activities that appear in **green** indicate a due date sometime in the "
"future."
msgstr ""
#: ../../content/applications/essentials/activities.rst:96
msgid "**Yellow** indicates that the activity's due date is today."
msgstr ""
#: ../../content/applications/essentials/activities.rst:97
msgid ""
"**Red** indicates that the activity is overdue and the due date has passed."
msgstr ""
#: ../../content/applications/essentials/activities.rst:99
msgid ""
"For example, if an activity is created for a phone call, and the due date "
"passes, the activity appears with a red phone in list view, and a red clock "
"on the kanban view."
msgstr ""
#: ../../content/applications/essentials/activities.rst:103
msgid "View scheduled activities"
msgstr ""
#: ../../content/applications/essentials/activities.rst:105
msgid ""
"To view scheduled activities, open either the :menuselection:`Sales app` or "
":menuselection:`CRM app` and click the :guilabel:`🕘 (clock)` icon, located "
"to the far-right side of the other view options."
msgstr ""
#: ../../content/applications/essentials/activities.rst:108
msgid ""
"Doing so opens the activities menu, showcasing all the scheduled activities "
"for the user, by default. To show all activities for every user, remove the "
":guilabel:`My Pipeline` filter from the :guilabel:`Search...` bar."
msgstr ""
#: ../../content/applications/essentials/activities.rst:112
msgid ""
"To view a consolidated list of activities separated by the application where"
" they were created, and by deadline, click the :guilabel:`🕘 (clock)` icon on"
" the header menu to see the activities for that specific application in a "
"drop-down menu."
msgstr ""
#: ../../content/applications/essentials/activities.rst:116
msgid ""
"The possibility to :guilabel:`Add new note` and :guilabel:`Request a "
"Document` appear at the bottom of this drop-down menu, when the :guilabel:`🕘"
" (clock)` icon on the header menu is clicked."
msgstr ""
#: ../../content/applications/essentials/activities.rst-1
msgid "View of CRM leads page emphasizing the activities menu."
msgstr ""
#: ../../content/applications/essentials/activities.rst:123
msgid "Configure activity types"
msgstr ""
#: ../../content/applications/essentials/activities.rst:125
msgid ""
"To configure the types of activities in the database, go to "
":menuselection:`Settings app --> Discuss --> Activities --> Activity Types`."
msgstr ""
#: ../../content/applications/essentials/activities.rst-1
msgid "View of the settings page emphasizing the menu activity types."
msgstr ""
#: ../../content/applications/essentials/activities.rst:131
msgid ""
"Doing so reveals the :guilabel:`Activity Types` page, where the existing "
"activity types are found."
msgstr ""
#: ../../content/applications/essentials/activities.rst:133
msgid ""
"To edit an existing activity type, select it from the list, then click "
":guilabel:`Edit`. To create a new activity type, click :guilabel:`Create`."
msgstr ""
#: ../../content/applications/essentials/activities.rst:136
msgid ""
"At the top of a blank activity type form, start by choosing a "
":guilabel:`Name` for the new activity type."
msgstr ""
#: ../../content/applications/essentials/activities.rst-1
msgid "New activity type form."
msgstr ""
#: ../../content/applications/essentials/activities.rst:143
msgid "Activity settings"
msgstr ""
#: ../../content/applications/essentials/activities.rst:146
msgid "Action"
msgstr "Hành động"
#: ../../content/applications/essentials/activities.rst:148
msgid ""
"The *Action* field specifies the intent of the activity. Some actions "
"trigger specific behaviors after an activity is scheduled."
msgstr ""
#: ../../content/applications/essentials/activities.rst:151
msgid ""
"If :guilabel:`Upload Document` is selected, a link to upload a document is "
"added directly to the planned activity in the chatter."
msgstr ""
#: ../../content/applications/essentials/activities.rst:153
msgid ""
"If either :guilabel:`Phonecall` or :guilabel:`Meeting` are selected, users "
"have the option to open their calendar to schedule a time for this activity."
msgstr ""
#: ../../content/applications/essentials/activities.rst:155
msgid ""
"If :guilabel:`Request Signature` is selected, a link is added to the planned"
" activity in the chatter that opens a signature request pop-up window."
msgstr ""
#: ../../content/applications/essentials/activities.rst:159
msgid ""
"The actions available to select on an activity type vary, depending on the "
"applications currently installed in the database."
msgstr ""
#: ../../content/applications/essentials/activities.rst:163
msgid "Default user"
msgstr "Người dùng mặc định"
#: ../../content/applications/essentials/activities.rst:165
msgid ""
"To automatically assign this activity to a specific user when this activity "
"type is scheduled, choose a name from the :guilabel:`Default User` drop-down"
" menu. If this field is left blank, the activity is assigned to the user who"
" creates the activity."
msgstr ""
#: ../../content/applications/essentials/activities.rst:170
msgid "Default summary"
msgstr ""
#: ../../content/applications/essentials/activities.rst:172
msgid ""
"To include notes whenever this activity type is created, enter them into the"
" :guilabel:`Default Summary` field."
msgstr ""
#: ../../content/applications/essentials/activities.rst:176
msgid ""
"The information in the :guilabel:`Default User` and :guilabel:`Default "
"Summary` fields are included when an activity is created. However, they can "
"be altered before the activity is scheduled or saved."
msgstr ""
#: ../../content/applications/essentials/activities.rst:181
msgid "Next activity"
msgstr ""
#: ../../content/applications/essentials/activities.rst:183
msgid ""
"To automatically suggest, or trigger, a new activity after an activity has "
"been marked complete, the :guilabel:`Chaining Type` must be set."
msgstr ""
#: ../../content/applications/essentials/activities.rst:187
msgid "Suggest next activity"
msgstr ""
#: ../../content/applications/essentials/activities.rst:189
msgid ""
"In the :guilabel:`Chaining Type` field, select :guilabel:`Suggest Next "
"Activity`. Upon doing so, the field underneath changes to: "
":guilabel:`Suggest`. Click the :guilabel:`Suggest` field drop-down menu to "
"select any activities to recommend as follow-up tasks to this activity type."
msgstr ""
#: ../../content/applications/essentials/activities.rst:193
#: ../../content/applications/essentials/activities.rst:220
msgid ""
"In the :guilabel:`Schedule` field, choose a default deadline for these "
"activities. To do so, configure a desired number of :guilabel:`Days`, "
":guilabel:`Weeks`, or :guilabel:`Months`. Then, decide if it should occur "
":guilabel:`after completion date` or :guilabel:`after previous activity "
"deadline`."
msgstr ""
#: ../../content/applications/essentials/activities.rst:198
#: ../../content/applications/essentials/activities.rst:225
msgid ""
"This :guilabel:`Schedule` field information can be altered before the "
"activity is scheduled."
msgstr ""
#: ../../content/applications/essentials/activities.rst:200
#: ../../content/applications/essentials/activities.rst:227
msgid "When all configurations are complete, click :guilabel:`Save`."
msgstr ""
#: ../../content/applications/essentials/activities.rst-1
msgid "Schedule activity popup with emphasis on recommended activities."
msgstr ""
#: ../../content/applications/essentials/activities.rst:206
msgid ""
"If an activity has the :guilabel:`Chaining Type` set to :guilabel:`Suggest "
"Next Activity`, and has activities listed in the :guilabel:`Suggest` field, "
"users are presented with recommendations for activities as next steps."
msgstr ""
#: ../../content/applications/essentials/activities.rst:211
msgid "Trigger next activity"
msgstr ""
#: ../../content/applications/essentials/activities.rst:213
msgid ""
"Setting the :guilabel:`Chaining Type` to :guilabel:`Trigger Next Activity` "
"immediately launches the next activity once the previous one is completed."
msgstr ""
#: ../../content/applications/essentials/activities.rst:216
msgid ""
"If :guilabel:`Trigger Next Activity` is selected in the :guilabel:`Chaining "
"Type` field, the field beneath changes to: :guilabel:`Trigger`. From the "
":guilabel:`Trigger` field drop-down menu, select the activity that should be"
" launched once this activity is completed."
msgstr ""
#: ../../content/applications/essentials/activities.rst-1
msgid ""
"Schedule new activity popup with emphasis on Done and launch next button."
msgstr ""
#: ../../content/applications/essentials/activities.rst:233
msgid ""
"When an activity has the :guilabel:`Chaining Type` set to :guilabel:`Trigger"
" Next Activity`, marking the activity as `Done` immediately launches the "
"next activity listed in the :guilabel:`Trigger` field."
msgstr ""
#: ../../content/applications/essentials/activities.rst:238
msgid ":doc:`/applications/productivity/discuss`"
msgstr ""
#: ../../content/applications/essentials/activities.rst:239
msgid ":doc:`/applications/productivity/discuss/team_communication`"
msgstr ""
#: ../../content/applications/essentials/export_import_data.rst:3
msgid "Export and import data"
msgstr ""
#: ../../content/applications/essentials/export_import_data.rst:8
msgid "Export data from Odoo"
msgstr ""
#: ../../content/applications/essentials/export_import_data.rst:10
msgid ""
"When working with a database, it sometimes is necessary to export your data "
"in a distinct file. Doing so can help to do reporting over your activities "
"(even if Odoo offers a precise and easy reporting tool with each available "
"application)."
msgstr ""
#: ../../content/applications/essentials/export_import_data.rst:14
msgid ""
"With Odoo, you can export the values from any field in any record. To do so,"
" activate the list view on the items that need to be exported, click on "
"*Action*, and, then, on *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:22
msgid ""
"Pretty simple, this action still comes with some specificities. In fact, "
"when clicking on *Export*, a pop-up window appears with several options for "
"the data to export:"
msgstr ""
#: ../../content/applications/essentials/export_import_data.rst-1
msgid ""
"overview of all the options to take into account when exporting data in Odoo"
msgstr ""
#: ../../content/applications/essentials/export_import_data.rst:30
msgid ""
"With the *I want to update data* option ticked, the system only shows the "
"fields which can be imported. This is very helpful in case you want to "
"update existing records. Basically, this works like a filter. Leaving the "
"box unticked gives way more field options because it shows all the fields, "
"not just the ones which can be imported."
msgstr ""
#: ../../content/applications/essentials/export_import_data.rst:36
msgid ""
"When exporting, you can choose between two formats: .csv and .xls. With "
".csv, items are separated with 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:39
msgid ""
"Those are the items you may want to export. Use the arrows to display more "
"sub-field options. Of course, you can use the search bar to find specific "
"fields more easily. To use the search option more efficiently, display all "
"the fields by clicking on all the arrows!"
msgstr ""
#: ../../content/applications/essentials/export_import_data.rst:44
msgid "The + button is there to add fields to the \"to export\" list."
msgstr ""
#: ../../content/applications/essentials/export_import_data.rst:45
msgid ""
"The \"handles\" next to the selected fields allow you to move the fields up "
"and down to change the order in which they must be displayed in the exported"
" file."
msgstr ""
#: ../../content/applications/essentials/export_import_data.rst:48
msgid "The trashcan is there if you need to remove fields."
msgstr ""
#: ../../content/applications/essentials/export_import_data.rst:49
msgid ""
"For recurring reports, it might be interesting to save export presets. "
"Select all the needed ones and click on the template bar. There, click on "
"*New template* and give a name to yours. The next time you need to export "
"the same list, simply select the related template."
msgstr ""
#: ../../content/applications/essentials/export_import_data.rst:56
msgid ""
"Its good to keep the fields external identifier in mind. For example, "
"*Related Company* is equal to *parent_id*. Doing so helps export only what "
"you would like to import next."
msgstr ""
#: ../../content/applications/essentials/export_import_data.rst:63
msgid "Import data into Odoo"
msgstr ""
#: ../../content/applications/essentials/export_import_data.rst:66
msgid "How to start"
msgstr ""
#: ../../content/applications/essentials/export_import_data.rst:68
msgid ""
"You can import data on any Odoo's business object using either Excel (.xlsx)"
" or CSV (.csv) formats: contacts, products, bank statements, journal entries"
" and even orders!"
msgstr ""
#: ../../content/applications/essentials/export_import_data.rst:72
msgid ""
"Open the view of the object you want to populate and click on "
":menuselection:`Favorites --> Import records`."
msgstr ""
#: ../../content/applications/essentials/export_import_data.rst:78
msgid ""
"There you are provided with templates you can easily populate with your own "
"data. Such templates can be imported in one click; The data mapping is "
"already done."
msgstr ""
#: ../../content/applications/essentials/export_import_data.rst:83
msgid "How to adapt the template"
msgstr ""
#: ../../content/applications/essentials/export_import_data.rst:85
msgid "Add, remove and sort columns to fit at best your data structure."
msgstr ""
#: ../../content/applications/essentials/export_import_data.rst:86
msgid "We advise to not remove the **ID** one (see why in the next section)."
msgstr ""
#: ../../content/applications/essentials/export_import_data.rst:87
#: ../../content/applications/essentials/export_import_data.rst:376
msgid ""
"Set a unique ID to every single record by dragging down the ID sequencing."
msgstr ""
#: ../../content/applications/essentials/export_import_data.rst:92
msgid ""
"When you add a new column, Odoo might not be able to map it automatically if"
" its label doesn't fit any field in Odoo. Don't worry! You can map new "
"columns manually when you test the import. Search the list for the "
"corresponding field."
msgstr ""
#: ../../content/applications/essentials/export_import_data.rst:100
msgid ""
"Then, use this field's label in your file in order to make it work straight "
"on the very next time."
msgstr ""
#: ../../content/applications/essentials/export_import_data.rst:104
msgid "How to import from another application"
msgstr ""
#: ../../content/applications/essentials/export_import_data.rst:106
msgid ""
"In order to re-create relationships between different records, you should "
"use the unique identifier from the original application and map it to the "
"**ID** (External ID) column in Odoo. When you import another record that "
"links to the first one, use **XXX/ID** (XXX/External ID) to the original "
"unique identifier. You can also find this record using its name but you will"
" be stuck if at least 2 records have the same name."
msgstr ""
#: ../../content/applications/essentials/export_import_data.rst:114
msgid ""
"The **ID** will also be used to update the original import if you need to "
"re-import modified data later, it's thus good practice to specify it "
"whenever possible."
msgstr ""
#: ../../content/applications/essentials/export_import_data.rst:120
msgid "I cannot find the field I want to map my column to"
msgstr ""
#: ../../content/applications/essentials/export_import_data.rst:122
msgid ""
"Odoo tries to find with some heuristic, based on the first ten lines of the "
"files, the type of field for each column inside your file. For example if "
"you have a column only containing numbers, only the fields that are of type "
"*Integer* will be displayed for you to choose from. While this behavior "
"might be good and easy for most cases, it is also possible that it goes "
"wrong or that you want to map your column to a field that is not proposed by"
" default."
msgstr ""
#: ../../content/applications/essentials/export_import_data.rst:131
msgid ""
"If that happens, you just have to check the ** Show fields of relation "
"fields (advanced)** option, you will then be able to choose from the "
"complete list of fields for each column."
msgstr ""
#: ../../content/applications/essentials/export_import_data.rst:139
msgid "Where can I change the date import format?"
msgstr ""
#: ../../content/applications/essentials/export_import_data.rst:141
msgid ""
"Odoo can automatically detect if a column is a date, and it will try 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 will not be "
"recognized. 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:147
msgid ""
"To view which date format Odoo has found from your file you can check the "
"**Date Format** that is shown when clicking on **Options** under the file "
"selector. If this format is incorrect you can change it to your liking using"
" the *ISO 8601* to define the format."
msgstr ""
#: ../../content/applications/essentials/export_import_data.rst:152
msgid ""
"If you are importing an excel (.xls, .xlsx) file, you can use date cells to "
"store dates as the display of dates in excel is different from the way it is"
" stored. That way you will be sure that the date format is correct in Odoo "
"whatever your locale date format is."
msgstr ""
#: ../../content/applications/essentials/export_import_data.rst:157
msgid "Can I import numbers with currency sign (e.g.: $32.00)?"
msgstr ""
#: ../../content/applications/essentials/export_import_data.rst:159
msgid ""
"Yes, we fully support numbers with parenthesis to represent negative sign as"
" well as numbers with currency sign attached to them. Odoo also "
"automatically detect which thousand/decimal separator you use (you can "
"change those under **options**). If you use a currency symbol that is not "
"known to Odoo, it might not be recognized as a number though and it will "
"crash."
msgstr ""
#: ../../content/applications/essentials/export_import_data.rst:164
msgid ""
"Examples of supported numbers (using thirty-two thousands as an example):"
msgstr ""
#: ../../content/applications/essentials/export_import_data.rst:166
msgid "32.000,00"
msgstr ""
#: ../../content/applications/essentials/export_import_data.rst:167
msgid "32000,00"
msgstr ""
#: ../../content/applications/essentials/export_import_data.rst:168
msgid "32,000.00"
msgstr ""
#: ../../content/applications/essentials/export_import_data.rst:169
msgid "-32000.00"
msgstr ""
#: ../../content/applications/essentials/export_import_data.rst:170
msgid "(32000.00)"
msgstr ""
#: ../../content/applications/essentials/export_import_data.rst:171
msgid "$ 32.000,00"
msgstr ""
#: ../../content/applications/essentials/export_import_data.rst:172
msgid "(32000.00 €)"
msgstr ""
#: ../../content/applications/essentials/export_import_data.rst:174
msgid "Example that will not work:"
msgstr ""
#: ../../content/applications/essentials/export_import_data.rst:176
msgid "ABC 32.000,00"
msgstr ""
#: ../../content/applications/essentials/export_import_data.rst:177
msgid "$ (32.000,00)"
msgstr ""
#: ../../content/applications/essentials/export_import_data.rst:180
msgid "What can I do when the Import preview table isn't displayed correctly?"
msgstr ""
#: ../../content/applications/essentials/export_import_data.rst:182
msgid ""
"By default the Import preview is set on commas as field separators and "
"quotation marks as text delimiters. If your csv file does not have these "
"settings, you can modify the File Format Options (displayed under the Browse"
" CSV file bar after you select your file)."
msgstr ""
#: ../../content/applications/essentials/export_import_data.rst:186
msgid ""
"Note that if your CSV file has a tabulation as separator, Odoo will not "
"detect the separations. You will need to change the file format options in "
"your spreadsheet application. See the following question."
msgstr ""
#: ../../content/applications/essentials/export_import_data.rst:191
msgid ""
"How can I change the CSV file format options when saving in my spreadsheet "
"application?"
msgstr ""
#: ../../content/applications/essentials/export_import_data.rst:193
msgid ""
"If you edit and save CSV files in spreadsheet applications, your computer's "
"regional settings will be applied for the separator and delimiter. We "
"suggest you use OpenOffice or LibreOffice Calc as they will allow you to "
"modify all three options (in :menuselection:`'Save As' dialog box --> Check "
"the box 'Edit filter settings' --> Save`)."
msgstr ""
#: ../../content/applications/essentials/export_import_data.rst:198
msgid ""
"Microsoft Excel will allow you to modify only the encoding when saving (in "
":menuselection:`'Save As' dialog box --> click 'Tools' dropdown list --> "
"Encoding tab`)."
msgstr ""
#: ../../content/applications/essentials/export_import_data.rst:202
msgid "What's the difference between Database ID and External ID?"
msgstr ""
#: ../../content/applications/essentials/export_import_data.rst:204
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 you"
" want to import such fields, Odoo will have to recreate links between the "
"different records. To help you import such fields, Odoo provides three "
"mechanisms. You must use one and only one mechanism per field you want to "
"import."
msgstr ""
#: ../../content/applications/essentials/export_import_data.rst:209
msgid ""
"For example, to reference the country of a contact, Odoo proposes you 3 "
"different fields to import:"
msgstr ""
#: ../../content/applications/essentials/export_import_data.rst:211
msgid "Country: the name or code of the country"
msgstr ""
#: ../../content/applications/essentials/export_import_data.rst:212
msgid ""
"Country/Database ID: the unique Odoo ID for a record, defined by the ID "
"postgresql column"
msgstr ""
#: ../../content/applications/essentials/export_import_data.rst:213
msgid ""
"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:216
msgid "For the country Belgium, you can use one of these 3 ways to import:"
msgstr ""
#: ../../content/applications/essentials/export_import_data.rst:218
msgid "Country: Belgium"
msgstr ""
#: ../../content/applications/essentials/export_import_data.rst:219
msgid "Country/Database ID: 21"
msgstr ""
#: ../../content/applications/essentials/export_import_data.rst:220
msgid "Country/External ID: base.be"
msgstr ""
#: ../../content/applications/essentials/export_import_data.rst:222
msgid ""
"According to your need, you should use one of these 3 ways to reference "
"records in relations. Here is when you should use one or the other, "
"according to your need:"
msgstr ""
#: ../../content/applications/essentials/export_import_data.rst:225
msgid ""
"Use Country: This is the easiest way when your data come from CSV files that"
" have been created manually."
msgstr ""
#: ../../content/applications/essentials/export_import_data.rst:227
msgid ""
"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)"
msgstr ""
#: ../../content/applications/essentials/export_import_data.rst:230
msgid ""
"Use Country/External ID: Use External ID when you import data from a third "
"party application."
msgstr ""
#: ../../content/applications/essentials/export_import_data.rst:232
msgid ""
"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."
msgstr ""
#: ../../content/applications/essentials/export_import_data.rst:237
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:240
msgid ""
":download:`CSV file for Products "
"<export_import_data/External_id_3rd_party_application_products.csv>`."
msgstr ""
#: ../../content/applications/essentials/export_import_data.rst:244
msgid "What can I do if I have multiple matches for a field?"
msgstr ""
#: ../../content/applications/essentials/export_import_data.rst:246
msgid ""
"If for example you have two product categories with the child name "
"\"Sellable\" (ie. \"Misc. Products/Sellable\" & \"Other "
"Products/Sellable\"), your validation is halted but you may still import "
"your data. However, we recommend you do not import the data because they "
"will all be linked to the first 'Sellable' category found in the Product "
"Category list (\"Misc. Products/Sellable\"). We recommend you modify one of "
"the duplicates' values or your product category hierarchy."
msgstr ""
#: ../../content/applications/essentials/export_import_data.rst:252
msgid ""
"However if you do not wish to change your configuration of product "
"categories, we recommend you use make use of the external ID for this field "
"'Category'."
msgstr ""
#: ../../content/applications/essentials/export_import_data.rst:256
msgid ""
"How can I import a many2many relationship field (e.g. a customer that has "
"multiple tags)?"
msgstr ""
#: ../../content/applications/essentials/export_import_data.rst:258
msgid ""
"The tags should be separated by a comma without any spacing. For example, if"
" you want your customer to be linked to both tags 'Manufacturer' and "
"'Retailer' then you will encode \"Manufacturer,Retailer\" in the same column"
" of your CSV file."
msgstr ""
#: ../../content/applications/essentials/export_import_data.rst:262
msgid ""
":download:`CSV file for Manufacturer, Retailer "
"<export_import_data/m2m_customers_tags.csv>`"
msgstr ""
#: ../../content/applications/essentials/export_import_data.rst:266
msgid ""
"How can I import a one2many relationship (e.g. several Order Lines of a "
"Sales Order)?"
msgstr ""
#: ../../content/applications/essentials/export_import_data.rst:268
msgid ""
"If you want to import sales order having several order lines; for each order"
" line, you need to reserve a specific row in the CSV file. The first order "
"line will be imported on the same row as the information relative to order. "
"Any additional lines will need an additional row that does not have any "
"information in the fields relative to the order. As an example, here is "
"``purchase.order_functional_error_line_cant_adpat.CSV`` file of some "
"quotations you can import, based on demo data."
msgstr ""
#: ../../content/applications/essentials/export_import_data.rst:275
msgid ""
":download:`File for some Quotations "
"<export_import_data/purchase.order_functional_error_line_cant_adpat.csv>`."
msgstr ""
#: ../../content/applications/essentials/export_import_data.rst:277
msgid ""
"The following CSV file shows how to import purchase orders with their "
"respective purchase order lines:"
msgstr ""
#: ../../content/applications/essentials/export_import_data.rst:280
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:282
msgid ""
"The following CSV file shows how to import customers and their respective "
"contacts:"
msgstr ""
#: ../../content/applications/essentials/export_import_data.rst:284
msgid ""
":download:`Customers and their respective contacts "
"<export_import_data/o2m_customers_contacts.csv>`."
msgstr ""
#: ../../content/applications/essentials/export_import_data.rst:287
msgid "Can I import several times the same record?"
msgstr ""
#: ../../content/applications/essentials/export_import_data.rst:289
msgid ""
"If you import a file that contains one of the column \"External ID\" or "
"\"Database ID\", records that have already been imported will be modified "
"instead of being created. This is very useful as it allows you to import "
"several times the same CSV file while having made some changes in between "
"two imports. Odoo will take care of creating or modifying each record "
"depending if it's new or not."
msgstr ""
#: ../../content/applications/essentials/export_import_data.rst:294
msgid ""
"This feature allows you to use the Import/Export tool of Odoo to modify a "
"batch of records in your favorite spreadsheet application."
msgstr ""
#: ../../content/applications/essentials/export_import_data.rst:298
msgid "What happens if I do not provide a value for a specific field?"
msgstr ""
#: ../../content/applications/essentials/export_import_data.rst:300
msgid ""
"If you do not set all fields in your CSV file, Odoo will assign the default "
"value for every non defined fields. But if you set fields with empty values "
"in your CSV file, Odoo will set the EMPTY value in the field, instead of "
"assigning the default value."
msgstr ""
#: ../../content/applications/essentials/export_import_data.rst:305
msgid "How to export/import different tables from an SQL application to Odoo?"
msgstr ""
#: ../../content/applications/essentials/export_import_data.rst:307
msgid ""
"If you need to import data from different tables, you will have to recreate "
"relations between records belonging to different tables. (e.g. if you import"
" companies and persons, you will have to recreate the link between each "
"person and the company they work for)."
msgstr ""
#: ../../content/applications/essentials/export_import_data.rst:311
msgid ""
"To manage relations between tables, you can use the \"External ID\" "
"facilities of Odoo. The \"External ID\" of a record is the unique identifier"
" of this record in another application. This \"External ID\" must be unique "
"across all the records of all objects, so it's 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:317
msgid ""
"As an example, suppose you have a SQL database with two tables you want to "
"import: companies and persons. Each person belong to one company, so you "
"will have to recreate the link between a person and the company he work for."
" (If you want to test this example, here is a :download:`dump of such a "
"PostgreSQL database <export_import_data/database_import_test.sql>`)"
msgstr ""
#: ../../content/applications/essentials/export_import_data.rst:322
msgid ""
"We will first export all companies and their \"External ID\". In PSQL, write"
" the following command:"
msgstr ""
#: ../../content/applications/essentials/export_import_data.rst:328
msgid "This SQL command will create the following CSV file:"
msgstr ""
#: ../../content/applications/essentials/export_import_data.rst:337
msgid ""
"To create the CSV file for persons, linked to companies, we will use the "
"following SQL command in PSQL:"
msgstr ""
#: ../../content/applications/essentials/export_import_data.rst:343
msgid "It will produce the following CSV file:"
msgstr ""
#: ../../content/applications/essentials/export_import_data.rst:353
msgid ""
"As you can see 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 persons and companies is done using the External ID of the "
"companies. We had to prefix the \"External ID\" by the name of the table to "
"avoid a conflict of ID between persons 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:359
msgid ""
"The two files produced are ready to be imported in Odoo without any "
"modifications. After having imported these two CSV files, you will have 4 "
"contacts and 3 companies. (the firsts two contacts are linked to the first "
"company). You must first import the companies and then the persons."
msgstr ""
#: ../../content/applications/essentials/export_import_data.rst:364
msgid "How to adapt an import template"
msgstr ""
#: ../../content/applications/essentials/export_import_data.rst:366
msgid ""
"Import templates are provided in the import tool of the most common data to "
"import (contacts, products, bank statements, etc.). You can open them with "
"any spreadsheets software (Microsoft Office, OpenOffice, Google Drive, "
"etc.)."
msgstr ""
#: ../../content/applications/essentials/export_import_data.rst:372
msgid "How to customize the file"
msgstr ""
#: ../../content/applications/essentials/export_import_data.rst:374
msgid ""
"Remove columns you don't need. We advise to not remove the *ID* one (see why"
" here below)."
msgstr ""
#: ../../content/applications/essentials/export_import_data.rst:381
msgid ""
"When you add a new column, Odoo might not be able to map it automatically if"
" its label doesn't fit any field of the system. If so, find the "
"corresponding field using the search."
msgstr ""
#: ../../content/applications/essentials/export_import_data.rst:388
msgid ""
"Then, use the label you found in your import template in order to make it "
"work straight away the very next time you try to import."
msgstr ""
#: ../../content/applications/essentials/export_import_data.rst:392
msgid "Why an “ID” column"
msgstr ""
#: ../../content/applications/essentials/export_import_data.rst:394
msgid ""
"The **ID** (External ID) is an unique identifier for the line item. Feel "
"free to use the one of your previous software to ease the transition to "
"Odoo."
msgstr ""
#: ../../content/applications/essentials/export_import_data.rst:397
msgid ""
"Setting an ID is not mandatory when importing but it helps in many cases:"
msgstr ""
#: ../../content/applications/essentials/export_import_data.rst:399
msgid ""
"Update imports: you can import the same file several times without creating "
"duplicates;"
msgstr ""
#: ../../content/applications/essentials/export_import_data.rst:400
msgid "Import relation fields (see here below)."
msgstr ""
#: ../../content/applications/essentials/export_import_data.rst:403
msgid "How to import relation fields"
msgstr ""
#: ../../content/applications/essentials/export_import_data.rst:405
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 you need to import the records of the related object first from "
"their own list menu."
msgstr ""
#: ../../content/applications/essentials/export_import_data.rst:409
msgid ""
"You can do it using either the name of the related record or its ID. 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/in_app_purchase.rst:3
msgid "In-App Purchase (IAP)"
msgstr ""
#: ../../content/applications/essentials/in_app_purchase.rst:5
msgid ""
"In-App Purchases (IAP) gives access to additional services through Odoo. For"
" instance, it allows you to send SMS Text Messages or to send Invoices by "
"post directly from your database."
msgstr ""
#: ../../content/applications/essentials/in_app_purchase.rst:11
msgid "Buying Credits"
msgstr ""
#: ../../content/applications/essentials/in_app_purchase.rst:13
msgid ""
"Each IAP Service relies on prepaid credits to work and has its own pricing. "
"To consult your current balance or to recharge your account, go to "
":menuselection:`Settings --> Odoo IAP --> View my Services`."
msgstr ""
#: ../../content/applications/essentials/in_app_purchase.rst:21
msgid ""
"If you are on Odoo Online and have the Enterprise version, you benefit from "
"free credits to test our IAP features."
msgstr ""
#: ../../content/applications/essentials/in_app_purchase.rst:25
msgid "IAP accounts"
msgstr ""
#: ../../content/applications/essentials/in_app_purchase.rst:27
msgid ""
"Credits to use IAP services are stored on IAP accounts, which are specific "
"to each service. By default, IAP accounts are common to all companies, but "
"can be restricted to specific ones. Activate the :ref:`developer mode "
"<developer-mode>`, then go to :menuselection:`Technical Settings --> IAP "
"Account`."
msgstr ""
#: ../../content/applications/essentials/in_app_purchase.rst:36
msgid ""
"An IAP account can be disabled by appending `+disabled` to its token. "
"Reverting this change will re-enable the account."
msgstr ""
#: ../../content/applications/essentials/in_app_purchase.rst:40
msgid "IAP Portal"
msgstr ""
#: ../../content/applications/essentials/in_app_purchase.rst:42
msgid ""
"The IAP Portal is a platform regrouping your IAP Services. It is accessible "
"from :menuselection:`Settings app --> Odoo IAP --> View my Services`. From "
"there, you can view your current balance, recharge your credits and set a "
"reminder when your balance falls below a threshold."
msgstr ""
#: ../../content/applications/essentials/in_app_purchase.rst:50
msgid "Get notified when credits are low"
msgstr ""
#: ../../content/applications/essentials/in_app_purchase.rst:52
msgid ""
"To be notified when its time to recharge your credits, you can go to your "
"IAP Portal through :menuselection:`Settings app --> Odoo IAP --> View my "
"Services`, unfold a service and check the Receive threshold warning option. "
"Then, you can provide a minimum amount of credits and email addresses. Now, "
"every time that the limit is reached, an automatic reminder will be sent by "
"email!"
msgstr ""
#: ../../content/applications/essentials/reporting.rst:3
msgid "Reporting"
msgstr "Báo cáo"
#: ../../content/applications/essentials/reporting.rst:5
msgid ""
"You can find several reports under the :guilabel:`Reporting` menu of most "
"apps that let you analyze and visualize the data of your records."
msgstr ""
#: ../../content/applications/essentials/reporting.rst:11
msgid "Selecting a view"
msgstr ""
#: ../../content/applications/essentials/reporting.rst:13
msgid ""
"Depending on the report, Odoo can display the data in various ways. "
"Sometimes, a unique view fully tailored to the report is available, while "
"several views are available for others. However, two generic views are "
"dedicated to reporting: the graph and pivot views."
msgstr ""
#: ../../content/applications/essentials/reporting.rst:20
msgid "Graph view"
msgstr ""
#: ../../content/applications/essentials/reporting.rst:22
msgid ""
"The :ref:`graph view <reporting/using-graph>` is used to visualize your "
"records' data, helping you identify patterns and trends. The view is often "
"found under the :guilabel:`Reporting` menu of apps but can be found "
"elsewhere. Click the **graph view button** located at the top right to "
"access it."
msgstr ""
#: ../../content/applications/essentials/reporting.rst-1
msgid "Selecting the graph view"
msgstr ""
#: ../../content/applications/essentials/reporting.rst:33
msgid "Pivot view"
msgstr ""
#: ../../content/applications/essentials/reporting.rst:35
msgid ""
"The :ref:`pivot view <reporting/using-pivot>` is used to aggregate your "
"records' data and break it down for analysis. The view is often found under "
"the :guilabel:`Reporting` menu of apps but can be found elsewhere. Click the"
" **pivot view button** located at the top right to access it."
msgstr ""
#: ../../content/applications/essentials/reporting.rst-1
msgid "Selecting the pivot view"
msgstr ""
#: ../../content/applications/essentials/reporting.rst:45
msgid "Choosing measures"
msgstr ""
#: ../../content/applications/essentials/reporting.rst:47
msgid ""
"After selecting a view, you should ensure only the relevant records are "
":doc:`filtered <search>`. Next, you should choose what is measured. By "
"default, a measure is always selected. If you wish to edit it, click "
":guilabel:`Measures` and choose one or, only for pivots, multiple measures."
msgstr ""
#: ../../content/applications/essentials/reporting.rst:52
msgid ""
"When you select a measure, Odoo aggregates the values recorded on that field"
" for the filtered records. Only numerical fields (:ref:`integer "
"<studio/fields/simple-fields/integer>`, :ref:`decimal <studio/fields/simple-"
"fields/decimal>`, :ref:`monetary <studio/fields/simple-fields/monetary>`) "
"can be measured. In addition, the :guilabel:`Count` option is used to count "
"the total number of filtered records."
msgstr ""
#: ../../content/applications/essentials/reporting.rst:58
msgid ""
"After choosing what you want to measure, you can define how the data should "
"be :ref:`grouped <search/group>` depending on the dimension you want to "
"analyze. By default, the data is often grouped by *Date > Month*, which is "
"used to analyze the evolution of a measure over the months."
msgstr ""
#: ../../content/applications/essentials/reporting.rst:63
msgid ""
"When you filter a single time period, the option to compare it against "
"another one appears."
msgstr ""
#: ../../content/applications/essentials/reporting.rst:0
msgid "Using the comparison option"
msgstr ""
#: ../../content/applications/essentials/reporting.rst:72
msgid "Select measures"
msgstr ""
#: ../../content/applications/essentials/reporting.rst:74
msgid ""
"Among other measures, you could add the :guilabel:`Margin` and "
":guilabel:`Count` measures to the Sales Analysis report. By default, the "
":guilabel:`Untaxed Amount` measure is selected."
msgstr ""
#: ../../content/applications/essentials/reporting.rst:0
msgid "Selecting different measures on the Sales Analysis report"
msgstr ""
#: ../../content/applications/essentials/reporting.rst:81
msgid "Group measures"
msgstr ""
#: ../../content/applications/essentials/reporting.rst:83
msgid ""
"You could group the measures by :guilabel:`Product Category` at the level of"
" rows on the previous Sales Analysis report example."
msgstr ""
#: ../../content/applications/essentials/reporting.rst:0
msgid "Adding a group on the Sales Analysis report"
msgstr ""
#: ../../content/applications/essentials/reporting.rst:92
msgid "Using the pivot view"
msgstr ""
#: ../../content/applications/essentials/reporting.rst:94
msgid ""
"Grouping data is quintessential to the pivot view. It enables drilling down "
"the data to gain deeper insights. While you can use the :guilabel:`Group By`"
" option to quickly add a group at the level of rows, as shown in the example"
" above, you can also click the plus button (:guilabel:``) next to the "
":guilabel:`Total` header at the level of rows *and* columns, and then select"
" one of the **preconfigured groups**. To remove one, click the minus button "
"(:guilabel:``)."
msgstr ""
#: ../../content/applications/essentials/reporting.rst:100
msgid ""
"Once you have added a group, you can add new ones on the opposite axis or "
"the newly created subgroups."
msgstr ""
#: ../../content/applications/essentials/reporting.rst:104
msgid ""
"You could further divide the measures on the previous Sales Analysis report "
"example by the :guilabel:`Salesperson` group at the level of columns and by "
"the :guilabel:`Order Date > Month` group on the :guilabel:`All / Saleable / "
"Office Furniture` product category."
msgstr ""
#: ../../content/applications/essentials/reporting.rst:0
msgid "Adding multiple groups on the Sales Analysis report"
msgstr ""
#: ../../content/applications/essentials/reporting.rst:112
msgid ""
"Switch the rows and columns' groups by clicking the flip axis button "
"(:guilabel:`⇄`)."
msgstr ""
#: ../../content/applications/essentials/reporting.rst:113
msgid ""
"Click on a measure's label to sort the values by ascending (⏶) or descending"
" (⏷) order."
msgstr ""
#: ../../content/applications/essentials/reporting.rst:114
msgid ""
"Download a `.xlsx` version of the pivot by clicking the download button "
"(:guilabel:`⭳`)."
msgstr ""
#: ../../content/applications/essentials/reporting.rst:119
msgid "Using the graph view"
msgstr ""
#: ../../content/applications/essentials/reporting.rst:121
msgid "Three graphs are available: the bar, line, and pie charts."
msgstr ""
#: ../../content/applications/essentials/reporting.rst:123
msgid ""
"**Bar charts** are used to show the distribution or a comparison of several "
"categories. They are especially useful as they can deal with larger data "
"sets."
msgstr ""
#: ../../content/applications/essentials/reporting.rst:126
msgid ""
"**Line charts** are useful to show changing time series and trends over "
"time."
msgstr ""
#: ../../content/applications/essentials/reporting.rst:128
msgid ""
"**Pie charts** are used to show the distribution or a comparison of a small "
"number of categories when they form a meaningful whole."
msgstr ""
#: ../../content/applications/essentials/reporting.rst:133
msgid "Bar chart"
msgstr ""
#: ../../content/applications/essentials/reporting.rst:0
msgid "Viewing the Sales Analysis report as a bar chart"
msgstr ""
#: ../../content/applications/essentials/reporting.rst:138
msgid "Line chart"
msgstr ""
#: ../../content/applications/essentials/reporting.rst:0
msgid "Viewing the Sales Analysis report as a line chart"
msgstr ""
#: ../../content/applications/essentials/reporting.rst:143
msgid "Pie chart"
msgstr ""
#: ../../content/applications/essentials/reporting.rst:0
msgid "Viewing the Sales Analysis report as a pie chart"
msgstr ""
#: ../../content/applications/essentials/reporting.rst:149
msgid ""
"For **bar** and **line** charts, you can use the stacked option when you "
"have at least two groups, which then appear on top of each other instead of "
"next to each other."
msgstr ""
#: ../../content/applications/essentials/reporting.rst:154
msgid "Stacked bar chart"
msgstr ""
#: ../../content/applications/essentials/reporting.rst:0
msgid "Stacked bar chart example"
msgstr ""
#: ../../content/applications/essentials/reporting.rst:159
msgid "Regular bar chart"
msgstr ""
#: ../../content/applications/essentials/reporting.rst:0
msgid "Non-stacked bar chart example"
msgstr ""
#: ../../content/applications/essentials/reporting.rst:164
msgid "Stacked line chart"
msgstr ""
#: ../../content/applications/essentials/reporting.rst:0
msgid "Stacked line chart example"
msgstr ""
#: ../../content/applications/essentials/reporting.rst:169
#: ../../content/applications/essentials/reporting.rst:184
msgid "Regular line chart"
msgstr ""
#: ../../content/applications/essentials/reporting.rst:0
msgid "Non-stacked line chart example"
msgstr ""
#: ../../content/applications/essentials/reporting.rst:174
msgid ""
"For **line** charts, you can use the cumulative option to sum values, which "
"is especially useful to show the change in growth over a time period."
msgstr ""
#: ../../content/applications/essentials/reporting.rst:179
msgid "Cumulative line chart"
msgstr ""
#: ../../content/applications/essentials/reporting.rst:0
msgid "Cumulative line chart example"
msgstr ""
#: ../../content/applications/essentials/reporting.rst:0
msgid "Regular line chart example"
msgstr ""
#: ../../content/applications/essentials/search.rst:3
msgid "Search and filter records"
msgstr ""
#: ../../content/applications/essentials/search.rst:5
msgid ""
"Odoo uses filters to include only the most relevant records depending on the"
" purpose of the view you are on. However, you can edit the default filter or"
" search for specific values."
msgstr ""
#: ../../content/applications/essentials/search.rst:11
msgid "Preconfigured filters"
msgstr ""
#: ../../content/applications/essentials/search.rst:13
msgid ""
"You can modify the default selection of records by clicking "
":guilabel:`Filters` and selecting one or several **preconfigured filters**."
msgstr ""
#: ../../content/applications/essentials/search.rst:17
msgid ""
"On the Sales Analysis report, only records at the sales order stage are "
"selected by default. However, you could *also* include records at the "
"quotation stage by selecting :guilabel:`Quotations`. Furthermore, you could "
"*only* include records from a specific year, for example *2022*, by "
"selecting :menuselection:`Order Date --> 2022`."
msgstr ""
#: ../../content/applications/essentials/search.rst:0
msgid "Using preconfigured filters on the Sales Analysis report"
msgstr ""
#: ../../content/applications/essentials/search.rst:27
msgid ""
"If you select preconfigured filters from the same group (i.e., that are "
"*not* separated by an horizontal line), the records can match *any* "
"condition to be included. However, if you select filters from different "
"groups, the records have to match *all* condition to be included."
msgstr ""
#: ../../content/applications/essentials/search.rst:34
msgid "Custom filters"
msgstr ""
#: ../../content/applications/essentials/search.rst:36
msgid ""
"You can create custom filters using most fields present on the model by "
"clicking :menuselection:`Filters --> Add Custom Filter`, selecting a field, "
"an operator, a value, and clicking :guilabel:`Apply`."
msgstr ""
#: ../../content/applications/essentials/search.rst:41
msgid ""
"You could *only* include records from a single salesperson on the Sales "
"Analysis report, for example *Mitchell Admin*, by selecting "
":guilabel:`Salesperson` as the field, :guilabel:`is equal to` as the "
"operator, and typing `Mitchell Admin` as the value."
msgstr ""
#: ../../content/applications/essentials/search.rst:0
msgid "Using a custom filter on the Sales Analysis report"
msgstr ""
#: ../../content/applications/essentials/search.rst:50
msgid ""
"If the records should *only* match one of several conditions, click "
":guilabel:`Add a condition` before applying a custom filter. If the records "
"should match *all* conditions, add new custom filters instead."
msgstr ""
#: ../../content/applications/essentials/search.rst:57
msgid "Search for values"
msgstr ""
#: ../../content/applications/essentials/search.rst:59
msgid ""
"You can use the search field to quickly look for specific values and add "
"them as a filter. Either type the full value you are searching for and "
"select the desired field, or type a part of the value, click the dropdown "
"button (:guilabel:`⏵`) before the chosen field, and select the exact value "
"you are looking for."
msgstr ""
#: ../../content/applications/essentials/search.rst:65
msgid ""
"Instead of adding a custom filter to select records where *Mitchell Admin* "
"is the salesperson on the Sales Analysis report, you could search for "
"`Mitch`, click the dropdown button (:guilabel:`⏵`) next to :guilabel:`Search"
" Salesperson for: Mitch`, and select :guilabel:`Mitchell Admin`."
msgstr ""
#: ../../content/applications/essentials/search.rst:0
msgid "Searching for a specific value on the Sales Analysis report"
msgstr ""
#: ../../content/applications/essentials/search.rst:75
msgid ""
"Using the search field is equivalent to using the *contains* operator when "
"adding a custom filter. If you enter a partial value and directly select the"
" desired field, *all* records containing the characters you typed for the "
"selected field will be included."
msgstr ""
#: ../../content/applications/essentials/search.rst:82
msgid "Group records"
msgstr ""
#: ../../content/applications/essentials/search.rst:84
msgid ""
"You can click :guilabel:`Group By` below the search field to cluster records"
" together according to one of the **preconfigured groups**."
msgstr ""
#: ../../content/applications/essentials/search.rst:88
msgid ""
"You could group the records by salesperson on the Sales Analysis report by "
"clicking :guilabel:`Group By` and selecting :guilabel:`Salesperson`. No "
"records are filtered out."
msgstr ""
#: ../../content/applications/essentials/search.rst:0
msgid "Grouping records on the Sales Analysis report"
msgstr ""
#: ../../content/applications/essentials/search.rst:95
msgid ""
"You can **customize groups** by using a wide selection of fields present on "
"the model. To do so, click :menuselection:`Group By --> Add Custom Group`, "
"select a field, and click :guilabel:`Apply`."
msgstr ""
#: ../../content/applications/essentials/search.rst:99
msgid ""
"You can use several groups at the same time. The first group you select is "
"the main cluster, the next one you add further divides the main group's "
"categories, and so on."
msgstr ""