From a4c382a5461761b1652457fbf8daa4132078f386 Mon Sep 17 00:00:00 2001
From: Alexis de Lattre <alexis@via.ecp.fr>
Date: Wed, 24 Jan 2018 21:29:25 +0100
Subject: [PATCH] Better handling of the origin field (which can be very long)
 on PO views

---
 purchase_usability/purchase_view.xml | 15 +++++++++++++++
 1 file changed, 15 insertions(+)

diff --git a/purchase_usability/purchase_view.xml b/purchase_usability/purchase_view.xml
index 39e3f30..8467a19 100644
--- a/purchase_usability/purchase_view.xml
+++ b/purchase_usability/purchase_view.xml
@@ -22,6 +22,14 @@
         <button name="button_cancel" type="object" position="attributes">
             <attribute name="confirm">Are you sure you want to cancel this purchase order?</attribute>
         </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>
 </record>
 
@@ -33,6 +41,13 @@
         <field name="state" position="after">
             <field name="is_shipped" invisible="not context.get('show_purchase', False)"/>
         </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>
 </record>