Profile Stereotype Instances Sync issue

[OlaOludola]

Hi All,

         I will be grateful to get any insight into this issue I am having. Each time I import an updated project profile and then perform the "Sync tagged values and constraints" function on the repository elements, Some of the instances would not get the updated tagged value why some will, I investigated the ones that dont and cant seem to know why they dont get it, it is a shared repository where other people instantiates objects from the profile. I have investigated why that happens but still cant seems to figure out why. I also tried making sure everyone has closed the repository but to no avail.

Any insight will be very helpful and appreciated.

Thanks

Ola

[qwerty]

I can't answer your question but if I read correctly you're doing that synch quite often. So my question would be: why? It means you made essential changes in your profile. And that should be avoided as fas as possible. A profile migration is not that trivial.

Further: what version of EA do you use? TV handling has changed from V9.3 essentially.

q.

[OlaOludola]

Thanks a lot for your reply Qwerty,

 My profile updates are actually very infrequent, this current update I am doing is the first time in about 6months, I had experienced this issue before but at that point the repository is quite small so I did some manual adjustments, however at this point the repositroy has expanded and I can no longer do what i did before, i currently use sparx 10.  I will be grateful to know more about the little caveats in applying profile changes to a repository other than how I know at this time. Still trying to see what's causing the partial instance sync.

thanks again.

Ola

[qwerty]

The issue is rather complex and I can't give any good advise. The only thing I can say is that a synch will just add new stereotypes and not replace existing ones. Nor will it remove those that are no longer defined in the profile. So if you have something like drop downs you need to do either some API programming or some clever SQL to update the TVs (that is to replace the memo field only/correct now invalid choices). I just remember that a profile migrations were blood, sweat and tears and none went through without accident.

q.