Odoo field has an attribute called ‘attrs’. This adds custom attribute to the Odoo form\/tree views. You may use different kind of attributes with attrs like ‘required’, ‘readonly’ or ‘invisible’. For basic, to hide a field regardless of it be an individual entity or parent relation, we use the following:<\/p>\n\n\n\n
This is useful when we are triggering a computed field that we don’t want to show on a tree\/form view. But what if we want to dynamically decide whether to invisible the field or not? For such cases, we usually use invisible with the ‘attrs’ attribute on fields, for example:<\/p>\n\n\n\n You might set the field Seems easy, right? But there is a catch, the above won’t hide the whole column if you are on a place like ‘purchase.order.line’ or ‘stock.move.line’. How can you work on such cases? It only works on individual entry, but not on a relational column. There is an attribute called ‘column_invisible’ same like ‘invisible’ we have used above. But the difference is, you need to set this based on parent value, thus hides a relational column. Here is an example to hide a column called ‘show_expiry’ in a picking operation:<\/p>\n\n\n\n Above code checks the ‘picking_type_code’ value from ‘stock.picking’ model, and hides the column if it’s an incoming shipment and shows when it’s an outgoing shipment. That means, the above, would show the column (show_expiry) if it’s a Delivery to customer location or you already have the product, but won’t show if you are doing a GRN, means you don’t have the stock yet, just arriving.<\/p>\n\n\n\n Pretty simple, isn’t it? Good luck.<\/p>\n","protected":false},"excerpt":{"rendered":" Odoo field has an attribute called ‘attrs’. This adds custom attribute to the Odoo form\/tree views. You may use different kind of attributes with attrs like ‘required’, ‘readonly’ or ‘invisible’. For basic, to hide a field regardless of it be an individual entity or parent relation, we use the following: <field name=’field_name’ invisible=’1’\/> This is … Continue reading “How to hide a column ‘dynamically’ in Tree View on Odoo”<\/span><\/a><\/p>\n","protected":false},"author":3,"featured_media":0,"comment_status":"open","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":[],"categories":[292,271],"tags":[],"_links":{"self":[{"href":"https:\/\/mellowhost.com\/blog\/wp-json\/wp\/v2\/posts\/471"}],"collection":[{"href":"https:\/\/mellowhost.com\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/mellowhost.com\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/mellowhost.com\/blog\/wp-json\/wp\/v2\/users\/3"}],"replies":[{"embeddable":true,"href":"https:\/\/mellowhost.com\/blog\/wp-json\/wp\/v2\/comments?post=471"}],"version-history":[{"count":1,"href":"https:\/\/mellowhost.com\/blog\/wp-json\/wp\/v2\/posts\/471\/revisions"}],"predecessor-version":[{"id":472,"href":"https:\/\/mellowhost.com\/blog\/wp-json\/wp\/v2\/posts\/471\/revisions\/472"}],"wp:attachment":[{"href":"https:\/\/mellowhost.com\/blog\/wp-json\/wp\/v2\/media?parent=471"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/mellowhost.com\/blog\/wp-json\/wp\/v2\/categories?post=471"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/mellowhost.com\/blog\/wp-json\/wp\/v2\/tags?post=471"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}<field name='field_name' invisible='1'\/><\/code><\/p>\n\n\n\n<field name='product_id' attrs=\"{ 'invisible': [('is_set', '=', True)]}\"\/><\/code><\/p>\n\n\n\n'is_set'<\/code> itself as invisible and a boolean computed field like the following:<\/p>\n\n\n\nis_set = fields.Boolean(compute=\"_set_is_set\")<\/code><\/p>\n\n\n\ndef _set_is_set(self):
if self.lot_id.life_date:
self.is_set = True
else:
self.is_set = False<\/code><\/p>\n\n\n\n<field name=\"show_expiry\" attrs=\"{ 'column_invisible' : [('parent.picking_type_code', 'in', ['incoming'])]}\" \/><\/code><\/p>\n\n\n\n