# Hiding column in treeview on specific model
**URL:** https://discuss.tryton.org/t/hiding-column-in-treeview-on-specific-model/5672
**Category:** Developer
**Tags:** stock
**Created:** [November 4, 2022, 1:12pm UTC](https://discuss.tryton.org/t/hiding-column-in-treeview-on-specific-model/5672 "2022-11-04T13:12:33Z")
**Posts on this page:** 8
**Page:** 1
Hi,
I need some help to hide a column in a treeview in some cases.
I defined a button for a custom wizard on outgoing assigned inventory moves (customer shipment).
```auto
class Move(metaclass=PoolMeta):
__name__ = 'stock.move'
@classmethod
def __setup__ (cls):
super(). __setup__ ()
cls._buttons.update({
'update_quantity_wizard': {
'invisible': ~Eval('state').in_(['assigned']),
'depends': ['state'],
},
})
@classmethod
@ModelView.button_action('module.wizard_update_quantity')
def update_quantity_wizard(cls, moves):
pass
```
Updating stock.move\_list\_shipment.xml:
```auto
```
With this result:
Button is visible when move state is “Assigned”:
Button is invisible for other states:
Until now, everything is ok 🙂
But this button is specific to Customer Shipment. So i don’t want to display the column “Pick” in Supplier Shipment model.
After a discuss on Irc, the suggestion was to use view\_attributes and context to hide the column.
```auto
class Move(metaclass=PoolMeta):
__name__ = 'stock.move'
@classmethod
def view_attributes(cls):
return super().view_attributes() + [
('/tree/button[@name="update_quantity_wizard"]', 'tree_invisible',
Eval('context', {}).get('shipment_in', False)),
]
```
And adding a variable in the action context:
```auto
```
But, this is not working and i’m still viewing the column “Pick” in the supplier shipment form:
Thanks for your help 🙂
---
> [@maxx](#):
>
> `Eval('context', {}).get('shipment_in', False)),`
It must be `Eval('shipment_in', Fase)`
> [@maxx](#):
>
> And adding a variable in the action context:
>
> ```auto
>
>
>
>
>
>
>
>
>
> ```
Are you sure this is actually updated? It is always odd to update existing XML record.
Indeed this can not work because the view you try to modify is not the view of the action because it is a One2Many.
For now the context is not passed to the screen of One2Many. I guess it could be taken via the view.
---
> [@ced](#):
>
> It must be `Eval('shipment_in', False)`
Ok, i did this way previously.
> [@ced](#):
>
> Are you sure this is actually updated? It is always odd to update existing XML record.
Yes, i saw the variable in the context when doing “tryton -v”
> [@ced](#):
>
> For now the context is not passed to the screen of One2Many. I guess it could be taken via the view.
What do you mean by “taken via the view” ? Adding ‘context’ in the field definition of “inventory\_moves” ?
---
> [@maxx](#):
>
> What do you mean by “taken via the view” ?
When the widget instantiate its Screen, it could retrieve the context from the parent Screen via the `view` attribute.
---