Unexpected Behaviour: Project Param locked by View Template can still be editted

[GertjanvandenbroekVKAE]

 While I was working I noticed that I could sometimes change viewport parameters even though they were locked by a view template. Check the screencast; keep an eye on the locked parameters becoming unlocked as I select and unselect the crop region. This is the only example I can find of this odd behaviour. Probably because only sections and views can be driven by templates.

Is it because our project parameter applies to both the view AND the section?

Is this behaviour intended? It seems kind of weird for someone to be able to change variables locked by a view template. It also happens in Revit 2018.

[pawel.romaniuk]

Hello @GertjanvandenbroekVKAE

It looks like expected behavior...

If in your opinion it should works differently please create Revit Idea maybe for many other unseres this is also confusing... 

--------------------
Ihr fandet einen Beitrag hilfreich? Dann vergebt dafür doch Kudos!
Eure Frage wurde erfolgreich gelöst? Dann einfach auf den 'Als Lösung akzeptieren'-Button klicken!

[Anonymous]

@GertjanvandenbroekVKAE, interesting pick up. I am also able to replicate this behaviour in 2018.2 and 2019. 

This looks like a glitch. Investigating further, once you select the crop region and change the value, it does not update the view template value (good). But it obviously does reorder the view in the project browser.

Problem is, if someone who was none the wiser, was to edit it because they wanted it in say "Building A" and then someone (who is more wise) changes the value to "Building B" in the view template, then the value gets updated and the view moves again. This isn't right. I agree, this looks like a bug. It could actually be associated with the glitch I picked up a few years ago with dependent views, which has since been resolved, maybe still some left over!

@pawel.romaniuk. could you please explain your response and what you mean by "expected behaviour". What part is expected and what scenario explains the benefits of this behaviour? Just curious as it doesn't seem right to me.  

[GertjanvandenbroekVKAE]

I can put this in revit ideas yes, but now I'm curious as to why this behaviour is concidered expected.

Most locks are meant to keep people out.

The best analogy of this behaviour I can come up with is that I'd have a locked door with an open window next to it.