Legend Component Excluded From Group

Legend Component Excluded From Group

mickdunn
Contributor Contributor
2,688 Views
7 Replies
Message 1 of 8

Legend Component Excluded From Group

mickdunn
Contributor
Contributor

We've had this issue appear on a couple of projects recently. We are using groups for our apartments. At some point (early concept in one project and well into construction docs on another) the groups have started to fail because they get this attached warning.

Basically, "Elements that cannot be grouped were removed from groups of type" etc. Expanding the error reveals a legend component is to blame. Of course, we've never placed a legend component into the group (not that we could if we wanted to). We've never even placed a single legend component in either project! If we back track, select by element id is unable to select the element. The legend component is always the same thing in each project (in one it is a wall type, in the other a floor type). It doesn't matter what we change in the group (add, delete, move any element) we will get this warning. Initially it is just a warning that the element will be excluded by after a bit the corruption moves further and we have to fix groups to continue. Bizarrely, when we do "ungroup" and then use filter to look at the elements selected (that were in the group) there is indeed the rogue legend component and we are able to isolate it and delete it then re-create the group. This is annoying but feasible during design but out of the question in a heavily documented model.

Has anyone come across this before or have any suggestions for what could be causing it?

0 Likes
Accepted solutions (1)
2,689 Views
7 Replies
Replies (7)
Message 2 of 8

Avaris.
Advisor
Advisor

Weird, try to check it and delete it in your warnings.

0 Likes
Message 3 of 8

mickdunn
Contributor
Contributor
As it's in a group all it does is exclude the element but keep it in the
group definition
0 Likes
Message 4 of 8

Avaris.
Advisor
Advisor

That is something I do not understand. Could you post a file where the problem is present?

0 Likes
Message 5 of 8

FAIR59
Advisor
Advisor
Accepted solution
Message 6 of 8

Anonymous
Not applicable

I'm having the exact same problem. "Fix groups" & "Legend component excluded" so I feel your pain... but what was the real solution to your problem?

0 Likes
Message 7 of 8

mickdunn
Contributor
Contributor

Hi - no real solution once the problem has set in besides what I mentioned in the first post (ungrouping, filtering and deleting elements).  To avoid the issue it's as was linked - don't create new types in Edit Group mode.  Things will usually be fine if you create a type and immediately use it, but if you happen to create a type within edit group and then don't place an instance of said type then you'll get the corruption.  For best practice we now tell our users never to create new types within edit group mode.

0 Likes
Message 8 of 8

ShanonC
Explorer
Explorer
Hey All, I had this same issue.
Someone duplicated a type within a group, this corrupted the group overtime and eventually the "fix group" warning was appearing with selective warnings relating the legend components for the specific element that was duplicated in the group edit mode.

Our fix was to write down each legend component ID based on the warning prompts, exit the group editing mode, select the legend components specifically by the ID's and finally delete legend components outside of the group edit mode. A general warning/notification identifies that group elements have been deleted outside of the group edit mode however; as long as we got rid of all of the legend components (In our case we had a warning/legend component count equal to the # of group iterations copied throughout the project as only one element was created using the duplication process described above, I imagine if multiple objects were created this way, you would get one warning & legend component per element edited this way, per group count) following the legend component deletions outside of the group edit mode, the group is now functioning properly without warning.
0 Likes