Titleblocks and shared parameter availability outside of a label
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report
So to start, I'm totally familiar with the use of shared parameters and labels in titleblocks and anywhere else in Revit.
My issue, and I can't be the first person to struggle with what seems to such a be a rudimentary requirement, is this:
1. I create a shared parameter for a value I wish to display on my titleblock - lets say its a scale - I add it to the label and it displays - Great!
2. I also want to use the value of this parameter to control something else on my sheet via a formula, such as the visibility of a scale bar - Problem!
The shared parameter in question is loaded directly into the label used to display it - it is not available anywhere else in my titleblock family such as the Family Types dialog where the rest of the titleblock parameters live. Even if I load the exact same shared parameter into the family itself it has no connection to the parameter loaded into the label. This is a problem for me since many elements in a titleblock are fundementally related - the scale and scalebars being just one obvious example.
Now I can think of ways around this such as using an embedded generic annotation family containing a label in my titleblock instead of a label directly to display values of parameters created in the titleblock family which CAN be used for other purposes but I seem to be jumping through hoops to recreate fundemental relationships that should already exist or be possible in a fully functional titleblock... or is it just me? Autodesk specifically tell us to go down the shared parameter route to display 'custom' values in the title block.
If I'm missing a screamingly obvious methodolgy for joined up titleblock creation please let me know!
(As an aside: why would I create a new scale parameter? because I've never produced a drawing that had only 1 view at 1 scale on it and as soon as this is not the case Revit's scale parameter gives up and hides... but that's another issue for another day.)
