Workspace administrators can use the Source models pane to change the source of a model-to-model import from one model to another. You can also use this pane to remove a source from an import.

Select the Source models icon in model settings to view, change, or remove sources from a model-to-model import.

The Source models grid has four columns:

  • The first column displays the workspace and source model to which imports in the current model were originally mapped.
  • The Sources column displays the number of import data sources mapped to each source model.
    Each import data source defines how source dimensions and items map to target dimensions and items.
  • The Imports column displays the number of imports that are mapped to each source model.
  • Where an import has been remapped, the Mapped to column displays the location of the current source model.

The Mapped to column only displays a value if the source has been remapped to a different location. The column is blank if:

  • The model-to-model imports for that source model are still mapped to the original location.
  • The source to which the imports were remapped has been removed.

If the original source is unavailable, and the Mapped to column is blank, you must add a new source to run the imports.

If the source to which imports were remapped is archived, the source still displays in the Mapped to column. To run the imports, either unarchive the currently mapped source or select Edit Mapping to change the source.

When you copy a target model from one workspace to another, the source model relationship is copied over in the import data source. This means that if the original source was in the same workspace as the target, the import data source remains set up to import from a source in the same workspace as the target.

For example, if Source A and Target B are in Workspace 1, and you import Target B to Workspace 2, the source displays in the first column as: Workspace 2 / Source A.

To use the import, you must either copy the source model to the new workspace, or remap the import to a new source.

The same applies in Application Lifecycle Management (ALM).

Suppose your development and production models are in different workspaces. Set up an import from Development source A to Development target B, in Workspace 1. Synchronize Development target B with Production target B in Workspace 2 to create the import in the production model. The source model for the import in Production target B is Workspace 2 / Development source A.

For the import to work in production, you must synchronize a production source model with Development source A and remap the import to the new source.