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!
I’m missing something. Can you elaborate?
How is this:
Any different than this (other than the outcome)?
What exactly are you trying to do again? And what is not working with your current setup? Add a screenshot or two?
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.
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)
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.
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, 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...
