Revit doesn't like to move detail groups with levels?

[james.levieux]

I'm surprised to find that Revit doesn't like to move detail groups when a level elevation is changed.  I received this enormous list of errors when trying to move a level just 6".    The problem went away after I removed these study sketches. 

We normally draw 2D sketches in groups so that the can be copied to other views.  This allows us update the sketch in one view, and have the revision propagate to the other views.    Is this normal that Detail Groups can't be moved with a level?  This is kinda devastating to our workflow [sad face].

Regards, James

[barthbradley]

Huh?  Can you share your project with us?  

[james.levieux]

Contractually, I don't think I can.  It might need to remain a mystery.  I'll try to replicate it in a clean project using those same groups.  I'll share that if it tests positive.  My hunch is to chalk it up as another unknowable glitch.

[james.levieux]

Test is positive.  I've attached a clean project containing the 6 detail groups.  Three tested positive for glitches.  I printed a initial plan to PDF, then another PDF after the level is moved causing elements to be deleted,  then compared then to find out what items were changed.   The results were surprising, not only were some elements deleted, many others were altered.  The project, groups, and PDFs are attached.

We have a user who likes to use filled regions as a way to group lines.  I'm def going to tell him to use groups instead, but I'm concerned about other time when a filled region is actually necessary, but becomes glitchy.  Any ideas on how can we avoid this in the future?

One last thing to point out.  The groups, when added to the clean project brought with them some Scope Boxes!  Very strange.  I could delete the scope boxes in the elevation view without even causing "excluded elements" in the group(s).