# Open as view not working

**URL:** <https://community.fibery.io/t/open-as-view-not-working/1360>\
**Category:** Bugs & Issues\
**Created:** [February 10, 2021, 1:40pm UTC](https://community.fibery.io/t/open-as-view-not-working/1360 "2021-02-10T13:40:28Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![Haslien](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/haslien/32/493_2.png) [@Haslien](https://community.fibery.io/u/Haslien)\
**Post date:** [February 10, 2021, 1:40pm UTC](https://community.fibery.io/t/open-as-view-not-working/1360/1 "2021-02-10T13:40:28Z")

</div>

Think it came with latest patch. Open as view does nothing and gives an error in console:  
 ![image](https://us1.discourse-cdn.com/flex020/uploads/fibery/original/2X/1/198d7800579c21ec1436f25d8d829a306509242d.png)

---

<div class="post-metadata">

**Author:** ![mdubakov](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/mdubakov/32/10_2.png) [@mdubakov](https://community.fibery.io/u/mdubakov)\
**Post date:** [February 10, 2021, 1:51pm UTC](https://community.fibery.io/t/open-as-view-not-working/1360/2 "2021-02-10T13:51:35Z")

</div>

Does refresh help? Can’t reproduce so far

---

<div class="post-metadata">

**Author:** ![Haslien](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/haslien/32/493_2.png) [@Haslien](https://community.fibery.io/u/Haslien)\
**Post date:** [February 10, 2021, 7:04pm UTC](https://community.fibery.io/t/open-as-view-not-working/1360/3 "2021-02-10T19:04:02Z")

</div>

I tried again, reloaded page with cache disabled, and it persists. Seems to be happening only for one entity however. Other entities work fine.

---

<div class="post-metadata">

**Author:** ![mdubakov](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/mdubakov/32/10_2.png) [@mdubakov](https://community.fibery.io/u/mdubakov)\
**Post date:** [February 11, 2021, 7:22am UTC](https://community.fibery.io/t/open-as-view-not-working/1360/4 "2021-02-11T07:22:11Z")

</div>

We reproduced the problem, will look into it today!