Wall/Partition Schedule - Code not in use

[martinlopez7Z4BZ]

Hello All,

I am creating a wall/partition schedule the problem I'm having is that the office they want codes that are not used in the project to be shown like the image below. "Code not in use / Not Used" The only way I have seen for them to appear on the schedule is actually drawing a wall in the project and adding the "Not Used" in the description parameter. This is a good work around but don't want random walls being in the project just so they appear on the schedule. So my question is if there is a way for all the types of partition to appear regardless of them actually being drawn in the project.

Thanks for the help.

[barthbradley]

Put all your wall/partition types in a pre-existing phase (demo'ed in existing) and set your schedule's reporting phase to "None". This will return a report of all the walls in the project. Then you can create a calculated parameter to return a value of "Not in Use" by evaluating a condition -- such as for every wall that is in the "pre-existing" phase, but not the "new construction" phase. 

[martinlopez7Z4BZ]

Thanks for the quick reply. 

So I still need to actually build the wall in the project, just placed in a different phase, for it to appear on the schedule?

[barthbradley · Accepted solution]

Sure. Just define all your wall types and place one instance of each in a phase that pre-dates the Existing Phase and Demolish them in a Phase that occurs before the actual project construction phases begin.  Make sure you set your Wall Schedule's reporting Phase to "None" so it will report all the walls, including the wall in the actual construction phases.  You probably don't even need to write a calculation parameter. You could simply put "Not in Use" in the "Comment" field for all the walls in the "Pre-existing" Phase.  Include "Comment" field in your Schedule, and you'll readily see (group, sort, filter, etc.) all those walls that are "Not in Use". 

[martinlopez7Z4BZ]

thanks for your help!! worked perfectly 🙂

[barthbradley]

You're welcome. Thanks for the Solution Credit.