Friday, March 3, 2023
7 changes · master
Enhancements to existing features
The Argentine electronic invoicing module now recognizes the new AFIP point-of-sale setting across both sales and purchase journals. This helps ensure Liquido Producto processing remains compatible with updated journal configuration rules and reduces compliance-related setup issues.
Original PR description
Update logic to make it compatible with new field Is AFIP POS (l10n_ar_is_pos) taking into account both sale and purchase journals This PR depends on https://github.com/odoo/odoo/pull/111076
The invoice extraction module now works with the newer invoice sending process in Odoo. This keeps electronic document handling aligned with how invoices are actually sent, improving reliability when information leaves Odoo.
Original PR description
The account.invoice.send wizard has been replaced by account.move.send. Main reason: EDI synchronization happens when info get out of Odoo and not on _post(). task-id: 3117238 [enterprise](https://github.com/odoo/enterprise/pull/36757) [community](https://github.com/odoo/odoo/pull/111857)
When an address is validated with Avalara, Odoo now also uses the latitude and longitude returned by Avalara to update the partner's geolocation fields. This reduces manual work and keeps address and map location data aligned for businesses using Avalara and geolocation features.
Original PR description
Before this PR when validating an address with Avalara the latitude and longitude of the response given by their API wasn't used. Since we also have a module named "Geo localization" that provide a way to get the geo localization of a user, we decided that it would be nice that when validating the address the geo localization field would change at the same time. Task-id: 3186071
Point of Sale now supports working across orders in the Belgian blackbox and settle-due flows. This improves cashier workflows and keeps related payment/order actions compatible with recent Point of Sale processing changes.
Original PR description
Related to odoo/odoo#109216 This commit aims at adding the feature "cross-orders" of the PoS. This commit is related to a change made in community where add_new_order now make calls to the server and became asynchronous. The calls to add_new_order must thus be preceded by "await" if necessary.
Users can now choose to display record properties as optional columns in list views, making custom information easier to compare without opening each record. This improves visibility in areas such as Helpdesk and Knowledge while keeping property columns optional and avoiding unsupported bulk editing.
Original PR description
[IMP] *: display properties in list view This commit adds the possibility to display a properties field in a list view. How it works: When a properties field is present in the arch of a list view, it will not be displayed directly. It will display its properties as an optional column. Now, we will find at the end of the dropdown of the optional columns a section by record parent of the properties field. The proposed sections will be the properties linked to the parent record of which at least one record referring to it has been encountered during the navigation in this list view. (A parent record is the record storing the properties definition). Limitation: Multi-editing is not applicable on properties fields as you cannot edit one property without modifying all the others. TaskID: 3105039 Co-authored-by: mcm-odoo <mcm@odoo.com> Co-authored-by: FrancoisGe <fge@odoo.com>
Resolved issues and error corrections
Point of Sale shops can now open normally when Worldline is enabled and a Worldline terminal is linked to a payment method. This prevents an unnecessary startup blockage, even when that payment method is not used in the shop.
Original PR description
Currenlty, PoS shop cannot be opened if we activate Worldline and create a pos payment method with an associated Worldline terminal (even without adding it to the shop) This PR solves this issue
Fixes an issue where changing a recurring planning shift to a single occurrence could delete the current shift and leave users stuck on an error screen. The form now returns to the previous view instead, keeping scheduling workflows smooth.
Original PR description
Steps: - Create a planning shift, set a recurrence for ever. - Go few occurences later (form via kanban) and set... ...recurrence type to "Number of Occurences", ...recurrence nmber to 1. - Save. Issue: "This record doesn't exist". Cause: The write method will update the recurrence so that it only contains only one occurrence. Consequently, the record you just updated is deleted. Then we try to fetch the record to display its form again. Because de read returns [], _fetchRecord rejects the promise, and we're stuck. Fix: In community commit, we make `FormController.saveButtonClicked` call `Record.save` with its params. In this commit, we override `FormController.saveButtonClicked` to call super with the arg `throwOnError` so that, if the shift is deleted when updating its recurrence, we will catch it and, rather than staying on its form, go back to the previous view. Related: https://github.com/odoo/odoo/pull/112335