Custom table magically appears in locked diagram

[Uffe]

Hi all,


Bit of a weird one. I created a custom table in a diagram, just for playing around with. I created a script in it.

At some point I went to the project browser, located the table element and hit Ctrl-U. EA reported that the table was shown in two diagrams, which I didn't expect. When I went to look, the table I'd created had indeed been placed in that other diagram.

Not by me. And I'm the only one in this project. And the diagram was locked by another user. And the diagram's Last Modified was four days ago. And the table was stretched out to hell horizontally.

So EA dropped my newly-created custom table into someone else's locked diagram.

My question is: is this behavior exclusive to custom tables? Has anyone seen it with other types of element?
I can simply not use custom tables, but if we can't trust EA to maintain the basic integrity of a security-enabled project, then that's going to be a bit of a thing.

I'm on 15.0.1512.


/Uffe

[Uffe]

Oh holy hell. It's not just the one.

I've created a couple of custom tables in the same diagram (which btw is in a package below a different root node to the one where EA inserts the table without being told), and I decided to look through them.

There's another one which exhibits the same behavior. Targeting the same diagram.

So if I hit Ctrl-U on one custom table, then open the diagram from that dialog, I see that table.
If I select the other table, hit Ctrl-U and open the same diagram, I now see the other table.

They don't share a diagram object. Instead, they appear to be placed right on top of each other (and EA presumable shuffles the Z order when locating an element in a diagram).

I noted three other diagram objects referencing non-existent object IDs. Possibly these refer to other custom tables I've created and then deleted. I couldn't say for sure.

I ran an integrity check, which got rid of the three extraneous diagram objects (while telling me the issue was that there was something wrong with their geometry, not that they referred to invalid object IDs, but heigh ho).

I then created another couple of custom tables and fiddled around with them for a bit, but that didn't cause them to appear in other diagrams.

/U

[Geert Bellekens]

I guess you figured it out on your own, but indeed, if EA start to act this weird there's a chance that behaviour is because of some kind of integrity error.

Running an integrity check often solves that.

The worst I have seen was that, all of a sudden, all diagrams placed directly under a package (and not under an element, so where ParentID = 0) where deleted.
Had to restore the backup that time, but then also, running an integrity check solved that. My explanation for this behavior was that one of my elements somehow had gotten ObjectID = 0. Then I deleted that object, causing EA to delete all diagrams where ParentID = 0

(Sparx did fix this particular bug after I reported it)

Geert