Community
Participate
Working Groups
Created attachment 206425 [details] The model used to reproduced the issue. Take the attach model. Go to the model explorer. Select Block4, Block0 and Block1. Move them after Block2 all at once by D&D (ie D&D after the future sibling element, not into the future parent element). => Only Block1 appears after Block2. Block4 and Block0 seem to be lost (and their owner set to null...). This issue may be related to bug #357639 (non-atomic move commands).
This bug has been fixed in the version 6275 . The request was badly constructed and the collection to set did not contains all elements.