Project Integrity check - fixing issues

[mariop]

Hi,

Is there a way to get pointed exactly to affected object for each line in report from Project Integrity check?

I have plenty of stuff that needs to be fixed and would like to check manually where/what the problem is, not only to hit the button and hope for the best.

Thanks in advance!

Best regards,

Mario.

[Geert Bellekens]

No, just click fix and trust EA.

In all honesty, I've never known this to go wrong in all the years I've used EA, and followed this forum.

Of course you still have your backup if something (probably something else) goes wrong, don't you?

One of the reasons EA can't (often) show you where the problem is, is because it often doesn't know.
If there is an attribute, that doesn't have a parent, where do you want EA to point you to?

And even in the cases it could, what good would it do?
If you have an object that has a classifierID that doesn't correspond to an actual ObjectID? What else but delete the value could you do?

Geert

[mariop]

Well... I am dealing with fairly big repository and Integrity check returned around 190 various issues.

Some portions of this repo are critical, but many will be left behind after migration.

The thing is: I would like to have some control over it. If I just click and hope for the best, it will backfire sooner or later, since it will be almost impossible to check and test all bits and pieces to see what changed.

If I could get details where actually problem is for each of those lines, I might verify if action proposed by EA makes sense and what will be consequences.

Integrity check requirement popped up after I noticed some errors in XMI import on new installation.

Does EA have any options to do this more gently?

Best regards,

Mario.

[Geert Bellekens]

No, just stop worrying and press the button.

My recommendation is to do a project integrity check every month or so, just to keep your repository healthy.

Geert

[qwerty]

Well, my recommendation is to do it once a week. The more often, the better. There should be some "fsck-automatism" that forces a check each x openings. But that's just wishful thinking.

q.

[mariop]

If I understand what you are telling me: it can hardly get worse than already is?

Mario.

[qwerty]

Exactly so. If the check does not work (for whatever reason) you are going to look up your backups.

q.