**Steps to reproduce:**

1- Install the purchase_stock module.
2- Create a new PO with a new vendor.
3- Add new one product in the purchase order line with quantity > 1.
4- Confirm the PO and go to the generated receipt.
5- Validate the receipt with less than the ordered quantity, by choosing no
   backorder.
6- Duplicate the receipt for the remaining quantity and validate it.
7- In vendor form view, the On-time Rate value shown in the smart button differs
   from the value in the graph.

**Issue:**
https://github.com/odoo/odoo/blob/e7da32fe67cfe78bc6da8bf5d36a7c584763e3bb/addons/purchase_stock/report/vendor_delay_report.py#L26-L42

- The On-time Rate shown in the smart button does not match the graph.

**Example:**

- PO Line ordered qty: 10  
- First receipt validated: 6 (no backorder)  
- Duplicated receipt validated: 4  
- In vendor form view inside On-time Rate Smart button
- Total quantity coming: 14 (incorrect)  
- Expected total qty for calculation: 10 (from PO line)  
- On-time delivery rate calculated: **71.43%**  
- Expected On-time delivery rate: **100%**

**Cause:**

- The report uses `product_qty` from the stock move.  
- When a receipt is duplicated and the demand quantity is manually set, 
`product_qty` is recomputed from this demand value.  
This leads to a mismatch between the PO line quantity and the aggregated stock 
move quantities.

**NOTE:**
In `test_02_vendor_delay_report_partially_cancelled_purchase_order`, added the line::
`purchase_order.order_line.flush_recordset()`

- Because we were taking the `partner_id` from the `Purchase Order line` is a stored related field.
- The computed value first lives in Odoo’s cache.
- It is not written to the database until a flush occurs.
- If we immediately call something like _read_group() (which queries the database directly), 
it won’t see the cached value — only what is persisted in the DB.

**Solution:**

- Use the purchase order line quantity instead of the stock move’s `product_qty` 
to ensure consistent and accurate On-time Rate calculation.

opw-4991367

Forward-Port-Of: odoo/odoo#236779
Forward-Port-Of: odoo/odoo#225529

**Patch description:**
- Following commit: odoo/odoo@e3b062e5d3820ddfcee2eb669f21edc0c53c3330 the behavior of dynamic snippet rendering changed.

- Previously (up to v18.4), the system first checked whether the dynamic filter existed before calling `_render` on it. After the referenced commit, `get_dynamic_filter` attempts to find the filter and immediately calls `_render`, even if the filter record is missing. diff: https://github.com/odoo/odoo/commit/e3b062e5d3820ddfcee2eb669f21edc0c53c3330#diff-d41b2dc5ff6fd6a303373f86e1af97d055db315ccc431749b4ffac1488dea119R416-R423

**Steps to reproduce:**
- Create a v19 db and install `website_sale`
- Add a dynamic snippet (e.g., Product Catalog) to the website homepage.
- Uninstall `website_sale`
- Install `website_sale` again
- Open the website homepage and then editor
- Traceback:
```py
  File "/home/odoo/odoo/odoo/addons/website/controllers/main.py", line 424, in get_dynamic_filter
    return dynamic_filter_sudo._render(**kwargs) or []
           ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/home/odoo/odoo/odoo/addons/website/models/website_snippet_filter.py", line 78, in _render
    records = self._prepare_sample(limit, res_model=res_model)
              ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/home/odoo/odoo/odoo/addons/website/models/website_snippet_filter.py", line 183, in _prepare_sample
    records = self._prepare_sample_records(length, **options)
              ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/home/odoo/odoo/odoo/addons/website/models/website_snippet_filter.py", line 201, in _prepare_sample_records
    model = self.env[(self.model_name or options.get('res_model'))]
            ~~~~~~~~^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/home/odoo/odoo/odoo/odoo/orm/environments.py", line 107, in __getitem__
    return self.registry[model_name](self, (), ())
           ~~~~~~~~~~~~~^^^^^^^^^^^^
  File "/home/odoo/odoo/odoo/odoo/orm/registry.py", line 322, in __getitem__
    return self.models[model_name]
           ~~~~~~~~~~~^^^^^^^^^^^^
KeyError: None
```

The issue occurs because the snippet’s `data-filter-id` refers to a filter record that gets deleted when `website_sale` is uninstalled. Upon reinstalling, new filter records are created with new IDs. The old snippet still references the deleted ID,
so in `get_dynamic_filter` when searching with `filter_id` returns no record.

Despite `_render` having an `self.ensure_one()` check, the mentioned commit changed it to `self and self.ensure_one()`, allowing a null/empty recordset to pass through and causing rendering issues.

This fix restores the proper behavior by verifying the filter’s existence before rendering.

opw - 5163214, 5248474


---
I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr

Currently an error occurs when a user tries to pay using Authorize.net, and Authorize.net returns an error in the response.

**Steps to replicate:**
* Install `website_sale` and `payment_authorize` with demo.
* Setup the payment provider Authorize.net with valid credentials.
* Add the product to your cart, proceed to checkout, then use and save the payment details from [1] and complete the purchase.
* Repeat the checkout process after replacing the `API Login ID` with an invalid value, and then pay using the saved payment details.

**Error:**
`TypeError: float() argument must be a string or a real number, not 'NoneType'`

**Root cause:**
* The error happens because after the API request at [2], an error response causes `tx_details` to have no `transaction` key, as shown in [3]. This makes the amount at [4] become `None`, which then triggers an error at [5] when Python tries to convert `None` to `float`.
* As noted in the Authorize.net forums (see [6], [7], [8], [9]), the `E00040 'record not found'` error can appear when Authorize.net has synchronization issues on their end.

**Solution:**
* Show the error, change the transaction’s status to ‘error’, and save the error message on the transaction.

[1]:
https://developer.mastercard.com/unified-checkout-solutions/documentation/testing/test_data/ 
[2]:
https://github.com/odoo/odoo/blob/f272eb19813be4254fd461ec21f1cc47e8834559/addons/payment_authorize/models/payment_transaction.py#L160 
[3]:
https://drive.google.com/file/d/1JrXkKzRRTbpjZ8l0kJsX5SIg-kS-P5tv/view?usp=sharing 
[4]:
https://github.com/odoo/odoo/blob/f272eb19813be4254fd461ec21f1cc47e8834559/addons/payment_authorize/models/payment_transaction.py#L163 
[5]:
https://github.com/odoo/odoo/blob/f272eb19813be4254fd461ec21f1cc47e8834559/addons/payment_authorize/models/payment_transaction.py#L167 
[6]:
https://community.developer.cybersource.com/t5/Integration-and-Testing/E00040-The-record-cannot-be-found-right-after-profile-create/m-p/55106#M30039 
[7]:
https://community.developer.cybersource.com/t5/Integration-and-Testing/E00040-when-Creating-Subscription-from-Customer-Profile/m-p/59597#M34176
[8]:
https://stackoverflow.com/questions/67506179/authorize-net-shows-e00040-when-creating-subscription-from-customer-profile 
[9]:
https://community.developer.cybersource.com/t5/Integration-and-Testing/quot-E00040-The-record-cannot-be-found-quot-when-creating/td-p/62409

sentry-7021997195

- Install Accounting and `l10n_de_reports`
- Switch to a German company
- Create a bill:
  * Price: `100.00`
  * Taxes: `19%`
- Edit the tax total with the pencil button
- Go to "Accounting / Reporting / Audit Reports / General Ledger"
=> The tax amount is the one that has been edited manually
- Download `Datev DATA (zip)`
- Open `EXTF_accounting_entries.csv` file

The total amount in the file is the one before the edition of the tax amount.

The Datev data depends on `price_total` field of the invoice lines, but this field is not updated when the tax amount is edited manually.

We now check the total by adding `price_total` of each invoice line and the total amount defined in `tax_totals` field. If there is a difference, compute the delta for each tax group and split it between all the lines where a tax of that group is used.

Ticket [link](https://www.odoo.com/odoo/project.task/4951488)
opw-4951488

Forward-Port-Of: odoo/enterprise#100086
Forward-Port-Of: odoo/enterprise#98684