Select Source models
You can use source models to redirect the source of production data imports in the following scenarios:
- In Application Lifecycle Management (ALM), segregation of duties can result in administrators in one workspace having no access to models in other workspaces. For example, a development administrator does not have access to the production workspace and cannot map the sources of imports for a production model. If you have access to the relevant workspace, source models let you quickly remap those import sources.
- You can define exactly which models are to be used as production data import sources to manage performance issues.
- Where there are multiple, cloned models (perhaps used for load balancing), you can update all the models consistently in Source Models
to update production data. Model synchronization updates structural information.
- When building, or deploying a model, you can rapidly redirect a model’s existing data sources, either temporarily or permanently.
The source model and target model must share the same structural information: the lists provide the structure of the model and 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. Import data changes as a result of end user activity and scheduled import processes, so should be checked thoroughly.
Data objects must be common to both models. Where data objects do not map to each other, the import fails.
If you are remapping import sources, you must have access to both the target and source workspaces and models.
Even though you can see models you do not have access to, you cannot select them as a source or target in the mapping process. If you select Edit Mapping, you can only view the workspaces and models you have access to.
Model mode and status
The mode and the status of models influence whether you can edit import source mapping.
For example, if the model mode is set to standard or deployed, and the status is either online or offline, you can edit both structural and production data.
If the model is archived or locked, the status is not applicable. You cannot edit any data and Edit Mapping is disabled.
Naming import sources
When searching for a target specified in an IDS definition, the search looks for:
- Module names
- List names
- Saved views by module name and saved view name
Lists, modules, and saved views must be 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 is unable to differentiate between them and the import fails. If lists have the same name, but contain different data, you could import the wrong data or inadvertently overwrite data.
Remapping import sources
A toolbar provides options to Edit Mapping, Remove Mapping, search for a workspace and model name, and refresh the view. You cannot use keyboard shortcuts.
You can only select one item in the grid. If you select multiple items, you cannot use Edit Mapping and Remove Mapping.
If a target workspace and model is visible in the Mapped to column, 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 and model is selected.
Source Models grid
- The first column shows all the models across a site, except Archived models. They're listed by workspace in alphabetical order, then by model name in alphabetical order.
- The Source column shows the number of import data sources mapped to the selected source.
- The Imports column records the number of import data sources mapped to the selected target.
- The Mapped To column shows the name of the target model. If blank, the chosen model has either never been used as a source, or has recently been synced and requires the mapping information to be re-entered.
To edit mapping:
- Select Source Models
in the model settings bar.
- Select a mapping from the list, then select Edit Mapping.
- Select a workspace from the Workspace list.
- Select a model from the list, then select OK. The workspace and model display in the Mapped to field.
Failed imports due to remapped source model
If you attempt an import from a renamed module, saved view, or list within a remapped source model, the import fails.
To fix imports from renamed modules, saved views, or lists within a remapped source model, you can:
- Change the name of the remapped source model back to its original name.
- Use Source Models > Edit Mapping, Data > Imports, or Actions > Import Data Sources to update the data source to include the new name for the module, saved view, or list.
To remove mapping:
- Select Source Models
in the model settings bar.
- Select a mapping from the list, then select Remove Mapping.
- Select OK to remove the data source in the Mapped To field.