Profile Upload instantiation update issue

[OlaOludola]

Hello all,
            I have developed a profile, saved it and deployed it to an eap instance. I have been able to instantiate the objects, then I later made further stereotype changes and deployed it, but due to some unknown reasons, whenever I instantiate new objects, the new attributes added does not show up for me but it works fine for all other users accessing the repository. I am suspecting something might have changed from my user access configurations, i will be glad to have some insight. thanks all.

[qwerty]

Might be a version issue. Pre 10 behaves different. TVs are not created dynamically.

q.

[OlaOludola]

Thanks for your reply qwerty, my current sparx version is version 10.0.0.1007. It was working before but stopped working for me all of a sudden.

[qwerty]

The simplest would be that you turned off the MDG in Settings/MDG.

q.

[OlaOludola]

Thanks a lot qwerty, thats a good point you brought up there, The profile is set to active but one thing I noticed is that whenever I try to upload a MDG MTS file, the selectable files are only xml, could this mean that MDG mts files are restricted?  or turned off in the configurations? this might be what is causing the problem I am having.

thanks again

[qwerty]

Well, the MTS files are only used to generate the MDG. They contain the file pointers as to which ones to glue together to the final MDG. The MDG itself is a XML file which (as said) consists of the single profile and other XML files created in preparation.

q.

[OlaOludola]

Yes q, thats true, mixed up files in that regards, ok, thanks, will head back to the issue with the new TVs added to a profile and then uploaded to apply to the working repository, only for me not to see the newly added TVs when i create a new instance of the object. still hoping to have this cleared out.

thanks a lot for your contribution thus far.

[OlaOludola]

So found out it was a profile version issue, I had initially deployed the profile via MDG which puts the profile in the %APPDATA% locally, however I later used an upload approach into the profile in the resource window which doesnt override the previously deployed version using the MDG Import which inserts the profile in the local machine, hence whenever I tried to instantiate new object it goes into %APPDATA% and uses the version there. So I removed that version and was now able to get all the newly added attributes on the new instances.

Lesson Learned: MDG profile version overides manually uploaded profile into resource window, hope this helps someone later.

thank you q.