# Perspective URL Query navigation/update behaviour? **URL:** \ **Category:** Ignition\ **Tags:** ignition83, perspective\ **Created:** [December 4, 2025, 9:51pm UTC](https://forum.inductiveautomation.com/t/perspective-url-query-navigation-update-behaviour/112631 "2025-12-04T21:51:28Z")\ **Posts on this page:** 5\ **Page:** 1
**Author:** ![tyler.robertson](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/tyler.robertson/32/18299_2.png) [@tyler.robertson](https://forum.inductiveautomation.com/u/tyler.robertson)\ **Post date:** [December 4, 2025, 9:51pm UTC](https://forum.inductiveautomation.com/t/perspective-url-query-navigation-update-behaviour/112631/1 "2025-12-04T21:51:28Z")
It’s possible I’m executing this wrong but unsure I have a page where when I pass a urlParams page parameter so that a certain view TabContainer currentIndex is updated and a certain tab is selected (allows me to link to a specific tab) ie: …/data/perspective/client/TaylorFactoryView/El-Cajon?tab=1 If I navigate a link to the address, the ‘tab’ parameter isn’t respected. If I refresh the page, nothing. If I past the address in the navigation bar, nothing (this is chrome/edge and I’ve tried IE as well) if I change the tab _value_, then it works, and changing back works fine too. ie: …data/perspective/client/TaylorFactoryView/El-Cajon?tab=2 then back to: …/data/perspective/client/TaylorFactoryView/El-Cajon?tab=1 Which is ...not great for links. Any insight? Thanks! ---
**Author:** ![Chris\_Bingham](https://avatars.discourse-cdn.com/v4/letter/c/e5b9ba/32.png) [@Chris\_Bingham](https://forum.inductiveautomation.com/u/Chris_Bingham)\ **Post date:** [December 5, 2025, 5:16am UTC](https://forum.inductiveautomation.com/t/perspective-url-query-navigation-update-behaviour/112631/2 "2025-12-05T05:16:37Z")
I’m missing something. Can you elaborate? How is this: > [@tyler.robertson](#): > > If I navigate a link to the address, the ‘tab’ parameter isn’t respected. Any different than this (other than the outcome)? > [@tyler.robertson](#): > > if I change the tab _value_, then it works What exactly are you trying to do again? And what is not working with your current setup? Add a screenshot or two? ---
**Author:** ![tyler.robertson](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/tyler.robertson/32/18299_2.png) [@tyler.robertson](https://forum.inductiveautomation.com/u/tyler.robertson)\ **Post date:** [December 5, 2025, 4:33pm UTC](https://forum.inductiveautomation.com/t/perspective-url-query-navigation-update-behaviour/112631/3 "2025-12-05T16:33:29Z")
hi @Chris_Bingham thanks for the reply - What I’m trying to do is get a url to a _tab_ in a tab container view. I have a page with url and it defaults to, lets say our ‘map’ - however, my HVAC team wanted a link they could bookmark, or shortcut on various systems in our facility that would go directly to the ‘hvac’ tab. Now, that tab is an embedded view - I absolutely could make them another page and link to that (which I’ll do as a workaround) - but I’ve used tabs often as I’ve found them convenient on mobile and avoids a lot of page configuration in Perspective. I was looking at urlParams as a way to pass tab selection so I could link to a specific tab on a page. ![image](https://us1.discourse-cdn.com/inductiveautomation/original/3X/5/9/594d31671a3e8676465d52987bc925b7fd2613e9.png) What’s not working is when I do pass a urlParams value, it doesn’t seem to be respected on first page load (maybe because of order of processing on page startup?). If I then change the value as posted in the first post, it will see the value and change the tab (as the tab index is bound to urlParams) ![image](https://us1.discourse-cdn.com/inductiveautomation/original/3X/3/9/39df555f06bc0eb2adaec22580d5341fb2a1cd64.png) ---
**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:** [December 5, 2025, 4:40pm UTC](https://forum.inductiveautomation.com/t/perspective-url-query-navigation-update-behaviour/112631/4 "2025-12-05T16:40:15Z")
> [@tyler.robertson](#): > > maybe because of order of processing on page startup This, I think, combined with a failure to notify the binding after `page.props.urlParams` is properly populated. I'm curious what you get if you bind to just `page.props` and then conditionally extract `value.urlParams.tab`. ---
**Author:** ![Chris\_Bingham](https://avatars.discourse-cdn.com/v4/letter/c/e5b9ba/32.png) [@Chris\_Bingham](https://forum.inductiveautomation.com/u/Chris_Bingham)\ **Post date:** [December 5, 2025, 10:38pm UTC](https://forum.inductiveautomation.com/t/perspective-url-query-navigation-update-behaviour/112631/5 "2025-12-05T22:38:44Z")
I recall working through this issue before but can't remember the path I went down. I don't currently have access to that project. In another project, I recall utilizing Page parameterization via URL query params. You could attempt to convert to [Passing Parameters to Pages](https://docs.inductiveautomation.com/docs/8.1/ignition-modules/perspective/pages-in-perspective#passing-parameters-to-pages), which could give the added benefit of navigating to specific tabs within the project (without reloading of the project). This project was for a large plant, with tens-and-tens of high-density P&ID-style pages, and a requirement to navigate between (tabs of) pages via nav arrows on each of the pages. Re: urlParams, I'll report back if I'm able to dig something up...