Odoo Changelog — 2026-09-03

Thursday, September 3, 2026

3 changes · saas-18.3

Bug Fixes(3)

Resolved issues and error corrections

[FIX] core: correct TransientModel access rights documentation

Coresaas-18.3core

The update corrects internal documentation about how temporary records are accessed, aligning it with the current permissions system. This reduces confusion for developers and administrators without changing product behavior for users.

Original PR description

Since 6d8688bb124d, TransientModel records use the regular access rights mechanisms instead of being implicitly restricted to their creator.

The docstring was not updated with that change and has therefore incorrectly documented creator-only access since 14.0.

Forward-Port-Of: odoo/odoo#286251

#documentation#access rights#permissions

[FIX] sale: correctly forbid partner name edition on portal

PR #286015

Coresaas-18.3sale

This fixes a loophole that allowed portal users to change a customer name by creating a different invoice contact. The sales process now applies the intended restriction consistently, helping keep customer records accurate and controlled.

Original PR description

Before this commit it was possible to update name by creating an other invoice partner. The AND condition was wrong here.

Forward-Port-Of: odoo/odoo#285537

#portal#customer-records#sales

[FIX] partner_autocomplete: reset dirty state after selection

PR #286268

Coresaas-18.3partner_autocomplete

Selecting a suggested partner now correctly returns the form to its saved state after the record is updated. This prevents users from seeing inactive save or discard buttons after autocomplete has already saved the partner details.

Original PR description

Steps to reproduce:
1) open partner form view
2) type in the name field
3) select a suggestion from the autocomplete dropdown

Issue:
The record is enriched and saved, but the form still displays the save/discard buttons, and clicking them does nothing.

The record dirty indicator is driven by 2 signals
1) `model.root.dirty`, which is cleared by save() call earlier in the onSelect()
2) the state `fieldIsDirty` of the `FormStatusIndicator`

The second indicator is set to true when the user types in an input field, and selecting an option never clears it. The `setDirty` prop no longer exists, and therefore was deadcode. This commit emits `FIELD_IS_DIRTY` bus event, which is the only way to update the second indicator. With that, the indicator goes back to saved state once the record is updated.

task-6475332

Forward-Port-Of: odoo/odoo#285897

#autocomplete#form status#user experience

Since 6d8688bb124d, TransientModel records use the regular access rights mechanisms instead of being implicitly restricted to their creator. The docstring was not updated with that change and has therefore incorrectly documented creator-only access since 14.0. Forward-Port-Of: odoo/odoo#286251

Steps to reproduce: 1) open partner form view 2) type in the name field 3) select a suggestion from the autocomplete dropdown Issue: The record is enriched and saved, but the form still displays the save/discard buttons, and clicking them does nothing. The record dirty indicator is driven by 2 signals 1) `model.root.dirty`, which is cleared by save() call earlier in the onSelect() 2) the state `fieldIsDirty` of the `FormStatusIndicator` The second indicator is set to true when the user types in an input field, and selecting an option never clears it. The `setDirty` prop no longer exists, and therefore was deadcode. This commit emits `FIELD_IS_DIRTY` bus event, which is the only way to update the second indicator. With that, the indicator goes back to saved state once the record is updated. task-6475332 Forward-Port-Of: odoo/odoo#285897