Presently using Cameo System Modeler 2021xR2HF5 and DOORS 9.7.2 with DataHub. Doing a one way sync from DOORS to Cameo.

Have defined a stereotype which generalizes the Cameo SysML abstract requirement type, and includes definition of specific DOORS attributes of interest. The mapping chosen for the Schema includes assigning DOORS Object Number to the Cameo ID (see pictured):

It would be better to assign the ID to a number like the DOORS Object Identifier (or) let Cameo assign a number on its own, however Cameo arranges the objects in the specification tree, tables, and other places "alpha-numerically", if you choose to let Cameo assign a unique ID of its own the IDs are assigned almost randomly and that ID doesn't help keep a meaningful organizational structure. Thus, having a way to maintain a top to bottom arrangement similar to the source data has value.

The confusing problem I'm seeing is when the Synchronization is complete the Specification window for an object shows it has an ID (See Example):

 And when you open the ID field (you can see ID is blank):

The ID does NOT show in the ID field, and does not show up in Tables, Requirement Diagrams, Requirement Matrices, or the Spec Tree --> it only shows the "HEADING".

If you assign an ID, undo the changes, or"refactor" it, it will suddenly display the ID in all the areas it did not as listed above. This seems like a Bug. Since the ID field was not blank to begin with, shouldn't it be listed in all areas?

I believe this bug might be occurring when you do a "Group Type" mapping, and have selected different schema mappings based on target value values in the DOORS objects? I have performed other imports without using the Group Type mapping and the numbers were displayed when DataHub completed.