New implementation of KM cost to property support the decimal precision at 3 digits (without changing the decimal precision of all prices in Odoo)
This commit is contained in:
@@ -6,20 +6,6 @@
|
||||
-->
|
||||
<odoo>
|
||||
|
||||
<record id="view_product_hr_expense_form" model="ir.ui.view">
|
||||
<field name="name">private.car.expense.product.template.form</field>
|
||||
<field name="model">product.template</field>
|
||||
<field name="inherit_id" ref="hr_expense.view_product_hr_expense_form"/>
|
||||
<field name="arch" type="xml">
|
||||
<div name="options" position="inside">
|
||||
<div name="private_car_expense">
|
||||
<field name="private_car_expense_ok"/>
|
||||
<label for="private_car_expense_ok"/>
|
||||
</div>
|
||||
</div>
|
||||
</field>
|
||||
</record>
|
||||
|
||||
<record id="product_template_search_view" model="ir.ui.view">
|
||||
<field name="name">private.car.expense.product.template.search</field>
|
||||
<field name="model">product.template</field>
|
||||
@@ -28,20 +14,8 @@
|
||||
<filter name="filter_to_purchase" position="after">
|
||||
<filter name="can_be_expensed" domain="[('can_be_expensed', '=', True)]"
|
||||
string="Can be Expensed"/>
|
||||
<filter string="Private Car Expense" name="private_car_expense_ok"
|
||||
domain="[('private_car_expense_ok', '=', 1)]"/>
|
||||
</filter>
|
||||
</field>
|
||||
</record>
|
||||
|
||||
<record id="private_car_product_action" model="ir.actions.act_window">
|
||||
<field name="name">Private Car Expenses</field>
|
||||
<field name="res_model">product.product</field>
|
||||
<field name="view_mode">tree,form,kanban</field>
|
||||
<field name="context">{'default_private_car_expense_ok': 1, 'search_default_private_car_expense_ok': 1}</field>
|
||||
</record>
|
||||
|
||||
<menuitem id="private_car_product_menu" parent="hr_expense.menu_hr_expense_configuration"
|
||||
action="private_car_product_action" groups="hr_expense.group_hr_expense_manager"/>
|
||||
|
||||
</odoo>
|
||||
|
||||
Reference in New Issue
Block a user