Duplicate Nested Namespace Names Not Allowed?

[dougcl]

Hi folks, FM 8.3. Dismayed to find that I cannot have two namespaces of the same name within a model, even though they are nested under different namespaces.

Here is how this came up:

We have a lot of models that we want to link in as segments into a master model. Problem is, each one of the models is built according to a standard and they all feature at least one standard namespace in them. When linked, the master model detects the duplicate namespaces across the linked models and refuses to link. Note though that creating further levels of nesting with namespaces doesn't help.

It seems that no namespace is ever really nested under another. They are all at the root level in the model despite the tree representation in the GUI display. Makes no sense to me, so I am curious if this is the way it really is.
Thanks,
Doug

[blom0344]

If you familiarize yourselve with the way xml works, then it all starts to make a lot more sense. As the model is stored in an xml format, the limitiations xml throws up are evident I guess..

[dougcl]

Perhaps you misunderstand the question. In FM this appears to not be allowed:

Customer (Namespace)-> Import (Namespace) -> CUSTOMER_TBL (Query subject)
Charges (Namespace)-> Import (Namespace) -> CHARGES_TBL (Query subject)

because the namespace name "Import" is used twice, even though it is nested in different namespaces. In other words, while FM shows them nested in separate namespaces, the GUI representation has nothing to do with anything. All namespaces are at the root level. Is this true?

[blom0344]

Does this make sense in your case:

Problem(Abstract)
Linking two models with the same common namespaces within them will result in the following error message due to a collision of the object names. 
 
Symptom
BMT-MD-3602 Unable to link model segment. The following items in the model segment have object names that conflict with the source model.
Object name: Object Name ID:Object Name 
 



Resolving the problem
Import only the non-common namespaces and folders from each model. If the common objects are required then they will be imported as child objects of the non-common namespaces from each linked model.
For example, if you have two child models: A and B. Each model contains a common linked model called "Common Namespace" and model A has a namespace called "Namespace A" and model B has "Namespace B".

When you link models A and B into a master model you will be presented with the list of objects from each in the link dialog. To link these models choose only "Namespace A" and "Namespace B". The "Common Namespace" will also be imported if required but it will be nested as a child object of both "Namespace A" and "Namespace B".

KB ref 1339004