Re-use of Smg VIEWs across projects

First of all, let’s have a quick look at the basics of how smgView works.
As for many other things in seemage, it is based on IDs.

Each part or assembly have is own and unique ID. We call it Ident or IdentGeom.
Example :

This ID is automatically created during the translation from CAD to seemage format.
This ID is also used in the update mechanism.
Moreover, the ID for a part will change each time you make the translation of the part.

By editing the smgView in an XML editor (XML Pad for example) you will see several different CLitView. In each tag, you have the configuration settings.

Hereafter an example with a part, an assembly and the main root :
ROOT : ID 9e9a40cc18e6b6d5
ASM : ID bf60098ebacc710d
PART1 : ID 8afdb35398ed06f4

When making a change to the part (i.e. moving), the ID that is used to move PART1 in this configuration is formed from parent pieces: 9e9a40cc18e6b6d5.bf60098ebacc710d.8afdb35398ed06f4.

So if you want to re-use a configuration in different projects (so re-use a smgView file), you must make the ID match.

But as said before, ID are unique and will change each time one make a translation from CAD.

So the solutions are :

• Translation is managed by a PLM/PDM and while smgXml, smgView and smgSce files are created, default ID created by the translation will be changed for your internal references. This solution needs a part of integration. We have this situation in many seemage clients where seemage Sync in managed by the PLM (Enovia, MatrixOne, Smarteam etc.)
• Id are changed manually by editing the XLM but can be long and painful. You can use any string you want (expect # and .)
• In v4.2, if you use Sync to translate the files, you can choose to use “names” instead of our IDs. As “names” can be the same in different projects, it will be more easy to make the ID match