Is there any chance to get baselining and comparison to work after somany years?

[PeterHeintz]

After many years I gave baselining and comparison a chance again.
This feature if working would be very valuable, but it does not.
I have a package with flat requirements in it have dependency relations to other elements within the model.
Creating a baseline and comparing it directly afterwards shows me that anything has changed, but of course it is not.
All requirements indicate changes in dependencies, and the reasons as far as I this is that in the baseline the model “Visibility” attribute is stored as “Scope” attribute within the baseline by mistake:
Further on, several requirement elements show differences in notes which does not exist and this seems to be related to kinds of carriage return handling different in the model note in relation to the xml-file

[PeterHeintz]

By the way the problem exits in the same manner for the new stnapshot feature in V17 as well!😒

[Geert Bellekens]

I think I had a look at this feature back in version 9 or something and came to the same conclusion.
The noise/signal ratio is simply to high to be useful.
Too bad this apparently hasn't improved enough in the meantime.

Geert

[PeterHeintz]

Even worst! Now the new snapshot feature has the same problem.
To say something positiv, at least it uses the same wrong code!

[Takeshi K]

The 'Visibility' in the Properties window of Enterprise Architect is stored in the t_object.Scope column internally, so this is not a bug.

The problem is that EA shows the internal column name in the Comparison view. It should be shown as 'Visibility,' the same as in the user interface.

[PeterHeintz]

Maybe "Visibility" is stored in a "Scope" filed in the DB for whatever reason.
But anyhow it is not just a display issue!

The compare shows a difference without changing anything.
On side it shows "Visibility/Scope" is set to "public" (what the dependeny relationship is by default) and on the other side, it states that the value is "not set" at all, and therfore it shows a difference.

Further on, the "Notes" are sometimes shown as different (even not changed) and this seem to happen if a carriage return is in the text.

For sure both ar bugs. A compare of unchanged things should just show nothing.

[PeterHeintz]

I just find out, that when I do the same thing on a SVN controlled package the "Visibility/Scope" "public/not set" difference is in addition as well shown on my elements/requirements!

[PeterHeintz]

And an other thing! When I do the compare with an exported xea file, at least the problem with the "notes" and carriage return is gone!

[PeterHeintz]

Next try with a transfered feap file shows for the compare the problem with the notes is gone as well, but the "Visibility/Scope" issue remains.