The gang in Autodesk Support and Development seem to have isolated at least one clear cut cause for this quirky situation where a model element is associated with a view workset. It shouldn't be possible ordinarily. Apparently this sequence can be blamed:
1) The user selects and enters an edit mode for an element on a view workset, for example this might include plan regions, detail groups, or filled regions.
2 )Instead of using ‘Finish Edit Mode’ or ‘Cancel Edit Mode’ the user instead clicks Undo to exit edit mode.
3) Now back in the project, the user starts adding model elements, such as walls. The walls are placed on the current View workset instead of the active User-Created workset (until the user opens the workset dialog or changes the active workset).
Ryan reports that 2014 has been worked on to help address this situation better, if a user takes the steps above Revit will reset the active workset properly now.
The fix for these poor elements has been (and remains) to use Cut to Clipboard and then Paste > Aligned to Same Place. Just make sure the correct workset is active.
You can read the original post at The Revit Clinic, thanks Ryan!
It also explains how to fix the issue in older versions of Revit.
1) The user selects and enters an edit mode for an element on a view workset, for example this might include plan regions, detail groups, or filled regions.
2 )Instead of using ‘Finish Edit Mode’ or ‘Cancel Edit Mode’ the user instead clicks Undo to exit edit mode.
3) Now back in the project, the user starts adding model elements, such as walls. The walls are placed on the current View workset instead of the active User-Created workset (until the user opens the workset dialog or changes the active workset).
Ryan reports that 2014 has been worked on to help address this situation better, if a user takes the steps above Revit will reset the active workset properly now.
The fix for these poor elements has been (and remains) to use Cut to Clipboard and then Paste > Aligned to Same Place. Just make sure the correct workset is active.
You can read the original post at The Revit Clinic, thanks Ryan!
It also explains how to fix the issue in older versions of Revit.
