# \[Bug-13088,13252\]Popup Views Fail To Interpret Parameters Which Are Objects Or Arrays

**URL:** <https://forum.inductiveautomation.com/t/bug-13088-13252-popup-views-fail-to-interpret-parameters-which-are-objects-or-arrays/23247>\
**Category:** Ignition Early Access\
**Created:** [March 12, 2019, 12:03pm UTC](https://forum.inductiveautomation.com/t/bug-13088-13252-popup-views-fail-to-interpret-parameters-which-are-objects-or-arrays/23247 "2019-03-12T12:03:44Z")\
**Posts on this page:** 1\
**Showing post:** 7

<div class="post-metadata">

**Author:** ![cmallonee](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/cmallonee/32/6416_2.png) [@cmallonee](https://forum.inductiveautomation.com/u/cmallonee)\
**Post date:** [March 12, 2019, 7:51pm UTC](https://forum.inductiveautomation.com/t/bug-13088-13252-popup-views-fail-to-interpret-parameters-which-are-objects-or-arrays/23247/7 "2019-03-12T19:51:09Z")

</div>

Yah, but my recommendation for passing the queryPath won’t work because we haven’t implemented a “property picker” for the queryPath input, so… You might just need to pass those two properties (project and queryPath), create a custom property (on the View, or Table Component) named whatever (“data” would be good though), bind the value of this new property to view.params.project, then use a script transform to run a named query where you also grab the value of `self.view.params.queryPath`. Something like

```auto
return system.db.runNamedQuery(project=value,path=self.view.params.queryPath)

```

This is a big hassle, but as soon as we get the object/array passing to popups working again it’ll be a breeze. The weird thing is Embedded Views are unaffected, so this is going to take some investigation by Dev.

---

_[View the full topic](https://forum.inductiveautomation.com/t/bug-13088-13252-popup-views-fail-to-interpret-parameters-which-are-objects-or-arrays/23247)._