The idea to allow a Schema Map to be exported, and then imported as a template is a must have. Thank you for starting down the path of such a feature. I'd like to use it in a large DOORS project I am working in however I believe I've hit a limitation, (or its a user error??). If it is a limitation it seems to be a big one.

https://docs.nomagic.com/display/CDH2021x/Exporting+schema+maps+as+new+templates

DatahubDOORS Using DOORS & DataHub, I am able to customize a group type mapping which is setting requirement stereotypes on import based on one of the DOORS attributes, on a per object basis. This works very well.

https://docs.nomagic.com/display/CDH2021x/Define+target+type+from+attribute+value+mapping

The next step would be to export this schema map and use it (with an import, or as a template) for a dozen other modules in the same DOORS project. But this apparently cannot be done??? Please confirm?

What I'm seeing when I export the schema map to XML is the DOORS module ID# and other very specific information that is specific to the path of the DOORS module used when the synchronization was created.

It's not much use as a "template" if I cannot re-use the export for another module? The effort undertaken to map each enumeration and the group type data takes patience and care. Am I missing a feature that allows this export to be treated as a template with other modules that contain the exact same attributes and enumerations?

I'm thinking I could get the DOORS module ID and manually update the XML; but the schema map will not even recognize another DOORS module until a synchronization has been setup. Am I missing something obvious? Thank you.