Elabore/odoo-usability
9
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

Better handling of the origin field (which can be very long) on PO views

Browse Source
This commit is contained in:
Alexis de Lattre
2018-01-24 21:29:25 +01:00
parent 5c9b6dd702
commit a4c382a546
1 changed files with 15 additions and 0 deletions
Download Patch File Download Diff File Expand all files Collapse all files

15
purchase_usability/purchase_view.xml
View File

@@ -22,6 +22,14 @@
<button name="button_cancel" type="object" position="attributes"> <button name="button_cancel" type="object" position="attributes">
<attribute name="confirm">Are you sure you want to cancel this purchase order?</attribute> <attribute name="confirm">Are you sure you want to cancel this purchase order?</attribute>
</button> </button>
<!-- the 'origin' field can be very long ; it can list a lot of MO or OP!
I think limiting the size of the field would not be the best option,
because the info it carries can be interesting. So we just move it
from the top of the view to the second tab -->
<field name="origin" position="replace"/>
<field name="date_approve" position="after">
<field name="origin"/>
</field>
</field> </field>
</record> </record>
@@ -33,6 +41,13 @@
<field name="state" position="after"> <field name="state" position="after">
<field name="is_shipped" invisible="not context.get('show_purchase', False)"/> <field name="is_shipped" invisible="not context.get('show_purchase', False)"/>
</field> </field>
<!-- the 'origin' field can be very long ; it can list a lot of MO or OP!
I think limiting the size of the field would not be the best option,
because the info it carries can be interesting. So we just remove it from
tree view to avoid layout issues -->
<field name="origin" position="attributes">
<attribute name="invisible">1</attribute>
</field>
</field> </field>
</record> </record>