Delete and clean up loose objects
While working with Quadri for Windows, you can get "Loose objects" (also called "Orphan objects" or "Non-result objects"). These are objects that do not belong to any tasks. This is the result of modules not working properly or sometimes also user choices. We are working on removing these errors.
The result of loose objects in the workset, is tangled with other problems and can together make it difficult to reserve or run tasks.
Here is an attempt to describe what a user can do to clean up projects where there are loose objects. It looks complicated, but is actually just a series of rather easy steps.
Round 1: trying the simple way
First step:
Right click on the cloud symbol for the project in the Quadri for Windows Explorer Window.
Select "Delete loose objects"
Answer "Yes" to any questions.
Second step:
Reserve all tasks named "Loose objects...", "Orphan objects..." or "Non-result objects".
If the reservation fails, try to reserve only some of these tasks (or one by one, if that is necessary). If you can not reserve a task that is select by it's own, look at the error message: if it is because of another reservation, try to get the person holding that reservation to release it and try again when that is done.
Now try to delete the tasks you could reserve. Always answer "Yes" to any question about wanting to delete the result features. If you get a message that you "Can not disconnect features from network objects", you will not get any features deleted.
If you succeeded in deleting some tasks, but not others, you might try a new round. Sometimes deleting one "Loose objects" task makes it possible to delete another.
If you can not delete the task, see: Can not delete task with loose objects .
After you can not delete any more such tasks, delete all of them that you could reserve, but select not to delete result elements. You will get a warning, just ignore that.
Now save, share and release what you have done so far. Sometimes a task with net element(s) that could not be deleted, have falsely included that net element. Check if you got a new "Loose object" task during sharing.
Also right click on the could and select "Delete non-result features" and check if maybe everything is OK already (no "Loose objects" tasks left and "Delete non-result features" says there is nothing to delete.
Round 2: more advanced cleanup
First step: try to reserve again
Try to reserve all unreserved "Loose objects" tasks one by one.
If you get errors about: "Objects in conflict", see: Something went wrong, under "A code with date and time...".
Round 3: undeletable tasks with loose objects
If you still have tasks with "Loose objects" you can not delete, but can reserve, see: Can not delete task with loose objects
Round 4: repeating the operations
If anything was successfully deleted in step 1-3:
share and release everything
Repeat step 1-4 until no change was made.
If you now have no tasks with "Loose objects", but "Delete non-result features" claims there are readonly features that are loose: share and release everything, disconnect your workset and download a new. Try to "Delete non-result features" again.
If there still are loose objects left, contact Trimble Support by sending an email to civil.support@trimble.com with the name of the project and the subject: "Can not delete loose objects".