Project Browser sorting, View templates & dependent views.

[Anonymous]

I have a view list sorted by a custom parameter we use for our Project browser sorting. All the views are sorted by there intended sheet series. ie: 100 Series Plans, 200 Series RCP etc etc. 

Some of the plans have dependent views. (We'll come back to this point shortly)

The other day I went through the process of renaming the 'sorting parameter' due to project scope changing. Fairly simple process as most views have view templates so I simply updated the parameter and all the views reconfigured themselves under the correct browser sorting names. ie: '100 Series Plans' changed to '1000 Series GA Plans'

BUT... when i went to the schedule view list which sorts by this parameter, i noticed some views were still using previous sorting names. eg: '100 Series Plans', weren't all changed to '1000 Series GA Plans', my view list still showed views assigned with 100 Series Plans. I realised the culprit views were infact the dependent views! 

The parent view had the correct sorting name displayed as assigned by the view template, but this did not update the dependent views. See attached. 

This seems to occur because the dependent views were created after a view template was assigned to the parent view. Therefore the dependent view takes the same information. If you create a dependent view first, then assign the view template to the parent view, the dependent view doesn't update the sorting parameter, but the VG obviously apply. 

This is quirky little thing, but now the problem - very annoying because the only way it appears i can fix this is to remove the view template from the dependent view, then manually update the parameter to the correct sorting title information, then reapply the view template, one view at a time!

Any thoughts on this? solutions or ideas? 

[Anonymous]

Error.

[Anonymous]

I wanted to give this a nudge. It caught me off guard again recently using 2016 and I think the problem is still the same in 2017.

If it is a dependent view and you change the view template for the parent view, shouldn't logic dictate that the dependent view parameters such as the one described above also update?

[Anonymous]

Include the parameter in the view template, meaning put the value of the parameter and add a checkmark to it under the Include column. That will get the value updated in all the views that have this view templated assigned.

[Anonymous]

Hi Alfredo, thanks for the reply, but I will have to prompt you to read the full post describing the problem. The parameter IS included in the view template.

To see the problem,

1. open a blank arch template
2. create a project browser sorting text parameter.
3. apply a view template to your ground floor
4. now create a dependent view of the ground floor
5. check the parameter for each view... they will match
6. go to view templates and change the value for browser sorting, click apply
7. the parent view will report the new parameter, the dependent view does not.

Also, if you apply the view template to the parent view AFTER the dependent view is created, the parent view will report the view template and text parameter value correctly, the dependent view will also report the view template, however the text parameter for browser will be blank! 

[ToanDN · Accepted solution]

I confirm this behavior.

[Alfredo_Medina · Accepted solution]

This time I tested this (before writing my previous reply I did not make a test). I can confirm that the issue happens. Even if the parent and the dependent views have the same view template assigned, and even if the parameter is included in the view template, when the value of the parameter is changed in the view template, the value of the parameter changes in the parent views but not in the dependent views.

[Anonymous · Accepted solution]

@ToanDN / @Alfredo_Medina 

ok, thanks for confirming.

Now, where is an Autodesk rep when you need one

Would be good to get this on the Knowledge Network Troubleshooting, hopefully something they can resolve in the future. 

[Anonymous · Accepted solution]

So, Just an update on this one. 3 years later and a test on Revit 2018.1 seems to demonstrate this problem being resolved. Woo! 

Never saw a knowledge network article on this, probably still a good idea as 2016 & 2017 are still in play and it can say if upgrading to 2018, problem is resolved! 

[chrisplyler]

Wow.

I just want to point out that you wouldn't have to manually correct EVERY view one at a time. You can select multiple views at the same time in the Project Browser, and then change parameter values for them all at once, including the View Template that is assigned.

[Anonymous]

Hi Chris, yes that's right. Whenever I come across this problem though, I just use a schedule sorting by view template. This allows you to collect all the views at once without having to select them, I simply change the template to 'None' and then back again to apply the change. 

I actually think this bug goes way back to I think 2012/2013 when we had the scenario where view templates didn't sync. I just think this was missed when they addressed that.