View Full Version : Wall Component Schedule
drewj
2007-03-28, 10:48 PM
I am looking to form a schedule for my walls where I show the name of the wall type followed by a list of the materials from exterior to interior, so far I have got to the stage of creating a material takeoff and including the fields for Type, Material:Name, but this then itemizes every components within the drawing, so if I have 7 components in a wall type and this wall type exists 75 times then my schedule has 525 lines, 518 more than I want.
I am looking for a setting to only include one of each family type I have in the drawing I guess.
Thanks
Overconstrained
2007-03-29, 04:04 AM
Under the "Sorting/Gouping" tab in your schedule properties uncheck "Itemise every instance" at the bottom of the tab.
Does that help??
Dimitri Harvalias
2007-03-29, 04:28 AM
What you are describing sounds like a wall legend. Take a look at legend views in the help file.
The bad news is you can't automatically get the list of all the elements in the assembly but the good news is, once you've typed all the text in you can re-use the legend view from project to project.
drewj
2007-03-29, 04:32 PM
Thanks Dimitri, so just to confirm, there is no way to ensure that all the wall family types used in a project are in the Legend, its a manual process of dropping in the legend components then placing text next to them. If the wall structure changes then you have to remember to manually modify the wall legend as well? If a new wall structure is created then you need to add this to the Wall Legend view?
Drew
drewj
2007-03-29, 04:37 PM
Thanks Overconstrained. I have managed to get fairly close to the requirement by showing the fields "Type" and "Material:Name", then sorting first by Type (Ascending - Header - Blank Line) then by Material:Name (Ascending) and not itemizing every instance, but this just sorts the wall components alphabetically, I would have like to sort them by wall location.
Thanks
Drew
tomnewsom
2007-03-30, 09:40 AM
Not possible, AFAIK - I tried for a while to do this, with all sorts of fancy filtered schedules and things. Should be easy enough to implement in the program, but we'll have to wait for them to do it.
Powered by vBulletin® Version 4.2.5 Copyright © 2024 vBulletin Solutions Inc. All rights reserved.