Daily updates from Odoo
Navigate
Branch
Thursday, January 20, 2022
7 changes
Enhancements to existing features
This update simplifies internal JavaScript model definitions used by Mail Enterprise and Approvals. It reduces duplicated technical configuration, making the code easier to maintain without changing day-to-day user workflows.
Original PR description
* = approvals, mail_enterprise task-2741386
Resolved issues and error corrections
This update refreshes the spreadsheet engine used in Documents and adapts related features so formulas, pivot templates, charts, clipboard actions, and sheet duplication behave more reliably. It reduces errors in everyday spreadsheet work, including translated sheet names, copied formatting, merged-cell pasting, and conditional formatting comparisons.
Original PR description
…mmit odoo/o-spreadsheet@17410e [FIX] cfEditor: avoid pulling html viewport down odoo/o-spreadsheet@d0042d [FIX] sheet: translate sheet names odoo/o-spreadsheet@85f13f [FIX] borders: copy borders as…
…mmit odoo/o-spreadsheet@17410e [FIX] cfEditor: avoid pulling html viewport down odoo/o-spreadsheet@d0042d [FIX] sheet: translate sheet names odoo/o-spreadsheet@85f13f [FIX] borders: copy borders as sparse arrays when duplicating sheet odoo/o-spreadsheet@148e2c [FIX] clipboard: paste merge overwrite content below the merge odoo/o-spreadsheet@fcb183 [FIX] conditional format: correctly compare numbers odoo/o-spreadsheet@102f61 [FIX] clipboard: correctly selected pasted zone outside sheet odoo/o-spreadsheet@6e29f6 [FIX] compiler: Add missing semicolon + code readability odoo/o-spreadsheet@2c25af [FIX] viewport: dispatch valid offset on scroll event odoo/o-spreadsheet@1aac7b [FIX] evaluation:function error for range outside of sheet odoo/o-spreadsheet@d95492 [FIX] o-spreadsheet: uncentred context menu caret icons odoo/o-spreadsheet@bd9b9c [FIX] chart: correctly copy chart when duplicating a sheet odoo/o-spreadsheet@973baf [FIX] *: backport of 'save formula normalized' odoo/o-spreadsheet@ea578b [FIX] normalize: Normalize number and string arguments in functions odoo/o-spreadsheet@b741b5 [FIX] tokenizer: Avoid running huge regex uselessly odoo/o-spreadsheet@76fc9c [FIX] rangeTokenize: avoid enrichedToken when not necessary odoo/o-spreadsheet@72f76a [REF] merge: use Range instead of zone odoo/o-spreadsheet@a075fe [REF] *: remove ui actions in plugins odoo/o-spreadsheet@9eb88a [REF] spreadsheet: move ui actions in parent of spreadsheet odoo/o-spreadsheet@fa1731 [REF] export: normalize formats odoo/o-spreadsheet@a9be0a [IMP] clipboard: copy several selection on the same column [FIX] documents_spreadsheet_bundle: Adapt PivotTemplatePlugin to the normalization Following odoo/o-spreadsheet@ea578b, The parser only supports normalized formulas, we had to adapt the code that converts functions to create/load formulas in templates. [FIX] documents_spreadsheet_bundle: Adapt ui action Following odoo/o-spreadsheet@9eb88a, the ui action should be defined in the parent of spreadsheet
Code cleanup and technical improvements
This updates internal code references so several Odoo Enterprise screens continue to work with the next version of the Owl interface framework. There is no intended change for end users, but it reduces upgrade risk for accounting, documents, and spreadsheet-related features.
Original PR description
Adaptation of all imports from the Owl library to the next version. In the next version of Owl, all exported terms are directly available from the top level object owl. This PR aims to adapt existing imports to this new system. This is done by importing any Owl variable used in files at the top, after the import | require statements. Community: https://github.com/odoo/odoo/pull/82736 -- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
Miscellaneous changes
Before this commit, when the `sectionField` is a Many2one and in at least one record we have False in this sectionField then we have a traceback saying "Bool is not scriptable", the reason is when the m2o field used to group the records is False on a record then `section_field_value = group[section_field][0]` will crash because `group[section_field] = False`. This commit adds a check to be sure the `group[section_field]` is not False before doing this `section_field_value = group[sectio
Original PR description
Before this commit, when the `sectionField` is a Many2one and in at least one record we have False in this sectionField then we have a traceback saying "Bool is not scriptable", the reason is when the m2o field used to group the records is False on a record then `section_field_value = group[section_field][0]` will crash because `group[section_field] = False`. This commit adds a check to be sure the `group[section_field]` is not False before doing this `section_field_value = group[section_field][0]`. Otherwise, we set the `section_field_value` to `group[section_field]` like we do for the other type of fields used as `sectionField`. Related #23096 Forward-Port-Of: odoo/enterprise#23623
### Expected Behaviour When exporting (in import-compatible export mode) data from price variable attribute and then trying to re-import it, price_extra isn't recognized as a field and can't then be imported ### Observed Behaviour Every exportable field in a import-compatible export should be importable ### Reproducibility This bug can be reproduced following these steps: 1. Export the values for an attribute, including the extra prices for each value, in .xlsx 2. Modify (optio
Original PR description
### Expected Behaviour When exporting (in import-compatible export mode) data from price variable attribute and then trying to re-import it, price_extra isn't recognized as a field and can't then be imported ### Observed Behaviour Every exportable field in a import-compatible export should be importable ### Reproducibility This bug can be reproduced following these steps: 1. Export the values for an attribute, including the extra prices for each value, in .xlsx 2. Modify (optional) the extra prices for certain values 3. Import the modified attribute values into the same database ### Problem Root Cause This issue is coming from the fact we limit the recursion in the fields search to a level of 2, where a third level is needed to get the product variable attributes. ### Related Issues/PR - opw-2560929 Forward-Port-Of: odoo/enterprise#23585 Forward-Port-Of: odoo/enterprise#23578
Step to reproduce: - Generate a link to sign FSM report with an access_token - Access the link without being logged in Current Behaviour: - AccessError when generating the pdf to add to chatter-box Behaviour after PR: - No Access Error General note: Sudo grant access to the report but not the linked document, which is not a an issue when logged in but can become once logged out. Same solve previously seen here: Part1 : odoo/odoo@57665a02f7b4cd113f8f40ec47c58a518fe8669c Part2
Original PR description
Step to reproduce: - Generate a link to sign FSM report with an access_token - Access the link without being logged in Current Behaviour: - AccessError when generating the pdf to add to chatter-box Behaviour after PR: - No Access Error General note: Sudo grant access to the report but not the linked document, which is not a an issue when logged in but can become once logged out. Same solve previously seen here: Part1 : odoo/odoo@57665a02f7b4cd113f8f40ec47c58a518fe8669c Part2 : odoo/odoo@61b4b6777d64218f94c51ec839c187fdc7b2034f opw-2722461 Forward-Port-Of: odoo/enterprise#23604 Forward-Port-Of: odoo/enterprise#23573
Since the last update, there were no more credentials for US shipping in the demo data. Since this is not very practical, here are the credentials for US shipping. Since the US account number was requested from the same account as the EU account number, the SiteID as well as the password are the same for the 2 account numbers. These credentials are demo data and need to be considered as such. this is why they are no longer in the data directory, but in the dedicated demo directory. T
Original PR description
Since the last update, there were no more credentials for US shipping in the demo data. Since this is not very practical, here are the credentials for US shipping. Since the US account number was requested from the same account as the EU account number, the SiteID as well as the password are the same for the 2 account numbers. These credentials are demo data and need to be considered as such. this is why they are no longer in the data directory, but in the dedicated demo directory. The packages data on the other hand are really data. All the EU accounts were kept as they were, so that the update of the module does not create any duplicates. This is not ideal because their names are ambiguous - for example `delivery_carrier_dhl_dom` is opposed to `delivery_carrier_dhl_dom_us` and should have been called something like `delivery_carrier_dhl_dom_eu` or `delivery_carrier_dhl_eu_dom`. Forward-Port-Of: odoo/enterprise#23540 Forward-Port-Of: odoo/enterprise#23114