View Template include subcomponent from other template

[GallowayUS_com_RonAllen2]

Link a view Template's sub property to include another view templates property.

In the example at right there are basic system overrides:
<NONE>

<APPLY>

Additionally other templates can be selected in lieu of specifying parameters form the current template.

For V/G Overrides IMPORT, look to "_LINK"'s settings to use for the current template.

The VG settings would need to scan to prevent A=B=C=A type loops. and only offer selections for non-recursive selections,

* warn prior to breaking the chain.

This particularly useful when setting LINED Revit Files VG overrides where the model components may be <BY HOST> or hidden alltogether.  These settings would only need to be modified to the "_LINK" tempalte and ant child template that used "_LINK" templates properties could be managed from the one partial template.

There may be cases where sub components point ot other subcomponents so that A=B=C. (e.g. AEFP, ADFP, AEFP-048X-ENLARGED, ADFP-048X-ENLARGED, ETC WOULD 'CASCADE' THROUGH THE TEMPLATES SETTING MORE AND MORE SPECIFIC INFORMATION AS THEY PASSED FROM ONE TEMPLATE TO ANOTHER.

[GertjanvandenbroekVKAE]

I'd imagine that this child template would behave exactly the same as a Template does now. Everything locked in the child will follow the parent, everything unlocked will follow the child template.

The biggest hurdle would be to differentiate between "follow parent / follow child / Unlocked from template". I can imagine that 2 columns of Checkboxes is very unpleasant.

Perhaps it'd be best to have a button on the template editor that brings you to a Parent > Child comparing view, in which you select what elements will be locked to the parent.

[GallowayUS_com_RonAllen2]

Could also use "AEFP-OVERALL-SCALES" (96xp) and "AEDT-ENLARGED-DETAILS"(24xp) to manage sets of acceptable scales for a project- to directly tie to a scales template for direct management and override of view scales in templates.

Being able to tie this directly into V/G as well would be helpful - much like the idea of global parameters, a views settings would be overridden to match a template directly through visibility graphics making the templates more like global parameters in lieu of

'just a template'.

[lionel.kai]

Not a replacement for this idea, but this would help some (and would probably be necessary if sub-templates were implemented): be able to set v/g (Visibility/Graphics Overrides for multiple Views at once

[MichaelWarwick7522]

Like CSS for websites. Would be superb if it came with an improvement to the warning about new element not visible in view that told which view template was hiding the element.

[GallowayUS_com_RonAllen2]

Color coding a 'treeview' would help to identify items directly set vs items set via linked template.

If the View scale for example were deferred to a "ENLARGED SECTION" template - only the scale portion would be set in the current template by the "ENLARGED SECTION".

If another portion of the host or parent template i.e the detail level could also be set to the "ENLARGED SECTION" and would defer that portion to what was specified there.

Being able to click into those and drill down would be beneficial and necessary to track where settings passed through templates came from.

Also the ability to select several categories at once and link them to other templates would be useful.

[purvigirwin]

It would be great to have the ability to nest templates. What do I mean? Have a single template with everything that is common for all projects, and then sub templates that have that content plus additional content based on specific project types. Whenever the main template is updated, that information could get pushed to the sub templates. 

Along with this, it would be great to have the option to connect the project with the template file so that updates to the template can get pushed (manually or automatically) to the projects created with this template. MS word can do this.

[rickt]

   I've been thinking this exact thing for a while now and just took the time to see if there were any similar posts.  This would revolutionize managing view templates.  Can't believe there hasn't been any action on this in the past two years.

VOTE...VOTE...VOTE

[karin]

Creating a tree structure for view templates that allows for small changes in individual views while maintaining a common graphic character. i.e 2 views that look the same but have different scale and linked views.

The current way of doing it is both prone to serious mistakes and uncomfortable.

[Anonymous]

Thumbs up.  I think it would make sense to hew closely to the model of Cascading Style Sheets.

[lmpka]

This would be very useful!   Why is no one voting for it?

Set up your basic template for plans....

Overall views - same  thing, but turn off minor grids

Roof view - same thing, just change graphics for Mech units.

[GlynnisVP]

Any of these suggestions would be very helpful.

Glynnis Patterson

www.ideatesoftware.com

[JSE_GaryA]

Its 2020 and I cant believe this hasnt been implemented yet. As it is now, you uncheck what you want and apply the other view templates to the views. Problem is when you change the applied templated you have to go back and remember what views and reapply. This suggestion already has it setup to where if you change the applied template it is automatic since it has an option to use that template instead of unchecked.

[Curty102]

@GallowayUS_com_RonAllen2 @lionel.kai @AnthonyViscusi and All,

• Agree, a View Template needs ability to reference Graphic Overrides from outside the template itself.
• Agree, View Templates need deeper, modular, more granular control over specific elements within.
• Agree, nailing down the hierarchy is key.  Perhaps a View Template is comprised of Graphic Instances (this would be a new term, see below).

• V/G Overrides Filters especially deserve deeper control since Selection Filters are so powerful.
• Graphic Override Values associated with Selection Filters need the same ability to be saved and referenced elsewhere.  Maybe the override values are called a Graphic Override Set.
• In the View Template Dialogue, under Properties, the Column Heading "Parameter" is actually a misnomer because it also contains entire groups of V/G Overrides (prime example of needing more granularity).  Maybe call this Graphic Instance.
• Together, a Selection Filter + Graphic Override Set could equal a type of Graphic Instance that could be referenced from any View (through V/G) or View Template.

[GallowayUS_com_RonAllen2]

@Curty102  view filters aren't granular enough - but I like where you are headed with a plug-and-play graphic override set. Goal is to affect as many <sub>Categories as possible in as few templates as possible.

[Curty102]

@GallowayUS_com_RonAllen2   Sub-Templates could assist with refining View Templates very well.  I would push this idea even further with globally defined Graphic Types.  Think of Graphic Types as the ingredients and View Templates/Sub-Templates  as the recipes.  Graphic Types essentially extend what was started with Revit Phase Graphic Overrides--allowing users to save predefined graphic sets for the various graphic elements that make up a view.  This could be much more accessible than having to drill down into a Sub-Template just to find a single line type for a single category.  Though I guess sub-templates could be made more navigable if all non-used content was greyed out or omitted for clarity.  See Graphic Type Manager below.

 

[anthonyIntensify]

We have numerous drawing types that each have very slight variations on a major theme. I want to be able to make adjustments to the major theme and have that populated through all my other views. Whether we call it Cascading View Templates, Nested View Templates or Sub View Templates, please can we have this feature. 

[patrick.r.jeffers]

I would love this feature as many views are alike but need minor tweaks to parse through and show the relevant information.

[DBauer.GTT]

@km, @Anonymous I agree the templates should be a parent-child linked list where the children inherit the template values of the parent (and greys-out the ones that are modified by the parent). Would be easy to see in a tree (similar to the project browser) and easy to modify. 

The OP idea is too complicated, causes other problems, and still requires too much modification down the line. Where as the parent-child relationship makes everything visual and easier to understand.

[GallowayUS_com_RonAllen2]

asking to consolidate all linked / View Templates / API to here:

https://forums.autodesk.com/t5/revit-ideas/view-template-honor-link-settings-sub-tempaltes/idi-p/136...

[anthonyIntensify]

The topic of the thread you propose addresses a subset of this topic. Both are valid. Both are important and needed. If you an get some action on them, then please do so.