Tuesday, September 17, 2024
5 changes · 17.0
Resolved issues and error corrections
E-waybills generated from sales or purchase orders in a foreign currency now correctly convert unit prices to INR. This prevents incorrect invoice and transport documentation values when exchange rates should apply.
Original PR description
Before this commit: While generating E-waybill from a SO/PO with different currency the price unit in E-waybill is displayed incorrect in INR, the currency conversion rate is not applied and the price unit is displayed as it is in INR which is incorrect After this commit: We resolve the above issue. Now the currency conversation rate is applied correctly on the price unit while generating E-waybill from SO/PO Description of the issue/feature this PR addresses: Current behavior before PR: Desired behavior after PR is merged: --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
Online Point of Sale payments could fail after a successful Razorpay transaction when no customer was selected, leaving the sale unconfirmed and the payment entry unposted. The fix treats such payments as coming from the public user instead of the admin user, avoiding company mismatches and allowing the POS payment flow to finish normally.
Original PR description
Steps: --------- - Install the Point of Sale module with demo data. - Set up online payment provider (e.g. Razorpay) for the Indian company. - Enable online payment method in Point of sale app…
Steps:
---------
- Install the Point of Sale module with demo data.
- Set up online payment provider (e.g. Razorpay) for the Indian company.
- Enable online payment method in Point of sale app configuration
- Add the payment method in Point of sale shop configuration.
- Make a successful online payment in the Point of sale app.
Issue:
---------
- Error occurs after successful payment, preventing the payment from being
processed and confirmed in POS module and the payment entry from being posted.
Cause:
---------
- Payment transactions status were failing due to company mismatch between the
partner(admin)'s company and the pos order's company.
FIX:
---------
- If customer is not selected in pos order, we consider the order and payment
from public user not from the admin user.
Improvement:
---------
- env is not accessible with self in controller for self.env.ref('base.public_user')
fixed with request.env.ref('base.public_user')
- Unused code removed from `_get_partner_sudo` method
task-3989409The Point of Sale now handles draft order lines that refer to products no longer loaded in the PoS. This prevents the PoS from failing to open after product category restrictions or similar settings are changed, helping sales teams resume work without interruption.
Original PR description
Before this commit, the PoS would fail to load if an orderline contained a product that was not loaded into the PoS. This issue could arise, for example, when category restrictions are applied after creating draft orders, preventing the PoS from loading. opw-4119028 --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
Fixed an issue where the Safari browser URL bar and navigation buttons were visible when accessing the Meeting Room booking page as an installed home screen app on iOS devices. The fix adds proper mobile web app configuration to provide a cleaner, full-screen experience for users who add the room booking to their iPhone home screen.
Original PR description
Steps to reproduce (on IOS): ------------------- With Safari browser: - Install `Meeting Rooms` app - Go to Meeting Rooms -> Rooms and open any room - Copy the `Room Booking URL` and open it in a new tab - Click on the menu, then on `Add to Home Screen` - Open the room booking from the home screen Issue: ------ The URL and browser buttons are visible at the top of the screen. Solution: --------- Add the meta tags `mobile-web-app-capable` and `apple-mobile-web-app-capable` to the room template. opw-3639196
This fix ensures that when the AvaTax module is installed or when a new US company is created, the required fiscal position is automatically set up across all US companies. Previously, the fiscal position was only available in the company where the module was initially installed, causing issues for multi-company setups.
Original PR description
Since the fiscal position is added in data with the xml, the others companies than the current ones don't have it. So this commit will allow: - When installing the Avatax modules, create the fiscal position in all US companies at the same time - When creating a new US company with the Avatax module installed, setup the fiscal position in the new company at the same time task: 4100725