odoo/odoo#187135
Created by fw-bot
Merged
at 4e724323d811dec76c186b5cfff6e4b0135b2128
Statuses:
- legal/cla: Contributor License Agreement check
- ci/runbot: Odoo Test Suite
- ci/upgrade_enterprise: Test upgrades for enterprise master
- ci/template: Contact runbot team on discord for help.
- ci/style: Optional style check. Ignore it only if strictly necessary.
- ci/security: Required security check. Can only be ignored by security team.
Linked pull requests
- label
- odoo-dev:17.0-16.0-account-empty-string-false-inconsistency-fix-jWyv-fw
- head
- dd46cca7ebe13b26e3483fcbb0a89268ab5e93a5
- merged
- 10 months ago by Accounting, William André (wan)
| odoo/odoo | odoo/enterprise | |
|---|---|---|
| 16.0 | #186079 | #73256 |
| 17.0 | #187135 | #73766 |
| saas-17.2 | #189097 | #74854 |
| saas-17.4 | #189099 | #74855 |
| 18.0 | #191026 | #75834 |
| saas-18.1 | #199289 | #80158 |
| saas-18.2 | #199307 | #80167 |
| saas-18.3 | ||
| saas-18.4 | ||
| 19.0 | ||
| master | #204193 | #82582 |
[FW][FIX] account: fix empty string and False/None inconsistencies
[FIX] account: fix empty string and False/None inconsistencies
When empty, the name field of account.move.line could inconsistently hold either an empty string or False. This inconsistency led to different results when searching for lines with an empty label, as label->not set and label == "" yielded different outcomes. The latter behavior aligns with expected ORM operations.
This fix ensures the name field is set to False whenever the computed result is an empty string, standardizing search behavior.
I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
Forward-Port-Of: #186079