Importing asset and configuration archives

If a duplicate asset is found for any asset type that is not selected in the Custom over write list, the import fails.

Some types of assets have dependencies on other asset types. For example, APIs have a dependency on policies, aliases, and applications. Some of the dependencies are needed, while others are optional. The required dependencies are always included in the archive when you export the asset. Consider your requirements and select the assets that need to be overwritten in the Custom list. Some asset types can have multiple overwrite options that are organized in the form of a tree. When you select such an asset, all its components are displayed and selected by default. You can select a parent component without selecting any of its child components. However, you cannot select a child component without selecting its parent component. For example, when you select Applications, it expands and displays its components, Strategies, and API Keys. Strategies, in turn, has a component Credentials. You can overwrite Applications without overwriting the API Keys. However, you cannot overwrite the API Keys without overwriting the Applications. Similarly, you can overwrite Strategies without overwriting the Strategy Credentials, but not vice versa.