Able to duplicate object names. Is that okay?

[Tom Johnson]

I was working in a deliverable model and  could duplicate the names of deliverables.  In fact , when coming back into the model after closing it, I drug a new deliverable, and the system created a deliverable that was already created, e.g. "Deliverable 1."  Is that allowed? 

I wonder what the implications of that will be when imporitng into my ProVision client.  Of course, any object created in the cloud has the possibility to have an existing duplicate in a current ProVision notebook.

[Rpringle]

Duplicate names are allowed although discouraged.

When importing a M3 model that contains objects of the same type with the same name into ProVision only one of the objects will be imported successfully.  The other objects will be ignored.

Regards,
Rachael

[Tom Johnson]

Hmmm....
(1) You would think if this is discouraged, M3 would prevent itself from doing this. In my experience, M3 automatically created a duplicate name that was in the model. Perhaps this is for another release.
(2) If there is not a dup in M3, but there is an object with the same name in ProVision, will ProVision give the standard combine/merge options?

[Rpringle]

(2) No, merge options are not displayed during the CIF import.

[Jim Clendon]

I agree Tom, a very big HMMMMMMMM.

If M3 is creating the duplicates that doesn't like discouraging duplicates.  Perhaps more correctly it is not recommended, but unless you ask the question like you just have, you wouldn't know that LOL

[Todd Greve]

This is one of the many things that are resolved in the next release of M3. The unique name requirements will follow what is used within Provision. Thanks for your loud HMMM's

Any existing duplicates will be handled through a migration process, although the majority of the duplicates out there have the generic names (like 'Activity 1')

Thanks

Todd