Hide unfinished Revisions from index sheets and title blocks

[SeanSpence]

I would like to be able to hide certain revisions, that arent ready to be issued from the index sheet.

Why would this be needed.

Bid packs, Bulletins/Addendumns are all tracked by the revisions manager. Quite often a Project Change Order will come in that requires work to be started in an area that requires tracking through revisions. This work quite often happens parallel with other work for the project.

If other issues have to go out prior to the completion of the PCO, then it is undesireable for the unfinished revisions to show up in the title block or in sheet indexes. Currently the only way to get around this is to temporarily delete the revision clouds, Print then Undo the deletion to get them back.

It would be nice to have an extra check box in the "sheet Issues/Revisions" manager so it can be checked as "Future" or "Not Issued". You could facilitate this by having "Not issued" clouds show up half tone without any entry appearing in the title block or index sheets. The previously issued revision would then show up in the index sheet letting the contractor know what version of the sheet is current.

[lionel.kai]

While I understand the desire for this functionality (and I always like more options/flexibility), you may want to be cautious with this in practice as any changes in the "unfinished revisions" will still be visible on the sheets. For this reason, we tend to "fork" the model (if we need to issue changes to the foundation permit set, for example, we'll make a copy of the model that was used for that submittal) instead of (or in addition to) making the change in the current model.

[SeanSpence]

That's understandable.

We tend to work on massive buildings with multiple plan sheets and different areas of work. That lends its self well to the work flow described. More often than not its needed for bulletins and addendums when only a few sheets are being issued as opposed to the whole set. It's at that point that having the ability to hide an in progress set of revisions from another sheet would be desirable.

[Zach.Neill]

For a fix available now, we bubble future revisions but don't populate the parameters that show in the revision schedule, and set the visibility of tags and clouds to "None". If a revision is going out ahead of that one, we push these future revisions to the end of the list so there's no blank rows in the revision schedule on the sheet.

[SeanSpence]

Thanks @Zach.Neill for the kudos for this and other ideas and this work around.

I typically have a revision called Un-issued changes that I use your tip above with. I make it the first revision so it doesn't change the issued for information until we are ready. Then I move the clouds to the right bulletin or PCO etc when its time to issue that item. Mostly the issue arises when we have a large project when work is occurring on multiple fronts. The project managers get upset when there are issues showing up on the index sheet for sheets not being issued with dates in the future.

Its just a pain to deal with. It would be nice to just click a button and have it hide those items from the index sheets and not have it affect the last issued iteration of those sheets.

[rickt]

I recently ran across this issue on a project. @SeanSpence I like the work around and agree it could be better.

There is already a checkbox for "Issued" revisions (see below).  If there were a way to filter out the revision from a sheet list without removing the sheet information, it seems like it would be a working system.

What if they added a checkbox to the filters tab of the Sheet Index table so that we could control which revisions show up for the sheets?

[rickt]

Here are the images to go with my previous post.

[SeanSpence]

That would work. Even adding a way to filter revisions by date, and not have the sheet disappear because its date is in the future. It just needs to ignore revisions of stuff not issued yet and leave the issued for of the sheet to be the current issue / previous and not the future un-issued.

I love the issued checkbox by the way. I have a sheet schedule included on my start screen that shows only the sheets that have issues that have not been sent out.

I have lost track of the amount of times when something small gets added to the dwgs that is put off until a bigger issue comes along only to be forgotten. Or when something gets done by temp project staff when someone is out and never gets issued / gets forgotten. Now if someone puts anything on that "Un-issued" revision that I mentioned above, it shows up for everyone to see when the project is opened.

[inastrand]

We often have projects where not all sheets are published at the same time. It would be great if it was possible to choose if a revision is shown in sheet lists. Something like a preliminary revision, that could be turned in to an actual revision when needed. That way you can keep track of your ongoing changes / place revision clouds - and still have sheet list with actual publish sheets.

Thx, Ina

[lionel.kai]

Same idea?:

https://forums.autodesk.com/t5/revit-ideas/hide-unfinished-revisions-from-index-sheets-and-title-blo...

[bberggren]

Need a way to hide a specific revision in the revision schedule in titleblock of sheet.  We don't want to lose clouds and deltas.  We just want a specific revision to not populate schedule.

[pieter1]

I think this is a duplicate post to this one: https://forums.autodesk.com/t5/revit-ideas/hide-unfinished-revisions-from-index-sheets-and-title-blo...

[pieter1]

This is a duplicate post to https://forums.autodesk.com/t5/revit-ideas/hide-unfinished-revisions-from-index-sheets-and-title-blo...

[pieter1]

I would prefer splitting the show column in three columns:

- show cloud

- show tag

- show in revision schedule

I wouldn't connect "issued" to whether it shows up in the schedule. We might want to show only some non-issued revisions on the titleblock or hide issued revisions.

[bberggren]

Great ideas!

[SeanSpence]

@Anonymous Great idea,

[lionel.kai]

@pieter1 I like your idea of adding a "show in revision schedule" property to the Revisions dialog - it seems like it would be the most flexible solution/implementation!

[Anonymous]

@Anonymous, your suggestion is exactly what we also direly need in our project. Can't believe it is not there already, it's already been two years since.

[Anonymous]

Hi all! A bit old topic, but maybe this would help some of you.

We have gotten around this by setting the Numbering method of unfinished revisions to "None".
This leaves the revision untouched, and you can still set Show setting from "None" to "Cloud" or "Cloud and Tag".  In our system, revisions are set in order by date, numbering per Sheet. Sequence number is only used to list all of the revisions (hundreds of them in current project) 

This way you can control most of the attributes of revisions in one place, no need for external notes, "fake revision clouds" or line types, but every revision can be marked out in the drawings immediately.

Our problems were mostly occurring in very large projects where there's hundreds of drawings and over ten architects working on the project. It became very hard to stay up to date with the revisions, especially when scheduling the drawing revisions into project database sheet list documents.

[emmi.viitala]

Battling with this issue currently. My solution would be to free the Issued parameter so that you could use it to drive visibility in Revision Schedules. I'm not really familiar with the Revit API, but it seems it might be a 'easy fix' from a developer point of view. 

[GertjanvandenbroekVKAE]

TL;DR:

It'd be really handy of there was a way to only display the revision clouds for the latest revision on a sheet.

We have the possibility of showing all clouds, or no clouds. Would be nice if we could only show the revision clouds with the highest sequence number on a sheet.

An smarter option would be interesting.

Here's the issue:

When we worked solely with PDF's we could generate a new revised pdf with the creation of a revision. We could draw our revision clouds for these revisions. Afterwards, when our pdf's are sent out, we then hide the clouds through the manage revisiions options.

Next time we create a plan, all the irellevant revisions are hidden; and we can draw new clouds for a new revision.

This worked fine.. BUT it already kind of brought some annoyances to the table. But it was do-able

Now however, we're working with ACC & B360, and this is where the current revisioning system runs into problems.

When we Publish our models