Suhani Modi
0546a1297a
Right now, the default invoice policy policy for the products is set to 'delivery'. However, in the case of event ticket products, usually you don't really handle the "delivery" of the ticket. It's most likely to be sent by email automatically. With this commit, the invocing policy for the default ticket product is set to 'order' to ease inovicing the SO. Apart from default product, the onchage method for 'event_ok' is adapted for setting the correct invoice policy and product type. Task Id : 2243915 closes odoo/odoo#63725 Signed-off-by: Thibault Delavallee (tde) <tde@openerp.com>
26 lines
962 B
XML
26 lines
962 B
XML
<?xml version="1.0" encoding="utf-8"?>
|
|
<odoo>
|
|
<data noupdate="1">
|
|
<record id="product_category_events" model="product.category">
|
|
<field name="parent_id" ref="product.product_category_1"/>
|
|
<field name="name">Events</field>
|
|
</record>
|
|
|
|
<record id="product_product_event" model="product.product">
|
|
<field name="list_price">10.0</field>
|
|
<field name="event_ok" eval="True"/>
|
|
<field name="standard_price">30.0</field>
|
|
<field name="uom_id" ref="uom.product_uom_unit"/>
|
|
<field name="uom_po_id" ref="uom.product_uom_unit"/>
|
|
<field name="name">Event Registration</field>
|
|
<field name="description_sale" eval="False"/>
|
|
<field name="invoice_policy">order</field>
|
|
<field name="categ_id" ref="event_sale.product_category_events"/>
|
|
<field name="type">service</field>
|
|
</record>
|
|
</data>
|
|
</odoo>
|
|
|
|
|
|
|