Documents now handle image processing more reliably, avoiding attempts to process unsupported PDF content as images. This improves document workflows by reducing errors when users work with files in Documents and spreadsheet-related document features.

…E-FFF EDI) AdditionalDocumentReference is currently injected right after DocumentCurrencyCode. However, in 15.0, OrderReference is implemented and then, AdditionalDocumentReference is no longer injected at the right place. To fix this, we inject now this field just before AccountingSupplierReference that must be always there and Signature is not implemented. See: http://www.datypic.com/sc/ubl20/e-ns19_Invoice.html -- I confirm I have signed the CLA and read the PR guidelines at www

…E-FFF EDI)

AdditionalDocumentReference is currently injected right after DocumentCurrencyCode.
However, in 15.0, OrderReference is implemented and then, AdditionalDocumentReference is no longer injected at the right place.
To fix this, we inject now this field just before AccountingSupplierReference that must be always there and Signature is not implemented.

See:
http://www.datypic.com/sc/ubl20/e-ns19_Invoice.html

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

Forward-Port-Of: odoo/odoo#82817
Forward-Port-Of: odoo/odoo#82788

Step to reproduce: - Create a lead - go on the smart button meeting - create a new meeting and edit it - save Current behaviour: - Validation Error - It seems the default_get apply command in onchange instead of passing the value which lead to missformed argument for meeting Behaviour after PR: - Take advantage of the automatic generation of attendee in to avoid passing attendee command and get default partner in create for quick_create - Automatic generation of attendee is more r

Step to reproduce:
- Create a lead
- go on the smart button meeting
- create a new meeting and edit it
- save

Current behaviour:
- Validation Error
- It seems the default_get apply command in onchange instead of passing the value which lead to missformed argument for meeting

Behaviour after PR:
- Take advantage of the automatic generation of attendee in  to avoid passing attendee command and get default partner in create for quick_create
- Automatic generation of attendee is more robust and also apply when the list is empty to accomodate for the default get setting the value to []

opw-2724372

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

Forward-Port-Of: odoo/odoo#82760
Forward-Port-Of: odoo/odoo#82286

In some cases, the SM description is incorrect To reproduce the issue: 1. Create a product P 2. Create a receipt with 1 x P Error: The description of the SM is incorrect: `<p><br></p>`. It should be the name of P Another example: 1. Create a product P: - Internal Notes: "Lorem Ipsum" 2. Create a receipt with 1 x P Error: The description of the SM is incorrect: `<p>Lorem ipsum<br></p>`. It should be "Lorem Ipsum" Since [1], `product_template.description` is a HTML field.

In some cases, the SM description is incorrect

To reproduce the issue:
1. Create a product P
2. Create a receipt with 1 x P

Error: The description of the SM is incorrect: `<p><br></p>`. It should
be the name of P

Another example:
1. Create a product P:
    - Internal Notes: "Lorem Ipsum"
2. Create a receipt with 1 x P

Error: The description of the SM is incorrect: `<p>Lorem ipsum<br></p>`.
It should be "Lorem Ipsum"

Since [1], `product_template.description` is a HTML field.

[1] bea5790713020209e0527840b7dbc1ea4806b762

OPW-2732208

Forward-Port-Of: odoo/odoo#82686

The store_fname is calculated based on the checksum, as for file_size and checksum, skip during create/write Avoid replacing in place the attachments in base as this breaks some tests reusing the vals_list content (e.g. test_complete_message_post running twice because of `@warmup` share the same self.vals) Forward-Port-Of: odoo/odoo#82882 Forward-Port-Of: odoo/odoo#82860

The store_fname is calculated based on the checksum, as for file_size
and checksum, skip during create/write
Avoid replacing in place the attachments in base as this breaks some
tests reusing the vals_list content (e.g. test_complete_message_post
running twice because of `@warmup` share the same self.vals)

Forward-Port-Of: odoo/odoo#82882
Forward-Port-Of: odoo/odoo#82860

Description of the issue/feature this PR addresses: - create an SO with dropshipping, confirm. It create a PO 1 - copy PO 1 --> Issue PO 2 is linked with the SO @amoyaux -- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr Forward-Port-Of: odoo/odoo#82605

Description of the issue/feature this PR addresses:
- create an SO with dropshipping, confirm. It create a PO 1
- copy PO 1
--> Issue PO 2 is linked with the SO


@amoyaux 




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

Forward-Port-Of: odoo/odoo#82605

Before this commit, users returning from Buckaroo to Odoo after payment could see their session renewed, depending on their browser's implementation of the `SameSite` cookie attribute. This prevented Odoo from retrieving the transaction from the users' session. This commit flags the return route of Buckaroo with `save_session=False`, hence allowing all users to immediately post-process their transactions when they return to Odoo. Forward-Port-Of: odoo/odoo#82929

Before this commit, users returning from Buckaroo to Odoo after payment
could see their session renewed, depending on their browser's
implementation of the `SameSite` cookie attribute. This prevented Odoo
from retrieving the transaction from the users' session.

This commit flags the return route of Buckaroo with
`save_session=False`, hence allowing all users to immediately
post-process their transactions when they return to Odoo.

Forward-Port-Of: odoo/odoo#82929

Forward-Port-Of: odoo/odoo#82927

Forward-Port-Of: odoo/odoo#82927

Some aggressive cache invalidation in the middle of method write() where the model has children models (in the _inherits sense) causes very nasty errors that are hard to fix. Consider two models A and B, where B inherits from A. Also consider two fields a1 and a2 on A, which are thus both inherited by B. Now take a record from model B, and update both fields as: record.write({'a1': ..., 'a2': ...}) As both fields appear as related fields on model B, the method write() puts al

Some aggressive cache invalidation in the middle of method write() where
the model has children models (in the _inherits sense) causes very nasty
errors that are hard to fix.

Consider two models A and B, where B inherits from A.  Also consider two
fields a1 and a2 on A, which are thus both inherited by B.  Now take a
record from model B, and update both fields as:

    record.write({'a1': ..., 'a2': ...})

As both fields appear as related fields on model B, the method write()
puts all values in cache, then it proceeds to call the inverse method of
both fields.  The inverse method of a1 is called, and this writes on the
parent record.  Now imagine that some override on A invalidates the
whole cache.  When the inverse method of a2 is called, the field's value
on B has been invalidated, and this therefore writes the value False on
the record's parent.

This patch removes and adapt such cache invalidations:
 - Since 4b1cb41cf7a3f936a1e6d00a2bb6a6a29e82d711, the cache invalidation
   in method write() of product.product is no longer necessary.
 - The cache invalidation in method write() of product.pricelist.item
   has been made more specific: it only invalidates the field that needs
   to be recomputed.

Fixes #76946, #77042

OPW: 2657461

Forward-Port-Of: odoo/odoo#82935
Forward-Port-Of: odoo/odoo#82901

Steps : - In mobile, go to Task Issue : - "Sales Order" stat button is not displayed. Cause : - This button's classe are : - d-md-inline = displayed when size is medium+. - d-none = or else not displayed - In the past, there was a field SO in the form, which made this button unnecessary and taking space. Fix : - Now that this field isn't present anymore, delete d-none part. opw-2722535 Description of the issue/feature this PR addresses: Current behavior before PR:

Steps :
- In mobile, go to Task

Issue :
- "Sales Order" stat button is not displayed.

Cause :
- This button's classe are :
	- d-md-inline = displayed when size is medium+.
	- d-none = or else not displayed
- In the past, there was a field SO in the form,
	which made this button unnecessary and taking space.

Fix :
- Now that this field isn't present anymore, delete d-none part.

opw-2722535

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

Forward-Port-Of: odoo/odoo#82889
Forward-Port-Of: odoo/odoo#82708

Steps to reproduce: Have a 0% Tax Make an invoice with it Open tax report The 0% tax is not present in the report because there is no tax lines generated for them because the resulting balance is zero. Since the tax details is making a mapping between tax lines and base lines and the tax report is using them to compute the report, the tax report is not able to compute the tax base amount for such taxes. Explanation: Until now, the tax line with a zero amount wasn't generated becau

Steps to reproduce:

Have a 0% Tax
Make an invoice with it
Open tax report

The 0% tax is not present in the report because there is no tax lines generated for them because the resulting balance is zero.
Since the tax details is making a mapping between tax lines and base lines and the tax report is using them to compute the report, the tax report is not able to compute the tax base amount for such taxes.

Explanation:

Until now, the tax line with a zero amount wasn't generated because considered as noisy journal items.
Now we must be able to groupby on the base tax account on the tax report, we are forced to use the tax details.
Injecting dynamically the 0% tax on the tax details sub-queries is really complicated and leads to a huge performance drop.
For that reason, we start to generate the tax lines for 0% tax even the balance is zero.
However, since there is nothing creating the missing lines in the past, it should be fixed case by case if needed.

opw-2711432

Forward-Port-Of: odoo/odoo#82370

As this test is always red, notably because of the qunit asset bundle, the threshold is raised for some bundles based on runbot builds observations. Forward-Port-Of: odoo/odoo#82954

As this test is always red, notably because of the qunit asset bundle, the
threshold is raised for some bundles based on runbot builds
observations.

Forward-Port-Of: odoo/odoo#82954

before this commit, there was a gap in the placeholder description when we create a new course. so this commit fixes the issue by removing the gap from the description Task Id: 2734524 Forward-Port-Of: odoo/odoo#82871

before this commit, there was a gap in the placeholder description
when we create a new course.

so this commit fixes the issue by removing the gap from the description

Task Id: 2734524

Forward-Port-Of: odoo/odoo#82871

now:  before:  -- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr Forward-Port-Of: odoo/odoo#82967

now: 
![image](https://user-images.githubusercontent.com/4848797/149929452-85ad9c7e-eb36-4334-84e6-2acbcca51649.png)


before:
![image](https://user-images.githubusercontent.com/4848797/149929520-c182d41f-e6e5-4518-a002-0bb4afee97c8.png)





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

Forward-Port-Of: odoo/odoo#82967

…ery printer The letterRendering setting was only properly set for the `Printer` class but not for the `EpsonPrinter`. Forward-Port-Of: odoo/odoo#82789 Forward-Port-Of: odoo/odoo#82656

…ery printer

The letterRendering setting was only properly set for the `Printer` class but not for the `EpsonPrinter`.

Forward-Port-Of: odoo/odoo#82789
Forward-Port-Of: odoo/odoo#82656

When reversing an invoice line, the new anglo-saxon lines do not have a correct unit price. The latter is computed as a standard invoice while it should instead consider the original anglo-saxon line or the returned product. Otherwise, it leads to inconsistencies in account journals. Two cases: - Without any sale order: _[FIX] stock_account: base reversed anglo-saxon AML on original one_ - With a sale order: _[FIX] stock_account, sale_stock: reverse AML using the returned SM value_ Details

When reversing an invoice line, the new anglo-saxon lines do not have a correct unit price. The latter is computed as a standard invoice while it should instead consider the original anglo-saxon line or the returned product. Otherwise, it leads to inconsistencies in account journals.
Two cases:
- Without any sale order: _[FIX] stock_account: base reversed anglo-saxon AML on original one_
- With a sale order: _[FIX] stock_account, sale_stock: reverse AML using the returned SM value_

Details about the use cases and the issues are explained in each commit

OPW-2646926
OPW-2628215

Forward-Port-Of: odoo/odoo#82961
Forward-Port-Of: odoo/odoo#82446

…he company has the right country 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 Forward-Port-Of: odoo/odoo#82232

…he company has the right country

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

Forward-Port-Of: odoo/odoo#82232

Steps to reproduce: 1) Create an invoice 1000 with a tax 21% 2) refund the invoice completely 3) Open the tax report: the base amount is -1000 instead of zero Explanation: The tax is using a different repartition line for invoice and for refund. So, the tax report is getting 2 tax details: (-1000, -210) & (1000, 210) due to the groupby on tax_repartition_line.id. The idea is to sum the base only once to avoid summing multiple times the same base amount when a tax has multiple repartitio

Steps to reproduce:
1) Create an invoice 1000 with a tax 21%
2) refund the invoice completely
3) Open the tax report: the base amount is -1000 instead of zero

Explanation:
The tax is using a different repartition line for invoice and for refund.
So, the tax report is getting 2 tax details: (-1000, -210) & (1000, 210) due to the groupby on tax_repartition_line.id.
The idea is to sum the base only once to avoid summing multiple times the same base amount when a tax has multiple repartition lines.
In our case, we need to consider the type of repartition line when grouping in order to count -1000+1000 = 0 as base amount.

Forward-Port-Of: odoo/enterprise#23595

is_in_conflict_or_force def was inconsistent. Fortunately the arguments passed were also inverted which leaded to a working code. This commit purpose is to clean the code. Forward-Port-Of: odoo/enterprise#23593

is_in_conflict_or_force def was inconsistent. Fortunately the arguments
passed were also inverted which leaded to a working code.

This commit purpose is to clean the code.

Forward-Port-Of: odoo/enterprise#23593

Bugfix for: - Overlapped text in the receipt - Empty value in the receipt - Cannot close POS session due to name having more than 50 characters Forward-Port-Of: odoo/enterprise#23509 Forward-Port-Of: odoo/enterprise#23451

Bugfix for:
- Overlapped text in the receipt
- Empty value in the receipt
- Cannot close POS session due to name having more than 50 characters

Forward-Port-Of: odoo/enterprise#23509
Forward-Port-Of: odoo/enterprise#23451

`line_ids` of an account move are dynamically updated. On an invoice, when there is no tax amount for a given tax the tax line is deleted. This is what happens here where all quantities are set to 0 and this dynamic behavior leads to an index error, because the lines are getting deleted within the loop. Anyway quantity is a business field only available for `invoice_line_ids`, so we should set quantity to 0 only for invoice lines and let standard accounting manage dynamic lines. opw-273463

`line_ids` of an account move are dynamically updated. On an invoice, when there is no tax amount for a given tax the tax line is deleted. This is what happens here where all quantities are set to 0 and this dynamic behavior leads to an index error, because the lines are getting deleted within the loop.

Anyway quantity is a business field only available for `invoice_line_ids`, so we should set quantity to 0 only for invoice lines and let standard accounting manage dynamic lines.

opw-2734637

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

Forward-Port-Of: odoo/enterprise#23552

### Issue Sometimes, an invoice can have been correctly registered with SUNAT but Odoo may not have correctly understood this. This can happen, for example, if the cron which sends the payment complement crashes because of a concurrent access error. When this happens, the Odoo user does not have access to the CDR (the receipt from SUNAT). This is an issue because they need to send it to their customer. If the user retries sending the invoice, the IAP service returns an error because th

### Issue
Sometimes, an invoice can have been correctly registered with SUNAT but Odoo may not have correctly
understood this. This can happen, for example, if the cron which sends the payment complement
crashes because of a concurrent access error.

When this happens, the Odoo user does not have access to the CDR (the receipt from SUNAT). This
is an issue because they need to send it to their customer.

If the user retries sending the invoice, the IAP service returns an error because the invoice is
already registered. It does not return the CDR, either.

As a result, the user has no way of obtaining the CDR.
Furthermore, the state in Odoo is not aligned with the state in SUNAT, and the user is not
presented with the relevant buttons e.g. to request the invoice's cancellation.

### Solution
When sending the invoice via the IAP service, if the IAP service returns an error because the
invoice is already registered, re-request the CDR from the IAP service and advance the state
in Odoo accordingly.

### Does it work?
See [this video demonstration](https://drive.google.com/file/d/1_sH_hf9AxHfvg-bH1dC4NCxxgNWTQGqV/view?usp=sharing) 

@jco-odoo thank you so much for your brilliant help :smile: 

Related to support tickets 2714559 and 2663502.

Forward-Port-Of: odoo/enterprise#23171