Daily updates from Odoo
Monday, August 19, 2024
16 changes · master
Enhancements to existing features
The Indian payroll demo data now uses more realistic but fictional bank information for selected employees. This improves the quality and credibility of sample payroll records without affecting real employee or banking data.
Original PR description
In this commit, modify bank details for employees to look realistic yet fictional. Bank Detail for Alisha sharma Bank Name :- HDFC Bank Account number :- 0112340000998 IFSC Code :- HDF00000123 Send Money :- Trusted Bank Detail for Shaurya Khurana Bank Name :- HDFC Bank Account number :- 0222340000789 IFSC Code :- HDF00000123 Send Money :- Trusted Bank Detail for Vihaan Sengupta Bank Name :- State Bank Account number :- 1245670000123 IFSC Code :- SBIS00004321 Send Money :- Trusted task-4037411
Users can now set a timer even when an accounting lock date applies only to themselves. This aligns the lock date workflow with updated business rules and gives users more flexibility when managing accounting periods.
Original PR description
Change of specs, we now allow to set a timer even when the lock date is set for "me". Was probably an overlook while going too fast while discussing about the spec.
Resolved issues and error corrections
This fixes an issue where manually validating imported bills could be incorrectly treated as a manual edit in certain localization flows. The change helps keep automatic bill posting recommendations accurate for users in affected e-invoicing localizations.
Original PR description
In b1046c8156ee3d3699d5b229720134cc3b2532d4, we introduced a new feature to allow autoposting of bills. When a user does not modify the imported bill for 3 consecutive times, we ask the user if he wants to activate the feature. To detect whether the user has modified the imported bill or not, we use a new field `is_manually_modified` which is always set to `True` when the bill is edited except for automatic flows (OCR, CRON, email) or when the user manually validates the bill. In the latter case, `is_manually_modified` shouldn't be set to `True` even if it is a manual flow. For this purpose, when posting, we use the special context key `skip_is_manually_modified=True` to skip the setting of `is_manually_modified`. This was done for the `_post()` method of `account.move`, but is also required for some extensions of this method in the `l10n_` modules. runbot error id: 74836 Community PR: https://github.com/odoo/odoo/pull/176905
The point-of-sale restaurant appointment screen now correctly highlights the Manage Bookings tab when it is selected. This makes navigation clearer for staff and reduces confusion when switching between tabs.
Original PR description
A new tab system has been introduced in 1bc90a18807c43206c4620d7faad2579a3a61fc9 The selected tab is supposed to be highlighted, but that is not currently the case for the `Manage Bookings` tab. In this commit we fix the issue. Related to: https://github.com/odoo/odoo/pull/176642
This update keeps Mexico electronic invoicing payment registration working after a related change in the core payment flow. It prevents disruption for users processing Mexican payments by aligning the localization with the updated system behavior.
Original PR description
…nity The `_get_batches()` method is removed in the community commit and changed by a computed field. We adapt the code that used it accordingly. task-3884561 Related to https://github.com/odoo/odoo/pull/174812
Code cleanup and technical improvements
The invoice extraction module has been reorganized so configuration and status screens are stored in the proper location. This is an internal cleanup that helps keep the module easier to maintain without changing business workflows.
Original PR description
Move res_config_settings_views and extraction_status from the data directory to the correct views directory. Also removed the account_move_views file, as constant invisible fields do not have to be declared anymore.
Miscellaneous changes
Before this commit, the bottom right label in sign templates which included the hourglass icon was overlapping the action buttons and the search panel in the left position of the screen was occupying a big part of the screen when the width was small, hiding the sign templates and sign documents in the bottom of the page. After this commit, the bottom right label does not overlaps the action buttons anymore and when the screen is small (in width) we hide the search panel for showing the sign t
Original PR description
Before this commit, the bottom right label in sign templates which included the hourglass icon was overlapping the action buttons and the search panel in the left position of the screen was occupying a big part of the screen when the width was small, hiding the sign templates and sign documents in the bottom of the page. After this commit, the bottom right label does not overlaps the action buttons anymore and when the screen is small (in width) we hide the search panel for showing the sign templates and sign documents correctly. task-4077791 Forward-Port-Of: odoo/enterprise#68490 Forward-Port-Of: odoo/enterprise#67700
**Description** A [recent](https://github.com/odoo/enterprise/commit/76d9188767e26c4ae1f815334af5ca3ac6c5fcdf) change in the l10n_fr_reports **IMB - Intermediate management balances** created a new child and parent hierarchy between report lines that never existed before. This causes a traceback when opening the report on migrated databases. The report lines must be loaded in an order where parent lines come before their children. The sorting of `account.report.line` model is by `sequence,
Original PR description
**Description** A [recent](https://github.com/odoo/enterprise/commit/76d9188767e26c4ae1f815334af5ca3ac6c5fcdf) change in the l10n_fr_reports **IMB - Intermediate management balances** created a new…
**Description**
A [recent](https://github.com/odoo/enterprise/commit/76d9188767e26c4ae1f815334af5ca3ac6c5fcdf) change in the l10n_fr_reports **IMB - Intermediate management balances** created a new child and parent hierarchy between report lines that never existed before. This causes a traceback when opening the report on migrated databases.
The report lines must be loaded in an order where parent lines come before their children. The sorting of `account.report.line` model is by `sequence, id`, where `sequence` column (if unchanged) remains null, causing lines to be sorted by `id`. The change caused larger id records to be assigned as the parent of smaller id records, violating the required hierarchy and raising a traceback.
**Traceback :**
```py
File "/home/odoo/src/enterprise/17.0/account_reports/models/account_report.py", line 4386, in get_report_information
'lines': self._get_lines(options, all_column_groups_expression_totals=all_column_groups_expression_totals, warnings=warnings),
File "/home/odoo/src/enterprise/17.0/account_reports/models/account_report.py", line 2123, in _get_lines
parent_generic_id = line_cache[line.parent_id]['id'] if line.parent_id else None # The parent line has necessarily been treated in a previous iteration
KeyError: account.report.line(338,)
```
**steps to reproduce**
1. install 'l10n_fr' and 'account_accountant' in a demo database of version 16
2. migrate it to version 17.
3. go to Reporting->Profit and Loss (Fr company should be selected)
4. Change Report to "IMB - Intermediate management balances"
Note: This PR is created by this [suggestion](https://github.com/odoo/upgrade/pull/6267#issuecomment-2244373973).
Forward-Port-Of: odoo/enterprise#68182
Forward-Port-Of: odoo/enterprise#67147#### [FIX] stock_barcode: restrict product scan pckging > #### How to reproduce: > - Create a product with a product packaging and set a barcode for this packaging; > - In the Receipts operation type config, check the product mandatory scan; > - Create and confirm a receipt for the created product; > - Open the receipt in the Barcode app; > - Scan the product's packaging => A notification asks you to scan the product first. > > This behavior is not right, a packaging should be a valid s
Original PR description
#### [FIX] stock_barcode: restrict product scan pckging > #### How to reproduce: > - Create a product with a product packaging and set a barcode for this packaging; > - In the Receipts operation type…
#### [FIX] stock_barcode: restrict product scan pckging > #### How to reproduce: > - Create a product with a product packaging and set a barcode for this packaging; > - In the Receipts operation type config, check the product mandatory scan; > - Create and confirm a receipt for the created product; > - Open the receipt in the Barcode app; > - Scan the product's packaging => A notification asks you to scan the product first. > > This behavior is not right, a packaging should be a valid scan too for product's mandatory scan. > > [OPW-4062460](https://www.odoo.com/odoo/project/49/tasks/4062460?cids=1) ### [FIX] stock_barcode: GS1 packaging with lot > #### Steps to reproduce: > - In Inventory settings, choose GS1 as barcode nomenclature and activate packages; > - Create a storable product tracked by lot; > - Create a lot for this product (e.g.: 12345); > - Create a second storable product tracked by lot; > - Create a new lot with the same name (12345) and a packaging on the product page with the barcode number 10000000240489; > - Go back to the barcode app and create a new delivery; > - San the barcode 01100000002404891012345 > => The line is added for the right product but the lot is missing. > > #### What happens: > When the GS1 barcode is parsed, we got a lot name and a packaging barcode, thus, we will search a lot for the scanned lot name. > To avoid fetching the wrong lot in case multiple lots have the same name (but different product), we give a filter when the lot is scanned alongside a product. > The issue here is we didn't scan a product but a packaging and we forgot to give the same filter in this case. > > [OPW-3894500](https://www.odoo.com/odoo/project/49/tasks/3894500?cids=1) ### [FIX] stock_barcode_picking_batch: reserved lot > Bug introduced by: https://github.com/odoo/enterprise/pull/63908 > > #### How to reproduce: > - Create a product tracked by lot; > - For this product, add some quantity in stock for at least two different lots; > - Create a delivery for this product, with enough quantity to reserve at least two different lots; > - Confirm it and add it into a batch; > - Open this batch in the Barcode app; > - You should have a button to display reserved lots on the product line, click on it, it will display the reserved lot AND select the first one; > - Scan a reserved lot other than the first one => The first one will be replaced by the scannned lot even if there is already another line with this lot. > > [OPW-4017945](https://www.odoo.com/odoo/project/49/tasks/4017945?cids=1) Forward-Port-Of: odoo/enterprise#68403 Forward-Port-Of: odoo/enterprise#67267
The BelastingDienst returns an error if the format for the 'ProfessionalAssociationForTaxServiceProvidersName' tag is not respected. The string value in that tag should not exceed 20 characters.µ opw-4075462 Forward-Port-Of: odoo/enterprise#67901 Forward-Port-Of: odoo/enterprise#67635
Original PR description
The BelastingDienst returns an error if the format for the 'ProfessionalAssociationForTaxServiceProvidersName' tag is not respected. The string value in that tag should not exceed 20 characters.µ opw-4075462 Forward-Port-Of: odoo/enterprise#67901 Forward-Port-Of: odoo/enterprise#67635
When a table has an upcoming appointment, the table number shown is incorrect. ( a `T` is prepended to the name for no reason ) In this commit we fix the issue and refactor the code slightly. Task: 4110510 Forward-Port-Of: odoo/enterprise#68367
Original PR description
When a table has an upcoming appointment, the table number shown is incorrect. ( a `T` is prepended to the name for no reason ) In this commit we fix the issue and refactor the code slightly. Task: 4110510 Forward-Port-Of: odoo/enterprise#68367
Partial revert of https://github.com/odoo/enterprise/commit/318ae33da2e36036e1a74028a36d02ad4fa5964e (we keep the test and revert the fix). The reverted commit intended to soluve issues with hide_if_zero, and had it consider the string values as 0. However, in 17.2+, this caused issues with the blank_if_zero columns, which then never showed such string values. We revert the original fix and take a new approach in this commit ; we do that in 17.0 instead of 17.2 just for homogeneity of the
Original PR description
Partial revert of https://github.com/odoo/enterprise/commit/318ae33da2e36036e1a74028a36d02ad4fa5964e (we keep the test and revert the fix). The reverted commit intended to soluve issues with hide_if_zero, and had it consider the string values as 0. However, in 17.2+, this caused issues with the blank_if_zero columns, which then never showed such string values. We revert the original fix and take a new approach in this commit ; we do that in 17.0 instead of 17.2 just for homogeneity of the code base, and ease of maintenance on longer term. The new strategy is bacisally to consider non-number values as 0 only when handling the hide_if_zero option, without touching to the computation of the is_zero key of column dicts. Also, this commit explicitly adds the 'percentage' figure_type to the ones checked by the 'is_zero' key in column dicts: percentages are numeric values; ignoring them there was wrong. Forward-Port-Of: odoo/enterprise#68511 Forward-Port-Of: odoo/enterprise#68450
Before this commit: - Budgets can be deleted in any state. After this commit: - Added validation to prevent deletion of budgets in the Open, Revised, or Done stages. Task-4108962 Forward-Port-Of: odoo/enterprise#68346
Original PR description
Before this commit: - Budgets can be deleted in any state. After this commit: - Added validation to prevent deletion of budgets in the Open, Revised, or Done stages. Task-4108962 Forward-Port-Of: odoo/enterprise#68346
This commit aims to add a minimum box size for sign items. regardless of how the user resizes them, they should maintain this minimum size. Task: 4014579 Forward-Port-Of: odoo/enterprise#67242
Original PR description
This commit aims to add a minimum box size for sign items. regardless of how the user resizes them, they should maintain this minimum size. Task: 4014579 Forward-Port-Of: odoo/enterprise#67242
Have a 0% Tax Open bank reconciliation widget Reconcile a bank statement with a manual operation including the 0% tax Issue: On the reconciliation widget a void line will be shown After validation the 0 balance tax line will be created opw-4043498 Forward-Port-Of: odoo/enterprise#68383 Forward-Port-Of: odoo/enterprise#67458
Original PR description
Have a 0% Tax Open bank reconciliation widget Reconcile a bank statement with a manual operation including the 0% tax Issue: On the reconciliation widget a void line will be shown After validation the 0 balance tax line will be created opw-4043498 Forward-Port-Of: odoo/enterprise#68383 Forward-Port-Of: odoo/enterprise#67458
Ensure that, when importing amounts involving currency exchanges, the system reads the amount that includes the fees. (New behavior confirmed with CHKL) opw-3999490 Forward-Port-Of: odoo/enterprise#68385 Forward-Port-Of: odoo/enterprise#67879
Original PR description
Ensure that, when importing amounts involving currency exchanges, the system reads the amount that includes the fees. (New behavior confirmed with CHKL) opw-3999490 Forward-Port-Of: odoo/enterprise#68385 Forward-Port-Of: odoo/enterprise#67879