Daily updates from Odoo
Navigate
Branch
Friday, July 22, 2022
13 changes
Enhancements to existing features
Helpdesk team settings now show clearer guidance about who can access a team based on the selected visibility option. This helps administrators understand access rules more easily and grant the right permissions with less confusion.
Original PR description
This commit introduces some information/instructions regarding the access to the helpdesk team depending on what the user has selected for the helpdesk team visibility. This should reduce confusion and thus increase productivity on the user side by making the task of granting access rights more straightforward to the user. task-2917471
This update brings the spreadsheet engine up to date with several fixes that improve formula recalculation, chart formatting, and menu interactions. It also adds support for the TEXT function, helping users format spreadsheet values more flexibly and reducing incorrect results in day-to-day spreadsheet use.
Original PR description
### Contains the following commits: https://github.com/odoo/o-spreadsheet/commit/24204855 [FIX] evaluation: assign correct error for a cell with two consecutive errors…
### Contains the following commits: https://github.com/odoo/o-spreadsheet/commit/24204855 [FIX] evaluation: assign correct error for a cell with two consecutive errors https://github.com/odoo/o-spreadsheet/commit/2d59441f [IMP] spreadsheet: export figure registry https://github.com/odoo/o-spreadsheet/commit/765361db [FIX] Tests: Clean *Registry after tests https://github.com/odoo/o-spreadsheet/commit/1b830e98 [IMP] husky: allow use of pre-commit hook for windows https://github.com/odoo/o-spreadsheet/commit/6306bad9 [FIX] evaluation: re-evaluate async formulas when changing sheets https://github.com/odoo/o-spreadsheet/commit/2b5cf2b4 [FIX] evaluation: re-evaluate errors in other sheets https://github.com/odoo/o-spreadsheet/commit/f3e4efc6 [IMP] Functions: Add `TEXT`function https://github.com/odoo/o-spreadsheet/commit/01f93c8d [FIX] Charts: Set a format on a cell invalidates runtimes https://github.com/odoo/o-spreadsheet/commit/0bf9533f [FIX] formats: use `cell.evaluated.format` https://github.com/odoo/o-spreadsheet/commit/7dd1bc3f [FIX] top_bar: bugged top_bar menu item hitbox https://github.com/odoo/o-spreadsheet/commit/67ec2703 [FIX] spreadhseet: fix link demo data
Resolved issues and error corrections
The guided field service walkthrough now fills in the worksheet before asking the customer to validate and sign the task report. This prevents the tour from stopping midway and helps users complete the process smoothly.
Original PR description
Prior to this commit, the tour was blocking at step `Invite your customer to <b>validate and sign your task report</b>.` as the worksheet was not complete. This commit adds a step in order to ensure that something is written in the worksheet to ensure it gets completed.
A broken image/link reference in the Documents spreadsheet placeholder was corrected after a recent code split. This ensures users see the intended placeholder graphic instead of a missing or incorrect visual.
Code cleanup and technical improvements
This update adapts many Odoo Enterprise apps to work with the newer list, form, and settings screens. It helps preserve day-to-day workflows across accounting, documents, helpdesk, payroll, field service, rentals, VoIP, and Studio as the underlying interface technology changes.
Original PR description
This commit is the enterprise counter part of odoo/odoo#78221. It adapts the enterprise codebase to the activation of wowl list and form views. Co-authored-by: Aaron Bohy <aab@odoo.com> Co-authored-by: Bruno Boi <boi@odoo.com> Co-authored-by: Géry Debongnie <ged@odoo.com> Co-authored-by: Samuel Degueldre <sad@odoo.com> Co-authored-by: Mathieu Duckerts-Antoine <dam@odoo.com> Co-authored-by: Simon Genin (ges) <ges@odoo.com> Co-authored-by: Francois (fge) <fge@odoo.com> Co-authored-by: Michael Mattiello (mcm) <mcm@odoo.com> Co-authored-by: Julien Mougenot <jum@odoo.com> Co-authored-by: Lucas Perais (lpe) <lpe@odoo.com> Co-authored-by: Jorge Pinna Puissant <jpp@odoo.com> Co-authored-by: luvi <luvi@odoo.com>
Miscellaneous changes
With a EU Company setup create an instrastat invoice. Have an invoice line with any quantity and 0 unit price Confirm the invoice The line will be present in the intrastat report, with EXTVAL 0 which is not allowed opw-2668145 Forward-Port-Of: odoo/enterprise#29719 Forward-Port-Of: odoo/enterprise#29608
Original PR description
With a EU Company setup create an instrastat invoice. Have an invoice line with any quantity and 0 unit price Confirm the invoice The line will be present in the intrastat report, with EXTVAL 0 which is not allowed opw-2668145 Forward-Port-Of: odoo/enterprise#29719 Forward-Port-Of: odoo/enterprise#29608
This PR comprises fixes for multiple separate issues present in the ACH files we generate. Although our ACH files passed an ACH validator from a commercial bank and they were used by some customers they still contained mistakes. These were not noticed because each bank implements their own ACH parser with: - different leniency: the validator we used doesn't appear to check any of the Entry Hash fields, - different auto-correcting: parts of our file indicated debits (money leaving the custome
Original PR description
This PR comprises fixes for multiple separate issues present in the ACH files we generate. Although our ACH files passed an ACH validator from a commercial bank and they were used by some customers…
This PR comprises fixes for multiple separate issues present in the ACH files we generate. Although our ACH files passed an ACH validator from a commercial bank and they were used by some customers they still contained mistakes. These were not noticed because each bank implements their own ACH parser with: - different leniency: the validator we used doesn't appear to check any of the Entry Hash fields, - different auto-correcting: parts of our file indicated debits (money leaving the customer's account), but banks would silently interpret them as credits because that's the only flow they support To fix these problems I used better documentation: the [ACH Universal documentation is clearer than most bank's docs and clearer than the official NACHA docs](https://www.treasurysoftware.com/ach/how-do-i-create-an-ach-nacha-file-detailed-file-format.aspx). On top of the ACH validator we used before (which seems quite lenient) I also used [moov.io's ach validator](https://github.com/moov-io/ach), which is more rigorous and found some issues. Validation was also performed by having customers in the linked tickets upload files to their respective banks. opw-2858885 opw-2896315 Forward-Port-Of: odoo/enterprise#29560
Props `isSaving` does not exist. Issue from this commit 63bcbbb Forward-Port-Of: odoo/enterprise#29754
Original PR description
Props `isSaving` does not exist. Issue from this commit 63bcbbb Forward-Port-Of: odoo/enterprise#29754
The special date changerq on l10n_es_full_line_21500 and l10n_es_pymes_line_21500 are incorrect. It says "At the beginning of the period". For example, user wants to extract a mid-term Balance Sheet and P&L. Fiscal year : 01/01/xx up to 12/31/xx Balance Sheet as of 06/30/xx At the beginning means : 06/01/xx While he expects "from the beginning" : 01/01/xx It is not enough to change the special date changer to "from the beginning" or the items on P&L accounts will be double counted in l10n_es_fu
Original PR description
The special date changerq on l10n_es_full_line_21500 and l10n_es_pymes_line_21500 are incorrect. It says "At the beginning of the period". For example, user wants to extract a mid-term Balance Sheet and P&L. Fiscal year : 01/01/xx up to 12/31/xx Balance Sheet as of 06/30/xx At the beginning means : 06/01/xx While he expects "from the beginning" : 01/01/xx It is not enough to change the special date changer to "from the beginning" or the items on P&L accounts will be double counted in l10n_es_full_line_21500 and l10n_es_full_line_21700, respectively "Resultados de ejercicios anteriores" and "Resultado del ejercicio". Adapt the formula of l10n_es_full_line_21500 and l10n_es_pymes_line_21500. opw-2920843 Forward-Port-Of: odoo/enterprise#29697
We provide "helpful" error messages for some of the more typical error codes returned by the OSE. Code 2022 is one of those, which triggers when the partner name does not meet some validation criteria. From testing, it seems that these validation criteria include: - the partner name is at least 2 characters long - the partner name does not contain special characters e.g. a tab. At the moment, our "helpful" error message tells the user to change the partner name to contain at least 2 c
Original PR description
We provide "helpful" error messages for some of the more typical error codes returned by the OSE. Code 2022 is one of those, which triggers when the partner name does not meet some validation criteria. From testing, it seems that these validation criteria include: - the partner name is at least 2 characters long - the partner name does not contain special characters e.g. a tab. At the moment, our "helpful" error message tells the user to change the partner name to contain at least 2 characters. This can be confusing if the problem with the partner name is in fact that it contains a special character. This commit amends the helpful error message so that it suggests the possibility that the partner name contains a special character. See this video where I show reproduction steps -> https://drive.google.com/file/d/1UVuqdo9__yV4Euk6XEn55oHmFAo8691I/view?usp=sharing Forward-Port-Of: odoo/enterprise#29530 Forward-Port-Of: odoo/enterprise#23972
…slips + reorganise a little bit the method to improve the performance by avoid using horrible filtered. Forward-Port-Of: odoo/enterprise#29546
Original PR description
…slips + reorganise a little bit the method to improve the performance by avoid using horrible filtered. Forward-Port-Of: odoo/enterprise#29546
Before this commit, when we try to create a shift from SO form view > hours to plan stat button, the default SOL of type service is not set on shift. So in this commit, pass the id of SOL instead of an object as a default value of `default_sale_line_id`. task-2873238 Forward-Port-Of: odoo/enterprise#29676
Original PR description
Before this commit, when we try to create a shift from SO form view > hours to plan stat button, the default SOL of type service is not set on shift. So in this commit, pass the id of SOL instead of an object as a default value of `default_sale_line_id`. task-2873238 Forward-Port-Of: odoo/enterprise#29676
Now support the addendas with CFDI 4.0. Before this fix: ```<ns0:Addenda xmlns:ns0="http://www.sat.gob.mx/cfd/3">``` After fix: ```<cfdi:Addenda>``` Forward-Port-Of: odoo/enterprise#29618
Original PR description
Now support the addendas with CFDI 4.0. Before this fix: ```<ns0:Addenda xmlns:ns0="http://www.sat.gob.mx/cfd/3">``` After fix: ```<cfdi:Addenda>``` Forward-Port-Of: odoo/enterprise#29618