I’m working in a Revit outsourcing firm and ran into a pretty odd issue with elevation tags.
For background, our client has two sheets with the same sheet number, differentiated only by a parameter (the sheet number is a combination of different parameters plus the Revit sheet number). We raised it as a concern, but they insisted on sticking to their company standard.
To make it work on our end, we ended up assigning longer sheet numbers specifically for those sheets. That solved one problem but created another — the longer sheet numbers don’t fit in the standard elevation and section tags.
So, we created a shared parameter to override the displayed sheet number. This worked fine for section tags, but not for elevation tags.
Turns out, elevation tags behave differently since they’re made up of a body and a pointer family. The pointer reads the shared parameter correctly, but the body doesn’t.
Our workaround was… a bit of a hack. We ended up using just the pointer family to reference the view. The tradeoff is that the body family can only host a single view, but in our case that’s acceptable since there are only a few of these instances anyway.
Just thought I’d share in case anyone else runs into something similar. Curious if there’s a cleaner way to handle this.