# Perspective: Passing in an object structure/json into page url param

**URL:** <https://forum.inductiveautomation.com/t/perspective-passing-in-an-object-structure-json-into-page-url-param/39484>\
**Category:** Ignition\
**Tags:** perspective, ignition80\
**Created:** [October 8, 2020, 5:51am UTC](https://forum.inductiveautomation.com/t/perspective-passing-in-an-object-structure-json-into-page-url-param/39484 "2020-10-08T05:51:46Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![nminchin](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/nminchin/32/6911_2.png) [@nminchin](https://forum.inductiveautomation.com/u/nminchin)\
**Post date:** [October 8, 2020, 5:51am UTC](https://forum.inductiveautomation.com/t/perspective-passing-in-an-object-structure-json-into-page-url-param/39484/1 "2020-10-08T05:51:46Z")

</div>

Is it possible to pass in an object/json structure into a page url param? E.g. say I had this object property:  
 ![image](https://us1.discourse-cdn.com/inductiveautomation/original/3X/7/a/7aef56e5bc6d4baec590e1c8f7b1588cdeedfcb4.png)  
Can I pass in `rowData` into the url param?

Note: I’m not saying I have a use-case for this at the moment, but just wondering in case i find one.

---

<div class="post-metadata">

**Author:** ![kgamble](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/kgamble/32/8019_2.png) [@kgamble](https://forum.inductiveautomation.com/u/kgamble)\
**Post date:** [October 8, 2020, 6:51am UTC](https://forum.inductiveautomation.com/t/perspective-passing-in-an-object-structure-json-into-page-url-param/39484/2 "2020-10-08T06:51:25Z")

</div>

Unfortunately it’s not possible without some effort

All perspective sees in your URL is one big long string parameter, however you can use url encoding in a string parameter and reverse engineer it into a dictionary with a transform.

I.e.  
`/param1=123&param2=abc&param3=41v` could be split into an array based off of the ampersand, and then broken apart into keys from there.

This is how I do it currently, unfortunately, I just keep a function in my inheritable project to cover this in any projects I need it for
