enterprise version of odoo/odoo#193052 odoo/odoo@a4a87c2 overrode an existing external id. odoo/oddo@824a641 adapted the query counts without this rule Forward-Port-Of: odoo/enterprise#76841

enterprise version of odoo/odoo#193052

odoo/odoo@a4a87c2 overrode an existing external id. odoo/oddo@824a641 adapted the query counts without this rule

Forward-Port-Of: odoo/enterprise#76841

Bug === 1. create a folder without company, and access_via_link='view' 2. create a document with a company A, and access_via_link_hidden=False 3. create a member in the folder 4. log-in using that member and disable the company in the interface => The document should be hidden since the company is not enabled, but it still visible Task-4463854 Forward-Port-Of: odoo/enterprise#76825

Bug
===
1. create a folder without company, and access_via_link='view'
2. create a document with a company A, and access_via_link_hidden=False
3. create a member in the folder
4. log-in using that member and disable the company in the interface => The document should be hidden since the company is not enabled, but it still visible

Task-4463854

Forward-Port-Of: odoo/enterprise#76825

When creating a write-off for multiple multicurrency journal items that where created with the same rate, the reconciliation wizard will recompute the balance of the write-off based on the residual amount of the journal items in invoice currency and the reconciliation rate. Because each journal item applied rounding separately, the resulting amount might differ from the residual amount of the journal items in company currency, which will trigger the creation of an exchange difference entry (f

When creating a write-off for multiple multicurrency journal items that where created with the same rate, the reconciliation wizard will recompute the balance of the write-off based on the residual amount of the journal items in invoice currency and the reconciliation rate.

Because each journal item applied rounding separately, the resulting amount might differ from the residual amount of the journal items in company currency, which will trigger the creation of an exchange difference entry (for a few cents).

This entry is spurious and confusing for the user because the reconciled journal items all shared the same currency and rate and therefore the reconciliation does not correspond to a currency exchange event.

After this commit, when computing the residual amount to write-off in the reconciliation wizard, we check whether the journal items used the same rate as the reconciliation rate, and in that case we directly take the residual amount of the journal item in company currency instead of recomputing the residual amount based on the invoice currency amount and the reconciliation rate, thus avoiding rounding errors.

task-4247344

Forward-Port-Of: odoo/enterprise#76976
Forward-Port-Of: odoo/enterprise#74570

Before this PR: - The `AccountMove.search` method was called without checking if `invoice_number` was valid. - This could lead to unexpected errors when `invoice_number` was `False`. After this PR: - Added a check to ensure the search is only performed if `invoice_number` is valid. - If `invoice_number` is `False`, it falls back to an empty `AccountMove` recordset. - Ensures smoother iteration over `moves` and prevents unnecessary errors in the GSTR-1 error handling logic. Forward-Port

Before this PR:
- The `AccountMove.search` method was called without checking if `invoice_number` was valid.
- This could lead to unexpected errors when `invoice_number` was `False`.

After this PR:
- Added a check to ensure the search is only performed if `invoice_number` is valid.
- If `invoice_number` is  `False`, it falls back to an empty `AccountMove` recordset.
- Ensures smoother iteration over `moves` and prevents unnecessary errors in the GSTR-1 error handling logic.

Forward-Port-Of: odoo/enterprise#76870