Search

Import Data Sources

A basic import process has a source of data and a target to which the data will be transferred.

The source can be …

The target can be …

a file

a list

an external system

a module

a list

a blueprint

a module

users

a saved view

versions

 

Naming import sources

When searching for an import target, 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 that data is imported 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.

Import Data Source (IDS)

To facilitate an import action, an Import Data Source definition (referred to from this point as IDS) is created on the import target and linked to the import source. If an IDS already exists for the source and target, it is amended with any new information.

Although the information in an IDS relates to the source of the import, the IDS itself is stored on the target. A source can have many IDS stored on a range of different targets.

This provides considerable flexibility for data transfer as sources can be accessed across workspaces. For example, where a data hub is used to update data in many workspaces.

The definitions in the IDS play an important role in both import data source re-mapping and in application lifecycle management.

Scenario

In the Model Settings > Source Models screen, the Source field shows the number of IDSs mapped to the selected source. The Imports field displays the number of IDSs mapped to the selected target.

This diagram shows data imports between six source models and six target models across three workspaces. In the simplest example, Source 1, in Workspace A, uses IDS – Source 1 to import data to Target 1. However, we can also see that the same IDS is used when importing data to Target 1 from Workspace C.

Another way of expressing this architecture is in a table, sorted by IDS name. As you can see, IDS Source 2 is used to import data from two workspaces — Workspace A and Workspace C — to three different target models (Target 2, Target 3, and Target 4).

Workspace

Source

IDS name

Target

A

1

IDS 1 - Source 1

Target 1

C

1

IDS 1 - Source 1

Target 1

A

2

IDS 2 - Source 2

Target 2

A

2

IDS 2 - Source 2

Target 3

A

2

IDS 2 - Source 2

Target 4

C

2

IDS 2 - Source 2

Target 2

B

3

IDS 3 - Source 3

Target 5

B

4

IDS 4 - Source 4

Target 5

B

4

IDS 4 - Source 4

Target 6

If a new workspace is added to this site, say, Workspace D, and an import configured from Workspace D, Source 1 to Target 5 on Workspace B, a new line would be added to IDS 4 – Source 4 to hold the configuration information for the import.

Configuring imports

Imports can be created in:

  • Model Settings > Versions
  • Model Settings > Users
  • In a module, Data > Import menu item
  • In a list, Import button

Once created, imports can be amended in Model Settings > Actions > Imports or, for model-to-model imports only, Model Settings > Source Models.

Manage Import Data Sources

Administrators can manage IDSs in Model Settings > Actions, on the Import Data Sources tab.

Administrators can:

  • Create a new IDS by uploading a new file or connecting to a different Anaplan model
  • Edit or remove an existing data source
  • Re-label IDSs; for example if the import source has changed
  • Mark IDSs as production data