developer unfriendly behaviour of menu - view definition
Example sales
after creating a customised special view (new name) - all the original menu entries use the new one - which is not the intended behaviour.
to regain the functionality of the original module it is necessary to define the following code for every menu entry ( I know this will be easier in V6 as not so many menu entries will exist)
I just want to ask if it is not possible to retain the default behaviour .
<!-- Quotation -->
<record model="
<field name="sequence" eval="1"/>
<field name="view_
<field name="view_id" ref="sale.
<field name="act_
</record>
<record model="
<field name="sequence" eval="2"/>
<field name="view_
<field name="view_id" ref="sale.
<field name="act_
</record>
Blueprint information
- Status:
- Not started
- Approver:
- None
- Priority:
- Undefined
- Drafter:
- None
- Direction:
- Needs approval
- Assignee:
- None
- Definition:
- New
- Series goal:
- None
- Implementation:
- Unknown
- Milestone target:
- None
- Started by
- Completed by