Odoo Changelog — 2021-03-16

Tuesday, March 16, 2021

25 changes · master

Improvements(2)

Enhancements to existing features

[IMP] utm*: Improve utm campaigns filtering

Coremastermass_mailingutmwebsite_links

The campaign field previously labeled as website-related has been renamed to better reflect that campaigns can be created automatically from multiple sources, not just websites. This improves clarity for users and administrators without changing how UTM campaign filtering or behavior works.

Original PR description

This PR renames the field is_website into is_auto_campaign
for clarity purpose.

The is_website field always meant that the campaigns were created automatically
in some instances. Could be created automatically via a link to the website
or even by simply creating a marketing campaign in marketing_automation.

is_auto_campaign is a better name as it does not wrongly imply that only
the website can generate campaigns automatically, while also pointing
out the automatic generation mechanism.

The utm campaigns behaviour rests unchanged.

--
I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr

#utm#campaigns#marketing#clarity

[IMP] hr_contract_salary: Store wage_with_holidays

PR #17054

Enterprisemasterhr_contract_salary

Salary contracts now store wage amounts that include holidays, making compensation figures easier to reuse consistently. This helps reduce recalculation needs and supports more reliable payroll-related reporting.

#salary#contracts#holidays

Removals(1)

Features or functions removed from Odoo

[REM] website: long-unused views

PR #67634

Coremasterwebsite

Old website templates that have not been used since 2015 were removed. This reduces maintenance clutter without affecting current website functionality.

Original PR description

Usages of the kanban and kanban_contains templates were removed back
in 2015 (4feb82dd490a6e140dc4956cf8009f3484601d95).

#cleanup#website#templates

Other(22)

Miscellaneous changes

[FW][I18N] l10n_cn: export source terms

PR #67871

Coremasterl10n_cn

Forward-Port-Of: odoo/odoo#67848

Original PR description

Forward-Port-Of: odoo/odoo#67848

[FW][FIX] translation overwriting is not working when forced by command line arg --i18n-overwrite

PR #67873

Coremaster

This PR renames the field is_website into is_auto_campaign for clarity purpose. The is_website field always meant that the campaigns were created automatically in some instances. Could be created automatically via a link to the website or even by simply creating a marketing campaign in marketing_automation. is_auto_campaign is a better name as it does not wrongly imply that only the website can generate campaigns automatically, while also pointing out the automatic generation mechanism. The utm campaigns behaviour rests unchanged. -- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr

When syncing Odoo with Google Calendar, if one Odoo event has an attendee with an email address that contains some uppercases, it will lead to undesirable behavior. To reproduce the error: (Need contacts) 1. Create an event - In attendees, adds a new partner PA - The email must be valid and the local-part must contain at least one uppercase (e.g. demoUP@example.com) 2. Sync with Google 3. On Google Calendar, update the event (e.g., add a description) 4. Refresh Odoo Calendar Error: The event is updated, but the attendee has been removed. The error comes from both Google and Odoo. Google Calendar is not case sensitive: if a user creates a meeting on Google Calendar and adds an email address with uppercases, the latter will be converted with lowercases. (On step 3, on Google Calendar, we can notice that PA's email address does not contain any uppercase) On Odoo side, when syncing the event, the module checks the attendees. To do so, it uses email addresses from Odoo (with uppercases) and Google (without uppercases): https://github.com/odoo/odoo/blob/12cb76bdfe7a5affb7580485473be71cfa37658a/addons/google_calendar/models/calendar.py#L105-L114 `email` comes from Google and `attendees_by_emails` from Odoo. Therefore, it will consider the email as a new attendee and will run `find_or_create` to get the associated partner. However, this method uses the normalized email address to find the partner: https://github.com/odoo/odoo/blob/12cb76bdfe7a5affb7580485473be71cfa37658a/addons/mail/models/res_partner.py#L50-L63 Thus, `find_or_create` returns PA and adds the latter to the attendees and partners (even if PA already exists in partners and attendees). After that, the module checks if some attendees must be removed: https://github.com/odoo/odoo/blob/12cb76bdfe7a5affb7580485473be71cfa37658a/addons/google_calendar/models/calendar.py#L115-L120 Again, `odoo_attendee` comes from Odoo and `email` comes from Google. Therefore, it will remove PA from attendees and partners. This explains why: - PA has disappeared - No partner has been created for the email address without uppercase This fix suggests to normalize the Odoo email addresses each they are compared with the Google ones. OPW-2464863 Forward-Port-Of: odoo/odoo#67826

When adding a variant product, if the option "Variant Grid Entry" is enabled, it will reset the delivery date of each purchase order line. To reproduce the error: (Use demo data) 1. In Settings, enable "Variant Grid Entry" 2. Create an RfQ 3. Add the field "Delivery Date" to purchase order line view 4. Add a basic product (e.g. "[FURN_6666] Acoustic Bloc Screens") - Keep its delivery date in mind 5. Add a variant product (e.g. "[E-COM12] Conference Chair (CONFIG)") Error: The delivery date of the first purchase order line has changed for no reason. Moreover, suppose that in step 4, the user defines a specific date: the latter will still be changed after the variant product is added. When adding a product, the delivery date of the purchase order and its lines are recomputed. However, an override of `onchange` ensures that the new delivery date of the lines will be ignored if the `onchange` concerns the field `order_line`. Here is the problem: when using the Variant Grid Entry, the `onchange` concerns the field `grid`. As a result, the new delivery dates are kept. This explains the creation of `_must_delete_date_planned` in this fix. However, when returing the result of an `onchange` linked to `grid`, the result contains the existing lines (on client side) and the new ones (from the Variant Grid Entry). If the field `date_planned` of the new lines is deleted, the client will raise an error when it tries to render these dates (it has no information about their value). Since existing lines are of the form `(0, <client_id>, <values>)`, this fix only deletes `date_planned` field for lines with <client_id> defined. OPW-2454164 Forward-Port-Of: odoo/odoo#67916

Issue - Install "Sales" - Switch to "German" language - Go to Sales -> Products -> Products - Try to filter on "Public Price" is equal to "2,3" Not possible to add decimal point at the end (only in middle of number). Cause In case the 'decimal point' in DB params is not a dot '.', the filter input will be considered as 'text' instead of 'number'. In case of the 'number' type; HTML do already a pre and post processing, including managing decimal point (who, for example, is not included in ev.target.value if last char is a '.'). Unfortunalty, the library is not well working with other language and not supported on every browser, therefore, must use own logic. In case of a 'text' type, the value will be send to 'parseFloat' ,then `parseNumber` will replace decimal_point by dot (also one the issues since needed to display decimal_point according user language), and `Number` will remove the decimal_point in case of '123,' -> '123', and therefore we will not be able to write decimals ( apart of adding the decimal point after writing the whole number...) Solution If user input is well parsed, store parsed value in condition.value and set condition.displayedValue to the input value (and so without updating input value). Else, replace input value with previous value (who should be the condition.DisplayedValue). opw-2463441 Forward-Port-Of: odoo/odoo#67767

Improvements(2)

[IMP] utm*: Improve utm campaigns filtering

[IMP] hr_contract_salary: Store wage_with_holidays

Removals(1)

[REM] website: long-unused views

Other(22)

[FW][I18N] l10n_cn: export source terms

[FW][FIX] translation overwriting is not working when forced by command line arg --i18n-overwrite

Improvements(2)

[IMP] utm*: Improve utm campaigns filtering

[IMP] hr_contract_salary: Store wage_with_holidays

Removals(1)

[REM] website: long-unused views

Other(22)

[FW][I18N] l10n_cn: export source terms

[FW][FIX] translation overwriting is not working when forced by command line arg --i18n-overwrite

[FW][FIX] point_of_sale: tour waits for everything to be loaded

[FW][FIX] web: fix x2many quick edit behaviours

[FW][FIX] website_sale: fix right corner ribbon

[FW][FIX] web: refit the forum UI biography

[FW][FIX] stock: fix _get_matching_bom and replenishement with archived RR

[FW][ADD] l10n_ar: Enable AFIP document types

[FW][FIX] link_tracker: prevent downloading big or non-html files

[FW][FIX] google_calendar: compare with normalized address

[FW][IMP] base: performance improvement when installing a module

[FW][FIX] website_forum: don't show editor image button

[FW][FIX] digest: visibility of digest config section

[FW][FIX] account: sequence in the past after more precise sequence

[FW][FIX] base: tools: float_split_str: avoid traceback when rounding to 0 places and add some test cases

[FW][FIX] purchase,purchase_product_matrix: ignore date planned

[FW][FIX] web: Allow filtering with decimals on price filter

[FW][FIX] web: properly find the scrolling element of zoomed pages

[FW][FIX] account_reports: limit memory used by aged receivable

[FW][FIX] account_asset: Fix falsy currency_id on account_move_line

[FW][FIX] planning: hides the link to the planning doc

[FW]Saas 14.1 salary credit yti