Voted for the original idea, thanks for posting.
While we're waiting for improvements, a short story:
To work around this issue, I tried to make a door schedule as a material takeoff. We're using long material names to make materials recognizable (Category, material, colour, shininess etc.) but only need to report colour codes (RAL, NCS, Veneer type as a code) in door schedules. Created a custom material parameter ("Värikoodi" for colour code) to hold the colour code as Text.
The material takeoff in a project then schedules, judging by door number ("Oven numero" in the Material takeoff/door schedule), individual bits of geometry (?) in door instances and their nested families, whose geometry's material is linked to the door's material parameter. Curiously, some scheduled items display the custom material parameter value ("Värikoodi"), some don't. I suspect the ones not showing a value at all are bits of geometry in nested families of the host door family, but I could be wrong. All door geometry linked to the material parameter ("Oven väri" for door colour) is in nested families of the host door family. I added a 1mx1mx1m cube into the host to see what happens, but the schedule now reports a volume of 1.162m3, whatever that represents! These items, however, show the correct colour code.
If only there was a way filter out the unnecessary lines in the schedule... Could use 1mx1mx1m (or larger) cube to filter by volume. Doors hardly ever have components of such volume, but with the way volumes are treated by Revit, it now feels like gamble. In addition, there's the trouble of extra geometry in door families and having to turn them off in all view templates/vg overrides.
So, as far I can see there's no really reliable workaround here. Any thoughts?
Attached screenshots of the Material takeoff/ door schedule before and after filtering (I added the "filtering cube" to only one family). Normally, we wouldn't of course display the material volume nor the door material column ("Oven_väri"), just the colour code ("Värikoodi").
Thanks for reading!