As the product.packaging model is used for two different business cases, the views shown when the model is used for product packaging must only contains a product_id, barcode, and qty because and when it's used for delivery packages we must show the carrier, barcode, size and wheight. So for usability purpose, we have made two different views explicitly called in each use case.
26 lines
1.2 KiB
XML
26 lines
1.2 KiB
XML
<?xml version="1.0" encoding="utf-8"?>
|
|
<odoo>
|
|
<record id="choose_delivery_package_view_form" model="ir.ui.view">
|
|
<field name="name">choose.delivery.package.form</field>
|
|
<field name="model">choose.delivery.package</field>
|
|
<field name="arch" type="xml">
|
|
<form string="Package">
|
|
<group>
|
|
<field name="delivery_packaging_id" domain="[('package_carrier_type', '=', context.get('current_package_carrier_type', False))]"
|
|
context="{'form_view_ref':'delivery.product_packaging_delivery_form'}"/>
|
|
<label for="shipping_weight" attrs="{'invisible': [('delivery_packaging_id', '=', False)]}"/>
|
|
<div class="o_row" attrs="{'invisible': [('delivery_packaging_id', '=', False)]}">
|
|
<field name="shipping_weight"/>
|
|
<span>kg</span>
|
|
</div>
|
|
</group>
|
|
<footer>
|
|
<button name="put_in_pack" type="object" string="Save" class="btn btn-sm btn-primary"/>
|
|
<button string="Discard" special="cancel" class="btn btn-sm btn-default"/>
|
|
</footer>
|
|
</form>
|
|
</field>
|
|
</record>
|
|
|
|
</odoo>
|