[FIX] crm: no context default user crm.lead
default_user_id on the crm.lead window actions is not needed since the current user is already the default on the field. So all it does is prevent user-defined values to work and possibly affect custom code that may not expect the behavior. opw-1938037 closes #31151
This commit is contained in:
@@ -833,7 +833,6 @@ for rec in records:
|
||||
<field name="domain">[('type','=','opportunity')]</field>
|
||||
<field name="context">{
|
||||
'default_type': 'opportunity',
|
||||
'default_user_id': uid
|
||||
}
|
||||
</field>
|
||||
<field name="search_view_id" ref="crm.view_crm_case_opportunities_filter"/>
|
||||
@@ -884,7 +883,6 @@ for rec in records:
|
||||
<field name="domain">[('type','=','opportunity')]</field>
|
||||
<field name="context">{
|
||||
'default_type': 'opportunity',
|
||||
'default_user_id': uid,
|
||||
'search_default_assigned_to_me': 1,
|
||||
}</field>
|
||||
<field name="view_ids"
|
||||
|
||||
Reference in New Issue
Block a user