on_change behaves odd when fields conflict with context_*
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Odoo GTK Client (MOVED TO GITHUB) |
Fix Released
|
Medium
|
Naresh(OpenERP) |
Bug Description
I'm testing on trunk version, the problem doesn't affect openobject-web client.
I created a model with a many2one field 'project_id' pointed to the model 'project.project', and I set an 'on_change_
The problem is when the on_change method triggered, the current 'project_id' didn't actually passed as an argument into on_change method, instead, the 'context_
I've noticed that the 'context_
Currently I can workaround the problem by setting the field name other than 'project_id' ,e.g. 'myproject_id', however, this really looks awkward.
Related branches
Changed in openobject-client: | |
status: | New → Confirmed |
Changed in openobject-server: | |
milestone: | none → 6.0 |
summary: |
- on_change event pass the value in context instead of the value on field + on_change behaves odd when fields conflict with context_* |
affects: | openobject-server → openobject-client |
Changed in openobject-client: | |
milestone: | 6.0 → none |
Changed in openobject-client: | |
importance: | Undecided → Medium |
milestone: | none → 6.0 |
Hello,
I created a new model and added a many2one field of project.project named as project_id and added an on_change method on it with context. And it is working as it should. Can you give me an example where you have used it and it mixes with context_project_id?
Thanks.