Thursday, October 7, 2021
11 changes · master
New functionality added to Odoo
Adds an XML export for Mexican accounting journal entries over a selected period. This helps companies meet SAT requirements during audits or when requesting tax refunds or compensation.
Original PR description
This is a legal requirement when one of the 2 following scenarios are given: - The SAT (Mexican government) asks to check the JEs to the company to audit (compulsory). It can happen to any company at some point the bigger the higher the chances of getting asked. Our MX office could be a case that will need this in the future. - When the company asks for compensation or return from the SAT (Government) An export of all Journal Entries from a specific period of time is needed, exported in an XML so later this can be uploaded to the SAT webpage. Target Versions: v14 & Master Task link: https://www.odoo.com/web#model=project.task&id=2479563
Miscellaneous changes
Currently, when select the project from the timesheet header dropdown then there is traceback due to invalid field in domain as allow_timesheet_timer is removed from project. So in this commit, replace the allow_timesheet_timer field by the allow_timesheets so it will display all the project which has timesheet enabled. Related PR: #21206 Task-2657391 Forward-Port-Of: odoo/enterprise#21525
Original PR description
Currently, when select the project from the timesheet header dropdown then there is traceback due to invalid field in domain as allow_timesheet_timer is removed from project. So in this commit, replace the allow_timesheet_timer field by the allow_timesheets so it will display all the project which has timesheet enabled. Related PR: #21206 Task-2657391 Forward-Port-Of: odoo/enterprise#21525
Linked to e3b5f5536fe in community. The company menu in the above commit has been set to always be visible. Since enterprise has the burger menu at some threshold, we make sure to remove the systray item when needed. Community: https://github.com/odoo/odoo/pull/77721 Forward-Port-Of: odoo/enterprise#21398
Original PR description
Linked to e3b5f5536fe in community. The company menu in the above commit has been set to always be visible. Since enterprise has the burger menu at some threshold, we make sure to remove the systray item when needed. Community: https://github.com/odoo/odoo/pull/77721 Forward-Port-Of: odoo/enterprise#21398
Forward-Port-Of: odoo/enterprise#21386
Original PR description
Forward-Port-Of: odoo/enterprise#21386
**Current behavior before PR:** - The folding helpdesk team cards still using the same space when they are unfolded. - On the Planning slots form view, a button 'i am unavailable' is visible even if 'allow unassignment' feature is enabled or not. - The visibility of the 'invoicing' notebook depends on the partner_id, not on FSM. **Desired behavior after PR is merged:** - The folding helpdesk team cards will use proper space. - On the Planning slots form view, a butt
Original PR description
**Current behavior before PR:** - The folding helpdesk team cards still using the same space when they are unfolded. - On the Planning slots form view, a button 'i am unavailable' is visible even if…
**Current behavior before PR:** - The folding helpdesk team cards still using the same space when they are unfolded. - On the Planning slots form view, a button 'i am unavailable' is visible even if 'allow unassignment' feature is enabled or not. - The visibility of the 'invoicing' notebook depends on the partner_id, not on FSM. **Desired behavior after PR is merged:** - The folding helpdesk team cards will use proper space. - On the Planning slots form view, a button 'I am unavailable' will only be visible if 'allow unassignment' feature is enabled and on shifts that are assigned to the current user. - If is_fsm is true, the invoicing notebook will display if allow_billable is true as well. - If is_fsm is false, the invoicing notebook will display if allow_billable is true and if a partner_id is set on the project. - The invoicing notebook will display even if the project is linked to a helpdesk team. Task-2647164 Forward-Port-Of: odoo/enterprise#21045
Before this commit, the View Editor Manager handled the edition of X2Many a bit roughly. Because of the refactoring of the upper layer in wowl (87f2fe1b561757c3cb791ced17cee99ee6f8d6cb), the VEM is always re-instanciated when clicking on the edition of a nested x2m view. This caused the VEM to always instanciate the editor for the main view and only then started to update itself for the edition of the x2m. As a consequence, RPC were done too many times and the rendering was a bit slow.
Original PR description
Before this commit, the View Editor Manager handled the edition of X2Many a bit roughly. Because of the refactoring of the upper layer in wowl (87f2fe1b561757c3cb791ced17cee99ee6f8d6cb), the VEM is always re-instanciated when clicking on the edition of a nested x2m view. This caused the VEM to always instanciate the editor for the main view and only then started to update itself for the edition of the x2m. As a consequence, RPC were done too many times and the rendering was a bit slow. After this commit, we instanciate the VEM in the right conditions from its start, allowing to have a smoother experience. This comes at the price of a rather heavy fix, but it should prepare us for a future refactoring in OWL. Forward-Port-Of: odoo/enterprise#21500
Before WOWL `.o_home_menu` was outside the `.o_action_manager`. And since [1] a global CSS rule (in mail module) was added to `.o_action_manager`: ```css .o_action_manager { min-height: 0; } ``` But after the commit [2] the `min-height` was removed, this as the effect that `.o_action_manager` takes the whole height of it's content. But the 'background' can't scroll. This commit force the `.o_home_menu_scrollable` to has its minimal size at `0px`, so the scroll happens here
Original PR description
Before WOWL `.o_home_menu` was outside the `.o_action_manager`.
And since [1] a global CSS rule (in mail module) was added to
`.o_action_manager`:
```css
.o_action_manager {
min-height: 0;
}
```
But after the commit [2] the `min-height` was removed, this as the
effect that `.o_action_manager` takes the whole height of it's content.
But the 'background' can't scroll.
This commit force the `.o_home_menu_scrollable` to has its minimal size
at `0px`, so the scroll happens here and not in the parent.
Steps to reproduce:
* Open Odoo on Mobile
* Go to 'Home Menu' if not already in
* Scroll => BUG
Refs:
[1] odoo/odoo@3fea5b2136627c1d7e83b2a5e111952fe3eb10a1
[2] odoo/odoo@06081d2e8d86ec695f68c155b882d6a15a3fce9f
Forward-Port-Of: odoo/enterprise#21461Issue: When trying to print an invoice with one line that doesn't contain a product, there is a traceback saying ``` File "/home/odoo/src/enterprise/14.0/l10n_pe_edi/models/account_move. py", line 169, in _l10n_pe_edi_get_spot max_percent = max(self.invoice_line_ids.mapped('product_id.l10n_pe_withh old_percentage')) ValueError: max() arg is an empty sequence ``` Steps to reproduce : 1- Create an invoice 2- Create an invoice line with a note only (no product) 3- Save 4- Try to pr
Original PR description
Issue: When trying to print an invoice with one line that doesn't
contain a product, there is a traceback saying
```
File "/home/odoo/src/enterprise/14.0/l10n_pe_edi/models/account_move.
py", line 169, in _l10n_pe_edi_get_spot
max_percent = max(self.invoice_line_ids.mapped('product_id.l10n_pe_withh
old_percentage'))
ValueError: max() arg is an empty sequence
```
Steps to reproduce :
1- Create an invoice
2- Create an invoice line with a note only (no product)
3- Save
4- Try to print invoice
Side-Note: since we check right after if `not max_percent`, the
developer of this code probably expected that there might be no
maximum, except that it needs to be explicitly written as default in
Python
opw-2658816 parent-task: 2641982
Forward-Port-Of: odoo/enterprise#21424Community PR: https://github.com/odoo/odoo/pull/77872 Forward-Port-Of: odoo/enterprise#21465
Original PR description
Community PR: https://github.com/odoo/odoo/pull/77872 Forward-Port-Of: odoo/enterprise#21465
This commit adapts studio code to odoo/odoo@1abe965 The "related" field of a field is now a dotted string and not a list of field. Forward-Port-Of: odoo/enterprise#21515
Original PR description
This commit adapts studio code to odoo/odoo@1abe965 The "related" field of a field is now a dotted string and not a list of field. Forward-Port-Of: odoo/enterprise#21515
Suppose a 3-steps delivery. When validating the task, if all pickings are not validated, it will lead to incorrect data To reproduce the issue: 1. Set the outgoing shipments on 3 steps 2. Create a task T in Field Service 3. Add a product to T 4. Confirm the generated SO 5. Validate the two first pickings 6. Mark T as done 7. Consult the pickings Error: The two first pickings have each 2 SML, and each SML has its done quantity equal to 1 OPW-2645545 Forward-Port-Of: odoo/enterp
Original PR description
Suppose a 3-steps delivery. When validating the task, if all pickings are not validated, it will lead to incorrect data To reproduce the issue: 1. Set the outgoing shipments on 3 steps 2. Create a task T in Field Service 3. Add a product to T 4. Confirm the generated SO 5. Validate the two first pickings 6. Mark T as done 7. Consult the pickings Error: The two first pickings have each 2 SML, and each SML has its done quantity equal to 1 OPW-2645545 Forward-Port-Of: odoo/enterprise#21480 Forward-Port-Of: odoo/enterprise#21275