1. Import and export data
  2. Map Imports to New Data
  3. Change the Source of a Model to Model Import

The Source Models menu option in Model Settings enables administrators to quickly define alternative sources for model-to-model production data imports.

Source Models removes the need to copy models between workspaces — a single model can provide source data for many models across a number of workspaces. This is particularly useful for sites that deploy a data hub or have multiple workspaces as part of application lifecycle management.

Source Models redirects import sources between Anaplan models by amending the Import Data Source (IDS) on the import target. Imports from external data sources are configured in Data > Import menu options.


There are many situations where administrators will benefit from using Source Models to redirect the source of production data imports:

  • In application lifecycle management, segregation of duties may dictate that administrators in one workspace don’t have access to models in other workspaces. Perhaps a development administrator doesn’t have access to the production workspace and cannot map the sources of imports for a production model. Source Models provides the production administrator with the ability to quickly remap those import sources (providing they have access to the development workspace).
  • Performance issues can be managed by defining exactly which models are to be used as production data import sources.
  • Where there are multiple, cloned models (perhaps used for load balancing), administrators can update all the models consistently using Source Models to update production data (model synchronization is used to update structural information).
  • When building, or deploying a model, administrators can rapidly redirect a model’s existing data sources (either temporarily or permanently).

Import structure

The source model and target model must share the same structural information: the lists that provide the structure of the model and, consequently, rarely change. Lists that comprise structural information are not marked as Production Data.

Import data is contained in lists that are marked as Production Data. This data is volatile: changing as a result of end user activity and scheduled import processes.

Data objects must be common to both models. Where data objects don’t map to each other, the import will fail.

Access limitations

The administrator who is remapping the import sources must have access to both the target and source workspaces and models.

Although administrators will see models they do not have access to, they will not be able to select those models as a source or target in the mapping process. When an administrator selects the Edit Mapping button, only those workspaces and models they do have access to are displayed.

Model mode and status

The mode and the status of models influence whether import source mapping can be edited:

If the mode is Standard or deployed and the status is either Online or Offline, administrators can edit both structural and production data and the Edit Mapping... button is enabled.

If the mode is Archived or Locked, the status isn't applicable. Administrators can't edit any data and the Edit Mapping... button is disabled.

Naming import sources

When searching for a target specified in an IDS definition, the search looks for:

  • Modules by module name
  • Lists by list name
  • Saved views by module name and saved view name (ModuleName.SavedViewName)
It is important that Lists, Modules, and Saved Views are named uniquely to ensure the data imports as you would expect it to.

Saved Views are often used as sources for imports. If several share the same name, Anaplan will be unable to differentiate between them and the import will fail.

If lists have the same name, but contain different data, there is the potential to import the wrong data or inadvertently overwrite data.

Remapping import sources

The Model Settings > Source Models grid is a centralized view of all the model-to-model import sources and their current target.

A toolbar provides options to Edit Mapping...,Remove Mapping..., Search for a workspace and/or model name, and Refresh the view.

Administrators can only select one item in the Source Models grid. If multiple items are selected, the Edit Mapping... and Remove Mapping... buttons will be disabled.

Because the grid is read-only, there are no keyboard shortcuts.

If a target workspace/model is visible in the Mapped to field, both the Edit Mapping... and Remove Mapping... buttons are enabled. If the Mapped to field is blank, the Edit Mapping... and Remove Mapping... buttons are disabled until a target workspace/model is selected.

Source Models grid

The grid contains four columns:

  • The first column shows all the models across a site (except Archived models), listed by workspace in alphabetical order, then by model name in alphabetical order.
  • Sources
    The Source field shows the number of Import Data Sources mapped to the selected source.
  • Imports
    The Imports field records the number of Import Data Sources mapped to the selected target.
  • Mapped To (Workspace/Model Name)
    The name of the target model. Where this field is blank, the model selected has either never been used as a source, or has recently been synced and the mapping information must be re-entered.

Edit Mapping

  1. Select Model Settings > Source Modules.
  2. Select a mapping from the list and click Edit Mapping...
  3. On the Workspace list select a workspace.
  4. Select a model from the list displayed and click OK.
    The workspace/model will be displayed in the Mapped to field on the Source Models grid.

Remove Mapping

  1. Select Model Settings > Source Modules.
  2. Select a mapping from the list and click Remove Mapping.
    A dialog will remind you to check that your users have the necessary access rights for any import processes.
  1. Click either:
    1. OK to remove the data source in the Mapped To field; or
    2. Cancel to cancel the process and return to the Source Models grid


We may update our documentation occasionally, but will only do so in a way that does not negatively affect the features and functionality of the Anaplan service.