Model update does not preserve checking decisions

[Simone Maioli]

While running some tests, I encountered a problem: when I update the models—after having already assigned checking decisions (such as “accepted” or “rejected”) Those previous decisions are not preserved. This happens even for issues that haven’t changed between the old and the updated model.

In the example I provided, I only changed one parameter of an object between the two models. However, after performing the check on the first model, if I close Solibri and reopen it, then load the updated model form a different path, I lose all the previous checking assignments.

model v1

model v2 with only changed one parameter

I also noticed that the same issue occurs even when I copy and paste the exact same model to a different file path—Solibri still runs the update and all previous assignments are lost. Can anyone explain why this happens? Is this expected behavior or could it be a bug?

[Alex.J]

We also have encountered similar symptoms in more recent versions of Solibri, although we couldn’t track down why.

I first thought my memory was bad, then that it was for specific rules where the issue slide had been created

• either on a folder level where a new issue hat appeared (in the same result folder)
• either on an issue level where additional components had appeared - e.g. minimal height of objects in a room: the results are per room (as the outside component), if one more fixture appears it might trouble the decision history, at least on issue-level.

I think there is a bigger need for optimization for preserving decisions…