How does Xoom handle duplicate items in configuration?

Duplicate items cause problems for Xoom, which uses the following workaround.

It is inadvisable to have duplicate items in configuration, but, as Service Optimization does not enforce uniqueness, duplicates can accumulate. Xoom can't model duplicate items because it is unable to assign each a unique Xoom identity. It works around duplication by selecting the duplicated item with the smallest key. In most cases this works because Service Optimization also uses the item with the smallest key in instances where the item is referenced by name. However, if Service Optimization references the item by key, rather than name, the workaround will be unsuccessful.

We therefore strongly advise Service Optimization users delete duplicate items as a routine part of configuration management.