Odoo Changelog — 2025-05-30

Friday, May 30, 2025

2 changes · saas-18.1

Bug Fixes(2)

Resolved issues and error corrections

[FIX] base_import: prevent TypeError when imported data field is invalid

Coresaas-18.1base_import

The import tool now handles cases where date values are accidentally mapped to text fields without crashing. This helps users catch mapping mistakes through normal validation instead of encountering a technical error.

Original PR description

Currently, if a `date or datetime` field is mapped with a `string or character` field error will be encountered. **Steps to Reproduce:** 1) Install the `Accounting` module. 2) Import…

Currently, if a `date or datetime` field is mapped with a `string or character` field error will be encountered.

**Steps to Reproduce:**
1) Install the `Accounting` module.
2) Import [this](https://docs.google.com/spreadsheets/d/1k_s_V7Q-zA9uQUaQblsJtBHC4VlEFM-w/edit?usp=sharing&ouid=101212513075316114369&rtpof=true&sd=true) file in Account Journal. 
3) Map `Date` with `Account Number`.
4) Click on **Test**, error will be encountered.

**Error:**
`TypeError: sequence item 0: expected str instance, datetime.date found`

**Root Cause:**
The `_handle_multi_mapping` method assumes that all values in the input data are strings. However, when a `datetime.date` or `datetime.datetime` object is encountered, Python raises a `TypeError` during concatenation at [1]

[1]- https://github.com/odoo/odoo/blob/81415d2fab4cfa07897f6a806e5d8a3108cd9c2b/addons/base_import/models/base_import.py#L1599-L1602

**Solution:**
This commit prevents error by ensuring that the `imported fields` are converted to `String` before concatenation.

sentry-6591445640

#import#data mapping#stability

[FIX] pos_urban_piper: print DUPLICATA only on reprinted preparation tickets

PR #85740

Enterprisesaas-18.1pos_urban_piper

Preparation tickets in UrbanPiper POS no longer show the duplicate warning during normal printing. This reduces confusion for restaurant staff by reserving the label for actual reprints only.

Original PR description

Before this commit:
------------------
- The preparation ticket displayed DUPLICATA on every print, regardless of whether it was a reprint or not.

After this commit:
--------------------
- DUPLICATA is now printed only when the preparation ticket is a reprint, avoiding confusion during regular printing.

Task: 4789682

Related PR - https://github.com/odoo/odoo/pull/209640

#pos#urbanpiper#preparation tickets#printing

Currently, if a `date or datetime` field is mapped with a `string or character` field error will be encountered. **Steps to Reproduce:** 1) Install the `Accounting` module. 2) Import [this](https://docs.google.com/spreadsheets/d/1k_s_V7Q-zA9uQUaQblsJtBHC4VlEFM-w/edit?usp=sharing&ouid=101212513075316114369&rtpof=true&sd=true) file in Account Journal. 3) Map `Date` with `Account Number`. 4) Click on **Test**, error will be encountered. **Error:** `TypeError: sequence item 0: expected str instance, datetime.date found` **Root Cause:** The `_handle_multi_mapping` method assumes that all values in the input data are strings. However, when a `datetime.date` or `datetime.datetime` object is encountered, Python raises a `TypeError` during concatenation at [1] [1]- https://github.com/odoo/odoo/blob/81415d2fab4cfa07897f6a806e5d8a3108cd9c2b/addons/base_import/models/base_import.py#L1599-L1602 **Solution:** This commit prevents error by ensuring that the `imported fields` are converted to `String` before concatenation. sentry-6591445640

Before this commit: ------------------ - The preparation ticket displayed DUPLICATA on every print, regardless of whether it was a reprint or not. After this commit: -------------------- - DUPLICATA is now printed only when the preparation ticket is a reprint, avoiding confusion during regular printing. Task: 4789682 Related PR - https://github.com/odoo/odoo/pull/209640