Thanks for the replay,
Yeah... the use case shown in the User manual is in the wrong direction of my use case. The use case in the manual is to let ignition user a number set in a view property to then set the url parameter that is set in the route.
Using this use case, here is my use case. After that happened, that a view has a tankNumber that ignition intercepted to set the url parameter and rendered a totally new view, in this new view that just rendered, I need access to that URL parameter /tank/2. It was set by a different view (and I got that working), but this new and different view needs access to the URL param /tank/2. In my use case I don't need to set the url param, I want to use the url param in the view. it is the other way around. Hope that makes sense.