Community
You can not do what you want with the out-of-the-box capabilities.
It might be possible for someone with better programming skills than I possess to create a custom application that would scan the drawing, collecting all of the room numbers for a particular door type, create a string that lists all of the room numbers and finally pushes that string into a manual property for each door of that type, which you could then put in a schedule table as a column.
If it were up to me to create the content, I would say that someone needs to decide what feature takes precendence. If showing the room number is more important (which is what my office does), then list each door. If making the schedule table as short as possible is more important, then do a type schedule.
It might be possible for someone with better programming skills than I possess to create a custom application that would scan the drawing, collecting all of the room numbers for a particular door type, create a string that lists all of the room numbers and finally pushes that string into a manual property for each door of that type, which you could then put in a schedule table as a column.
If it were up to me to create the content, I would say that someone needs to decide what feature takes precendence. If showing the room number is more important (which is what my office does), then list each door. If making the schedule table as short as possible is more important, then do a type schedule.
I never said you could not create a "type" schedule in ACA; in fact, you can. If you add a quantity column to a schedule table, all identical rows in the schedule table will collapse into a single row, and the quantity column will display the number of objects that single row represents. The key to remember here is that the datum in EVERY cell on each row have to be the same in order for the rows to combine. That is why putting the room number as a column in your schedule table will generally result in a separate line for each door (excepting Spaces served by two or more identical Doors). What I said would be hard to do would be to get the lines to collapse while still having a column that lists all of the rooms in which that door type occurs.
I have no idea what type of work you do, or what sorts of doors you typically have. Assuming that you want to show door size in your schedule table and that the string you use for the door type "ID" either incorporates size, or you are willing to have multiple lines with the same "ID", with different sizes on each line, you can set up door types and by carefully selecting the properties the schedule will show, you can get a type schedule. If you do not want to show the quantity column in your schedule table, that column can be hidden.
If your mark does show the size (eg, A1 = type A door, 3-0x7-0; A2 = type A door, 3-6x7-0, etc), and you use the same typical sizes project after project, you can build the types into your styles provided you set up standard sizes in your styles. This blog article goes into more detail if you are interested:
http://architects-desktop.blogspot.com/2009/11/aca-scheduling-by-mark.html
I have no idea what type of work you do, or what sorts of doors you typically have. Assuming that you want to show door size in your schedule table and that the string you use for the door type "ID" either incorporates size, or you are willing to have multiple lines with the same "ID", with different sizes on each line, you can set up door types and by carefully selecting the properties the schedule will show, you can get a type schedule. If you do not want to show the quantity column in your schedule table, that column can be hidden.
If your mark does show the size (eg, A1 = type A door, 3-0x7-0; A2 = type A door, 3-6x7-0, etc), and you use the same typical sizes project after project, you can build the types into your styles provided you set up standard sizes in your styles. This blog article goes into more detail if you are interested:
http://architects-desktop.blogspot.com/2009/11/aca-scheduling-by-mark.html
Wow. I read your post, then I read the posted document and I have no idea what you are trying to do. I am willing to blame that on "Friday Brain Syndrome". If your goal is to pass data attached to a Space to a Door, you can do that with a Location property (limited to one Space per Door or Window object).
We do not include information in our Door Schedule about the surrounding Wall construction; we make the contractor look at the drawings to determine throat depth for the frames, etc. But getting Wall data into the Door or Window object is a good use of the Anchor property, and is what I would use if I had to describe the Wall hosting the Door in the Door Schedule.
I think I got lost when you started talking about Spaces and Areas. What version are you using? In recent versions, the "old" Space and Area objects have been combined into one "super" Space obejct that can be 2D (like the old Areas) or 3D (like the old Spaces, but even more so, with the freeform option). What is your end goal in having the Doors aware of the hosting Wall and having the Wall aware of a Space to which you are anchoring the Wall (assuming that is possible - I have never tried to do so)?
We do not include information in our Door Schedule about the surrounding Wall construction; we make the contractor look at the drawings to determine throat depth for the frames, etc. But getting Wall data into the Door or Window object is a good use of the Anchor property, and is what I would use if I had to describe the Wall hosting the Door in the Door Schedule.
I think I got lost when you started talking about Spaces and Areas. What version are you using? In recent versions, the "old" Space and Area objects have been combined into one "super" Space obejct that can be 2D (like the old Areas) or 3D (like the old Spaces, but even more so, with the freeform option). What is your end goal in having the Doors aware of the hosting Wall and having the Wall aware of a Space to which you are anchoring the Wall (assuming that is possible - I have never tried to do so)?
Back in the bad old hand-drawing days (and even pre-ACA-ADT CAD days), we did not have a "chart-type" Door Schedule. We had a four-position code at each Door, and the "Door Schedule" drawing had an explanation of what the values in each position meant. The first position was a letter, and each letter was tied to a specific door size. The second position was a numeral, and each numeral was tied to a door elevation/door material/door construction type. The third position was a letter, and it was tied to a frame elevation/frame material type. The final position was a numeral that indicated the hardware set number, as described in the Specifications. So the code at the line/arc representing the door in plan might be A1B8, where the "A" meant 3'-0" x 7'-0", "1" meant full flush hollow metal door, "B" meant a hollow metal frame with an integral sidelight (configured as shown in the elevation of type "B" frame) and "8" meant hardware set 8. This worked well to indicate what each door should be, and avoided the tedium of drawing a big grid, filling in the text and then trying to keep it coordinated.
That it left it up to each subcontractor to assign a "mark" to each opening (which most will do). This created a small problem on larger projects if the doors/frames/hardware were not being handled by one subcontractor and the various subcontractors did not agree on a single set of "marks" for the project - checking the submittals and cross comparing were a challenge when the door references were not consistent. So we started adding our own "door ID" to each opening, based on the served room's room number, in addition to our four-position code, and, in the specification, mandated that the subcontractor(s) use our ID to identify the opening.
It was not until we started using ADT and its "automatic" scheduling that we started adding chart-type door schedules to every project. We still tag each door with the ID, which then ties back to the schedule. The opening size is given explicitly on the schedule, but we still use letters to identify a door type and numbers to identify a frame type. We have a door style for each type, so that is in a style-based property. To avoid a gajillion styles, the frame type is an object-based property, but we do have a list of standard frame types - if you use one, a formula property automatically calls up the right material designation. Non-standard frame types require filling in the material designation in a separate object-based property, which the formula property reads in when a non-standard frame type is encountered.
On larger project, that means several sheets of schedule tables, but it if the model is created properly, the tables just "fall out" of it, and having each door in the schedule makes it easier to check the submittals and verify that all doors have been included.
That it left it up to each subcontractor to assign a "mark" to each opening (which most will do). This created a small problem on larger projects if the doors/frames/hardware were not being handled by one subcontractor and the various subcontractors did not agree on a single set of "marks" for the project - checking the submittals and cross comparing were a challenge when the door references were not consistent. So we started adding our own "door ID" to each opening, based on the served room's room number, in addition to our four-position code, and, in the specification, mandated that the subcontractor(s) use our ID to identify the opening.
It was not until we started using ADT and its "automatic" scheduling that we started adding chart-type door schedules to every project. We still tag each door with the ID, which then ties back to the schedule. The opening size is given explicitly on the schedule, but we still use letters to identify a door type and numbers to identify a frame type. We have a door style for each type, so that is in a style-based property. To avoid a gajillion styles, the frame type is an object-based property, but we do have a list of standard frame types - if you use one, a formula property automatically calls up the right material designation. Non-standard frame types require filling in the material designation in a separate object-based property, which the formula property reads in when a non-standard frame type is encountered.
On larger project, that means several sheets of schedule tables, but it if the model is created properly, the tables just "fall out" of it, and having each door in the schedule makes it easier to check the submittals and verify that all doors have been included.
![Autodesk Design & Make Report](https://forums.autodesk.com/t5/image/serverpage/image-id/1350519iCB55845EBFC43016/image-size/large?v=v2&px=999" "Autodesk Design & Make Report")
