If this were the case, why does it count the revisions when the revision system is set to by project? Why would it count them when set to By Project but not count them when set to By Sheet? Does that mean revisions inside a legend scheduling properly when it is set to By Project is an unintended result?
@Anonymous wrote:
This is as intended. Legend components placed in legend views are simply
2D graphics derived from the available family types and are not counted
in the project. This is to avoid scheduling the graphics that represent
that component. If you place the revision cloud on the sheet, as
suggested, it will schedule.
This is a poor solution as making a change in a legend across a project now requires every single sheet to add a revision cloud. The concept of revit is to reduce repetitive tasks and this one instance is achieving the opposite result. Has anyone submitted this as a request on the ideas board for a change to the Autodesk Team?
-Rich
@RichConyers wrote:This is a poor solution as making a change in a legend across a project now requires every single sheet to add a revision cloud. The concept of revit is to reduce repetitive tasks and this one instance is achieving the opposite result. Has anyone submitted this as a request on the ideas board for a change to the Autodesk Team?
-Rich
Call it what you want. If it worked the way, there would be other undesirable issues.
Just ran into this on a project and the logic makes sense after some wrestling with Revit.
If revisions are tracked "Per Sheet" in the Revision window you cannot tag a revision cloud in a Legend as that Legend could appear across different sheets in a different sequence. Delta 1 on A111 may be Delta 4 on A112 although part of the same issuance if tracked "Per Sheet".
However, if revisions are tracked "Per Project" in the revision window you CAN tag that revision cloud in a legend as that will be consistent across all sheets for a project.
I'm curious - any reason to track revisions by a "Per sheet" numbering method?
The fact that it does tag when the revisions are set to "per project" is a fairly new addition to Revit, maybe in 2020 or 2021. It used to be that either way, revisions in legends would end up with a blank tag. However, that is a separate issue from the original post, which is that whether it's set to per project or per sheet, if your revision on a particular sheet only occurs in a legend, that revision does not populate in the revision schedule in your title block.
Putting the cloud on the sheet will solve the issue, but as others have noted, if that legend occurs on multiple sheets that isn't ideal. If that is the case, another workaround is just putting a single cloud bubble line on the sheet in an inconspicuous spot. That will populate the schedule. I'm not surprised by the Autodesk response from 2007, as legends weren't designed to operate like other views. However, with recent Revit versions they have been given more functionality similar to regular views, so I'm hoping this will be including in an upcoming version.