Skip to content

[17.0] [FIX] base_tier_validation: Fixed readonly behavior of fields. #1055

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
wants to merge 1 commit into
base: 17.0
Choose a base branch
from

Conversation

NachoAlesLopez
Copy link

@NachoAlesLopez NachoAlesLopez commented Mar 27, 2025

The module base_tier_validation behaves strangely when computed fields are present. For example, the following screenshots come from a base installation of Odoo with the sale_tier_validation and sale_purchase module added, which causes the purchase order count to be editable when inside a smartbutton:

image

Or, when paired with the sale_margin module, it allows the editing of the margin when the field should be read-only:

image

This is because the base module doesn't take into account the read-onliness of the fields, especially computed fields. This PR should fix that behavior and add a test case to ensure the cases shown before remain patched.

@OCA-git-bot
Copy link
Contributor

Hi @LoisRForgeFlow,
some modules you are maintaining are being modified, check this out!

@NachoAlesLopez NachoAlesLopez changed the title [17.0] [FIX] Fixed readonly behavior of fields. [17.0] [FIX] base_tier_validation: Fixed readonly behavior of fields. Mar 27, 2025
@NachoAlesLopez NachoAlesLopez force-pushed the 17.0-fix-base_tier_validation-computed_fields branch from dac4717 to 05dc3c2 Compare March 27, 2025 15:35
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants