Find the Mistake (or: unable to save object after migration)

[Carsten Schmitz]

Find the problem. Due to lack of spoiler tags, scroll all the way down for the solution.














































































































































Jepp, in this object that was last edited in 2011 and migrated (along with the whole database) through the versions to version 12.3, there is no interpretter set at all. This results in a java stack trace error and a user unable to save any changes. A quick look at the stack trace hints at the problem, and once you click one of the radio buttons, you can save the object.

I do not intend to file a support ticket because I can not replicate this, which usually means it's not going places, and also I filed tickets for corrupt objects after migrations before, and I really think we're done here. My customer takes the workaround instead.

It would be neat if Automic had some sort of data consistency check and this makes that case once more. Alas it doesn't. But from now on, when you encounter an old object you can't save, this may be the explaination, and a quick fix along with it.