Resolve Duplicate Names

You can't import a model or control if its name matches that of a model or control already existing in your target instance. This applies both to items you select directly and items your selections depend on.

• If you select a transaction model or control with a filter that specifies a user-defined object, that object and its data set control are also selected for import automatically. (A control that generates data for a user-defined object is known as a data set control.)

• If you select an access model or control that calls entitlements, the entitlements are also selected for import.

• If you select a delivered-content transaction model that calls an imported object, that object is also selected for import.

You can resolve most duplicate-name conflicts during the import process:

• You can rename models, controls, and user-defined objects. The import process can detect whether a model and its user-defined object are revisions of an earlier version; if so, when you import the model, you're required to rename its object.

• You can't rename entitlements or imported objects. If one of these items with a matching name exists in your target instance, the item from the import file isn't imported, and you continue to use the already-existing item.

  You can, however, edit existing entitlements to update them. You can also use a separate import process to refresh imported objects.

Use the Resolve Duplicate Name Violations page to address the naming conflicts you can resolve. The page may list models or controls individually, or may list user-defined objects and their data set controls as paired items.

You must resolve all these naming conflicts before you can move beyond the Resolve Duplicate Name Violations page. Review the Status column to determine which conflicts require your attention. For each item, select an action:

• Rename means that you'll import the item from the import file, but under a unique name that you supply. Do so in the New Record Name field.

  As you import a user-defined object and its data set control, you can rename them with distinct names. This is so even though, if you were to deploy a data set control from a model, its user-defined object would be created automatically, and the control and object would necessarily share the same name.

• Use Existing means that you won't import the item from the import file. The item already existing in your target instance will satisfy any dependency relationships with other items you import. Because there's no need to supply a new name, the New Record Name field is inactive when you select the Use Existing option.

  If you select Use Existing for either a user-defined object or its data set control, you must also select Use Existing for the other item in the pair.

In some cases, Rename is the only action available to you:

• If an import model cites a user-defined object, and the name of that model matches the name of an existing model, you must either rename the import model or remove it from the import job. You'd use the Rename option to rename the model, or return to the Select Items page to remove it.

• If the name of either a user-defined object or its data set control duplicates an existing name, but the other name is unique, you must rename both. Once again, you can give the object and its data set control distinct names.

After acting to resolve naming conflicts, click Validate. This determines whether new names for import items introduce new conflicts with existing-item names. If so, you must resolve them.