Not Really, but we make it work...
How we currently handle this is...;
- Creating a 'Callout: Detail-type' view in the Plan (It took me YEARS to get my CW-folks to understand that it is architecturally-wrong to make callouts in Elevation).
- Toggle the "Show in" option to; "Itnersecting Views" to get the callout to appear in Elevations that it is orthogonal to (important when dealing with buildings with organic geometry -- like building grids, this "intersecting views" option is only successful when it intersects perpendicular views).
- Toggle "Parent View" to <none> which allows us to control the height and depth of the view in Elevation View.
There are still issues with this though...
- These "plans" are not Plan-type views (they are Detail-type views), meaning we can't have a callout IN these Detail-type views that callout to an Elevation-type or Plan-type view (this is architecturally backward) -- this seems to be another thing that only "vertical trades" do, since why would anyone else have a detail view call out to a Plan or Elevation -- detail views are a "destination-type" view.
- We can't use Plan-View-Templates on these Detail-type views -- I think I should rephrase this, Revit ALLOWS us to do this (apply a Plan-View-Template to a Detail-type view) but the Detail-Type View ignores settings specific to Plan-type Views which includes...
- System Color Schemes.
- All the Underlay options are gone entirely.
- View Range is swapped for Clipping - meaning the default is inherited from the Parent View until it set to <none> at which point its full controllable with grips or depth distance.
- No Scope Box Association at all.
For the most part it works... until we need to use Underlays, Scope Boxes, or a Project Manager insists on Calling out to a Plan/Elevation-type View from a Detail -- at which point folks start to lose their minds, create Dumb-Callout Families, Duplicate Plan Views and slide them precisely under the Details... thousands of other horrible ideas... etc.