I think the ORM should be smart enough to use {} (that works) instead of None (that causes exceptions) for the for any field that requires a dictionary; and [] instead of None for any field that requires a list.
So, when it finds something like this:
<record id="my_action" model="ir.actions.act_window">
<field name="context"></field> <!-- (currently this does not work) -->
</record>
It should work just as good as:
<record id="my_action" model="ir.actions.act_window">
<field name="context">{}</field>
</record>
Ferdinand: That is the intuitive way for me: Explicitly set the value to none/null/nothing if I want to disable/remove it.
I think the ORM should be smart enough to use {} (that works) instead of None (that causes exceptions) for the for any field that requires a dictionary; and [] instead of None for any field that requires a list.
So, when it finds something like this: ir.actions. act_window" > ></field> <!-- (currently this does not work) -->
<record id="my_action" model="
<field name="context"
</record>
It should work just as good as: ir.actions. act_window" > >{}</field>
<record id="my_action" model="
<field name="context"
</record>
Ferdinand: That is the intuitive way for me: Explicitly set the value to none/null/nothing if I want to disable/remove it.