In summary, if you applied a view template to a view and subsequently created a dependent view afterwards, changing a custom text parameter via the view template would result in the value updating in the the parent view, but not in the dependent view.
|Dependent View not updating custom project parameter|
I am pleased to report that a test on Revit 2018.1 today seems to demonstrate this problem as resolved!
Finally! Now we can confidently make changes to things like browser sorting without 'left over' parameter values hanging around.
Unfortunately though, it doesn't seem like a fix ever made it to Revit 2016 or 2017, which a number of users are still on. If you are curious, to replicate the problem, follow the below steps:
- Open a blank architecture template
- Create a text project parameter for the 'views' category (eg: For browser sorting)
- Apply a view template to your ground floor & type a value in the new parameter.
- Now create a dependent view of the ground floor
- Check the parameter for each view... they will match
- Go to view templates and change the value for the custom parameter, click apply
- The parent view will report the new parameter, the dependent view does not.