# View.SetCategoryOverrides OOTB node issue

**URL:** <https://forum.dynamobim.com/t/view-setcategoryoverrides-ootb-node-issue/32697>\
**Category:** Revit\
**Created:** [February 27, 2019, 3:02am UTC](https://forum.dynamobim.com/t/view-setcategoryoverrides-ootb-node-issue/32697 "2019-02-27T03:02:30Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![stillgotme](https://avatars.discourse-cdn.com/v4/letter/s/e480ec/32.png) [@stillgotme](https://forum.dynamobim.com/u/stillgotme)\
**Post date:** [February 27, 2019, 3:02am UTC](https://forum.dynamobim.com/t/view-setcategoryoverrides-ootb-node-issue/32697/1 "2019-02-27T03:02:30Z")

</div>

So i tried using the View.SetCategoryOverrides OOTB to turn on and off some of the categories in Visibility graphics but the result was not what it was intended.

The result is that the View.SetCategoryOverrides OOTB node temporary hide.isolate element instead. attached below is the graph and result and dynamo version im using.  
Revit 2016 by the way.

 ![image](https://us1.discourse-cdn.com/flex022/uploads/dynamobim/original/3X/5/f/5f89d62f90b4f389b38f6f0752091e0d3ee8c4a2.png)  
 ![image](https://us1.discourse-cdn.com/flex022/uploads/dynamobim/original/3X/b/1/b1ecbe3fe487440a2acb0a2a70508cfa2e2447c5.png)  
 ![image](https://us1.discourse-cdn.com/flex022/uploads/dynamobim/original/3X/b/0/b0bc767222d0c3bd3c47ea00304ce325997b4b2c.png)

Any help on this issue is much appreciated.

Related Post:

> [@Set Category Visibility](https://forum.dynamobim.com/t/set-category-visibility/24019/5):
>
> You can just use out of the box (OOTB) nodes and avoid the package dependency all together.

---

<div class="post-metadata">

**Author:** ![stillgotme](https://avatars.discourse-cdn.com/v4/letter/s/e480ec/32.png) [@stillgotme](https://forum.dynamobim.com/u/stillgotme)\
**Post date:** [February 27, 2019, 3:59am UTC](https://forum.dynamobim.com/t/view-setcategoryoverrides-ootb-node-issue/32697/2 "2019-02-27T03:59:57Z")

</div>

I tried using on Revit 2017 and it has no issue. Only issue with Revit 2016 i guess? any help on this?
