Connect to a Model to Import Data

You can connect to another model and import data from it.

• The model you connect to as source for the import can belong:
  • To the same workspace that you are currently working in.
  • If you are using standard username and password authentication:
    • To any other workspace to which you have access in the same customer environment.
  • If you are using Single Sign-On (SSO) authentication:
    • To any other workspace assigned to the same SSO server.
• When you select another model as the source for an import, you can:
  • Choose whether to import from a list, a module, or a saved view in the source model.
  • Choose whether to split composite lists into separate columns.
• After you have performed an import, you can Use Previous Sources for Imports.
• Constraints based on user access rights to module and list data in both target and source model might be applied to the import. This depends on the type of user performing the import. See below Access Constraints in Model-to-Model Imports.

Here, we'll import list data as an example of the general procedure for connecting to another model to import data.

1. In Model Settings > General Lists, select the list into which you want to import data.
2. Click Import.



The Select Source dialog appears:



3. Click Connect to Anaplan Model. The Select Source dialog adjusts and lists the other models in the current workspace.
4. Select the model you want to connect to for the import:

The default source for an import by connecting to another model is List and the lists in the selected source model are shown in the right box. Alternatively, you can select Module or Saved View and the dialog will adjust to show the modules or saved views of the source model in the right box.

If Split Composite Lists into Separate Columns is selected, data from any composite lists in the import source, including composite lists used as module dimensions, is split into separate columns by list level. For more information, see Split Composite Lists by Level.

If you have access to more than one workspace in the current customer environment, then the Select Source dialog will have a Workspace list where you can select another workspace for the model you want to connect to for import. If you select to import a module or saved view, then the list of modules or saved views will be filtered to show only those you have access to.
5. Select the list in the source model in the right box:



Here, we'll connect to the FP&A Budgeting, Planning and Forecasting model and import data from the Product Group list.

6. Click Select. The Import Mapping dialog appears, which allows you to configure how the selected list in the source model will be mapped into the target list and how import items will be uniquely identified.



Here, list items will be uniquely identified using item names or codes.

The Anaplan import process will match only against the names of source items, which will then be matched against the names or codes of target items. The import process cannot use any other property of the source items which is not displayed — such as code or property values — to match against the target items. In this way, Anaplan treats imports from another model in the same way it would a flat file that is imported from an external source. Consequently, if any changes are made to source item names, you must update the import definition to allow for the changes.
7. Check the mappings and make any necessary adjustments and click Run Import. The list import from another model runs and you will see a progress dialog. When the import completes, an Import Completed dialog appears:



Here, the import completed successfully and 10 list items were created. If there are any errors or failings during import, these will be clearly flagged and you can open the Details tab for a detailed report.

8. Click Close. The dialog closes and we can see that the previously empty Product Group list now contains 10 items, all of which were imported from the Product Group list in the import source model.

Split Composite Lists by Level

When you connect to another model to import data, in the Select Source dialog, you can select the Split Composite Lists into Separate Columns checkbox. When selected, any composite lists in the import source, including those used as module dimensions, are split into separate columns by list level.

For example, the following composite list has three list levels: Fastly Vertical (numbered), Fastly Segment (numbered), and Geo L1:

If you import this composite list into another model and select Split Composite Lists into Separate Columns, the Mapping tab displays a separate column for every list level in the composite list:

Note that data from identically-named list items is imported separately when Split Composite Lists into Separate Columns is selected. This makes the setting particularly useful for importing composite lists in which multiple list levels are numbered.

Using the regular mapping options, you can map a composite list to a target module with line items that apply to different levels.

The Split Composite Lists into Separate Columns setting can be edited on the import data source.

Using Previous Sources for Imports

If you set up a model-to-model import and select a list, a module, or a saved view as the import source, the source is retained for future imports and made available to other users based on their user access rights.

If you select a file as the import source, you can decide whether to set a private file or a default file for the file import. By default, files are kept private. For more information, see Overview of Private and Default Files.

Whenever you edit or run an import, retained import sources are shown in the Select Source dialog:

Access Constraints in Model-to-Model Imports

When you perform a model-to-model import, constraints based on user access rights to module and list data in both target and source model are applied and depend on the type of user performing the import.

Module Data

The rules for respecting or ignoring user access rights when performing imports for module data are as follows:

Source Model

• Administrator: import respects user access rights.
• Non-administrator: import respects user access rights.

Target Model

• Administrator: import ignores user access rights.
• Non-administrator: import respects user access rights.

List Data

The rules for respecting or ignoring user selective access rights when performing imports for list data are as follows. Note that this is with respect to read selective access applied to lists — users do not need write selective access.

Source Model

• Administrator: import ignores user selective read access.
• Non-administrator: import respects user selective read access.

Target Model

• Administrator: import ignores user selective read access.
• Non-administrator: import respects selective access.