Exporting/Importing Packages (Diagrams w/ Images)

[BSchuyler]

I've been running into the problem for some time now and was hoping the build releases would correct the issue.  Here's what's happening at our company.

1.  I perform an Export on a package in one EA model and select the checkbox "Generate Diagram Images" with the format of Metafile or BMP or GIF.
2.  The export from EA Model #1 is successful.  
3.  I then perform an Import on EA Model #2 with the .xml file from EA Model #1 (setting the checkbox Strip GUIDs).
4.  The import takes place and the diagrams are displayed.
5.  The images which were part of the diagram are either totally incorrect or non-existent.  I must import each image into the Image Manager separately in EA Model #2 and then proceed to correct every diagram which has an image on it by "Selecting Alternate Image" and selecting the image I just added to the Image Manager.

This situation is very time consuming and costly for our company.  It would seem to me when you export the package from Model #1 it should carry along the Image Name and ID from the Image Manager and when you Import the package via the .xml file into Model #2 it should take the images and automatically load them into the Image Manager in Model #2 and directly link the image to the diagrams as they are called out in Model #2.  This would save a lot of "recreating the wheel" activities we must go through everytime we Export/Import packages.

Is there another setting of some type I'm missing to make this process happen or is this a deficiency in the toolset?

Regards,
Bill

[Paolo F Cantoni]

Bill,

From first principles (since I'm not going to test it).  I suspect you'll find that the image numbers of the incorrect ones (if you could get to them - look in t_image table in model 1).  Will correspond to the image numbers of the incorrect images in model 2.  Those non-existent ones are likely to not be available in model 2.

It is a deficiency in the tool set, but one that is hard to rectify without a serious change in underlaying DB design.  For example, you'll probably need to give each image a GUID.  Which, counter to the other GUID, you shouldn't strip!

Report it as it is a defect that does need rectification.

HTH,
Paolo

BTW, if you were really keen (and I DON'T see a resolution to this quickly) I would create an image mapping table and using the DB, I would realign the images so the numbers were the same in both models and fix it behind the scenes.  A bit of work, but since it is consistent, better than human trial and error...