# Run Perspective view from JSON File

**URL:** <https://forum.inductiveautomation.com/t/run-perspective-view-from-json-file/89855>\
**Category:** Ignition Early Access\
**Tags:** perspective\
**Created:** [May 2, 2024, 8:03pm UTC](https://forum.inductiveautomation.com/t/run-perspective-view-from-json-file/89855 "2024-05-02T20:03:34Z")\
**Posts on this page:** 6\
**Page:** 1

<div class="post-metadata">

**Author:** ![nader.chinichian](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/nader.chinichian/32/9261_2.png) [@nader.chinichian](https://forum.inductiveautomation.com/u/nader.chinichian)\
**Post date:** [May 2, 2024, 8:03pm UTC](https://forum.inductiveautomation.com/t/run-perspective-view-from-json-file/89855/1 "2024-05-02T20:03:34Z")

</div>

I have a special case where I need to run Perspective Views from its JSON definition on the disk and I can't run it from its path as the views path belongs to other projects on the Gateway.  
Unfortunately, project inheritance doesn't work here as the parent project should be runnable, and when I make it Inheritable it stops running.  
So I wonder is there any hack to make the JSON definition of the view load by Jython?

---

<div class="post-metadata">

**Author:** ![pturmel](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/pturmel/32/3295_2.png) [@pturmel](https://forum.inductiveautomation.com/u/pturmel)\
**Post date:** [May 2, 2024, 8:04pm UTC](https://forum.inductiveautomation.com/t/run-perspective-view-from-json-file/89855/2 "2024-05-02T20:04:47Z")

</div>

Add another layer of inheritance.

---

<div class="post-metadata">

**Author:** ![nader.chinichian](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/nader.chinichian/32/9261_2.png) [@nader.chinichian](https://forum.inductiveautomation.com/u/nader.chinichian)\
**Post date:** [May 2, 2024, 8:08pm UTC](https://forum.inductiveautomation.com/t/run-perspective-view-from-json-file/89855/3 "2024-05-02T20:08:46Z")

</div>

I can't it is an administrator project for other projects in the gateway.  
In this project, I need to see any project resources and it should be dynamic so if in the future a new project is added I to be able see it.

---

<div class="post-metadata">

**Author:** ![pturmel](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/pturmel/32/3295_2.png) [@pturmel](https://forum.inductiveautomation.com/u/pturmel)\
**Post date:** [May 2, 2024, 8:11pm UTC](https://forum.inductiveautomation.com/t/run-perspective-view-from-json-file/89855/4 "2024-05-02T20:11:53Z")

</div>

I don't know any way to do that.

You could probably **list** resources via the gateway's project manager API (SDK stuff), but I don't think you'll be able to open them.

---

<div class="post-metadata">

**Author:** ![nader.chinichian](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/nader.chinichian/32/9261_2.png) [@nader.chinichian](https://forum.inductiveautomation.com/u/nader.chinichian)\
**Post date:** [May 2, 2024, 8:16pm UTC](https://forum.inductiveautomation.com/t/run-perspective-view-from-json-file/89855/5 "2024-05-02T20:16:51Z")

</div>

I can easily list all project names in the gateway and target ignition installed file location to access the projects view JSON file, the problem is running it.  
I wish IA add something like `[projectName]viewPath` as the Tag provider.

---

<div class="post-metadata">

**Author:** ![paul-griffith](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/paul-griffith/32/37249_2.png) [@paul-griffith](https://forum.inductiveautomation.com/u/paul-griffith)\
**Post date:** [May 2, 2024, 8:48pm UTC](https://forum.inductiveautomation.com/t/run-perspective-view-from-json-file/89855/6 "2024-05-02T20:48:36Z")

</div>

I am not sure I even understand quite what you're asking for, but I don't think it's possible.

It _might_ be possible in 8.3. We're planning to make it possible for modules to directly contribute arbitrary resources and/or projects; hypothetically this would make it possible to write a module that got resources from arbitrary other projects, rolled them up together (doing who knows what upon conflict), and presented them to the rest of Ignition as a single "runnable" project.