Should i define some extra rules in python code?
Should not this field be automatically readonly/disabled if write access = False ? (bug ?) It seems it was working before. Now i can check and uncheck the field even if i’ve only read access right…
The goal of this field is to allow many users to create products but only products having validated field = True can be used in Sales, Purchases, … And only users in group “product_validate” are allowed to write this specific field (so they check if all product’s data are correct before to validate the product).
Thanks for help!
So defined right access on the field in XML are correct, i just need to set the field readonly to avoid the error message? Can i set a field readonly or not depending on a group ?
Would be nice!
As the field is defined on product template and then also referenced on product variant, should i define access rights on both models ?
We made some tests: my code was working on tryton 5.0 (with field access rights in xml). The field related by only read access rights is readonly. So there’s an update in 5.2 that change this behaviour. (don’t know yet which issue made this change)
I made some easy tests: setting field “consumable” in product template readonly for all users, and all access (R,D, C and W) to admin. I set product administration rights to demo user. Field is not readonly when using demo user in 5.2, but field is readonly with the same access rules in 5.0