Using groups in Revit seems to be a no brainer; we create groups for elements that are repetitive and yet we are still able to quantify them as if they were individual elements. Modify one instance of the group and it will be updated everywhere in the entire project. One can even exclude an element from a group instance to make an exception.
Over the years, Autodesk has improved upon this awesome tool, but has not made it more flexible. If we create a group the wrong way, Revit gets upset. You don’t want to see Revit upset. In actuality, Revit actually gets confused. The main problems occur when groups contain elements that are constrained outside the group. In the simplest form, if one was to create a group of elements including a door, the wall where the door is hosted would need to be within that group. And in many instances the wall could have a top constraint that is not applicable for all instances. It is also common to create groups for casework that rely on the walls for placement, but the walls are not part of the group. In class, you may have heard me say, groups should be “self-centered”. These types of constrained can also cause problems in Design Options.
That being said, yes, there are restrictions that one should be aware of when implementing the use of groups throughout a big project. Here are some tips.
In a previous post, I discussed “What Causes Revit Data Corruption?” and some model maintenance suggestions, “Revit Project Maintenance Guidelines”. I hope you find this article and those listed here helpful. Reach out with questions or comments anytime.
Best Practices with Revit Groups: Rule #1 http://www.seandburke.com/blog
About Best Practices for Groups Autodesk Knowledge Network