# Perspective URL props to docked window

**URL:** <https://forum.inductiveautomation.com/t/perspective-url-props-to-docked-window/38550>\
**Category:** Ignition\
**Tags:** ignition80, perspective\
**Created:** [September 10, 2020, 1:21pm UTC](https://forum.inductiveautomation.com/t/perspective-url-props-to-docked-window/38550 "2020-09-10T13:21:36Z")\
**Posts on this page:** 1\
**Showing post:** 3

<div class="post-metadata">

**Author:** ![Carl.Gould](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/carl.gould/32/7262_2.png) [@Carl.Gould](https://forum.inductiveautomation.com/u/Carl.Gould)\
**Post date:** [September 10, 2020, 6:19pm UTC](https://forum.inductiveautomation.com/t/perspective-url-props-to-docked-window/38550/3 "2020-09-10T18:19:47Z")

</div>

Fundamentally, you’re right - this shouldn’t be so difficult. Perhaps we should simply set the page URL parameters on all views that have the proper input defined. So for example, if you had the page mounted at `/mypage/:paramName` and _both_ your primary view and a docked view defined an input named `paramName`, we could simply set both.

In the meantime, however, there _is_ an easier way than passing messages, which as you surmised, is not really that safe (you can’t rely on one view loading before the other, their loading speed is relative to their complexity and is largely at the whim of the browser)

The “page” props are themselves a writable space. There’s no issue in you using that namespace for your own purposes. For example, you can do this in your main view’s startup event:  
`self.page.props.paramSharing = {'paramName': self.params.paramName}`

And then you can simply bind something in the docked view to `page.props.paramSharing.paramName`

(there’s nothing special about the name “paramSharing” you can put them in whatever organization you’d prefer)

---

_[View the full topic](https://forum.inductiveautomation.com/t/perspective-url-props-to-docked-window/38550)._