Lists are groups of related items, such as people in a department, products on a shopping list, or the regions comprising a geographic area. They are fundamental to Anaplan as they define the structure and content of a model.
Anaplan can use a single list as a component in multiple list hierarchies, making list management flexible and adaptable. Composite lists and parallel hierarchies can both be used to maximize the number of ways that the data in a list can be used. List items that belong to a list that doesn't have a parent hierarchy are called orphans.
When a list changes, all the modules associated with it are immediately updated.
Items in a list are referred to as child items, list items, or roll-up items (child items are said to ‘roll-up’ into their parent item).
The types of lists used to build models include flat lists, simple lists, composite hierarchies, parallel hierarchies, numbered lists, and list subsets. Each of these list types has distinct features and is used in particular ways.
Flat lists are groups of items with no hierarchy. Flat lists can contain as few or as many items as required.
Flat lists are rarely used in isolation in model building. They can, however, be incorporated into a composite hierarchy of lists. A single flat list can be used in a number of different composite lists or as properties of other lists.
Examples of flat lists include: employee names, account codes, departments, roles, asset names, etc.
A simple list contains a hierarchy — a parent–child relationship. They can contain multiple levels of hierarchy. For example, in a three-level hierarchy, employees could be organized by departments which are organized in geographic areas.
Data can only be entered against the child items in a simple list. Parent items are seen as aggregates or summary items, rather than data items in their own right. For this reason, it’s preferable to construct composite lists as they’re more adaptable.
List Items and Line Items
List Items and Line Items are completely different elements of a model.
- belong to a list (not to the module the list is used in).
- can be used in any module in the model.
- can be referenced in a formula.
- define the structure of a model (areas, departments, account codes, product lines, opportunity types, etc.).
- belong to the module in which they were created.
- can contain a formula (the formula applies to all cells within that line item, unlike Excel which applies formulae to individual cells).
- represent how your data is measured or expressed (a date, a Boolean value, a calculation, a value assigned from a list, etc).
Lists and Roll-ups
Model Settings > Lists and Roll-ups > General Lists provides an overview of all the lists in a model, displaying information about individual lists, and providing the ability to change some of their attributes.
The maximum number of characters for a list item name is 60 (including spaces).
Default Lists in a Model
All models are created with two default list categories; Organization, which has a Top Level Item list called Total Company (in the Configure tab of the Organization list), and Users, which is dynamically created by Anaplan and contains all users listed in Model Settings > Users who have a Role other than No Access. The contents of the Users list are not editable in General Lists.
These lists are the first list dimensions in your module and, as you add subsequent lists, you extend the number of dimensions in the model.
Tree View displays a hierarchical view of the selected list. As well as importing and exporting list items, you can add, delete, and move them in this view.
There is a limit of 1000 items in Tree View—where there are more than 1000 items, you will be automatically taken to Grid View.
Grid View shows list items with the attributes Parent, Code, Properties and/or Subsets.
Parent drives the aggregation / hierarchy of list items.
Code can be used as an alias for the item name. Imports will automatically match list items on either item name or Code.
List Properties contain metadata—additional information about list items. For example, in a list of Employees, you could add properties such as Employee Preferred Name, the Department they work in, etc.
Properties can be used in line item calculations or to drive the aggregation of data through a model.
|Format||Select and configure the line item formatting—number, boolean, date, text, time period, list, no data.|
|Formula||The property formula. To enter a formula or edit an existing formula, double-click in the cell.|
|Data Tags||Shows any data tags applied to the list property. To apply a data tag, click the ellipsis … and then select one or more data tags.|
|Notes||Shows any notes added to the property.|
|Referenced By||Shows the line items and properties whose formula reference the property.|
Subsets contain some, but not all items from a list. This enables efficient use of the items in a list (without unnecessarily increasing the size of the model). List Subsets can be used in exactly the same way as the list from which they are derived.
You can create a number of subsets from a single list.
When you create a subset of a list, a column is added to the Grid View of that list. Check boxes are displayed to select the items to include in the subset.
|Notes||Shows any notes added to the list subset.|
|Referenced in Applies To||Shows the module and subsidiary line items where the List Subset has been applied as a dimension|
|Referenced as Format||Shows the module and list properties where the List Subset has been set as the line item format|
The Configure tab enables you to change options for the list.
|Top Level Item||Shows the very highest level in the hierarchy or the subtotal into which all lower level list items will roll up into. It's really important that you populate this field to ensure that links and lists will map correctly from module to module. You'll want a top level in nearly all cases, with the exception being a list that is only used as a flag. You can add the top level either on the main General Lists view or on the Configure tab for a specific list.|
|Parent Hierarchy||Indicates whether another list is going to be used for the next level 'up' from the list shown. For example, Opportunities might roll up into Sales Reps, and Sales Reps could roll up into Organization.|
Can be used to group lists based on what type of data the list holds, for example: Organization, Geography, Products, etc.
|Data Tags||Shows any data tags applied to the list. To apply a data tag, click the ellipsis …, select one or more data tags, then click Apply.|
|Selective Access Enabled?||Used to limit users' access to parts of the hierarchies, but should be set up with help from Anaplan support. See Selective Access.|
|Managed By||Reserved for future use and not available for editing.|
|Workflow Enabled?||Used to monitor progress towards completion of a forecast. One list in the model would be set to drive Workflow. See Workflow for more information.|
|Numbered List?||Used to mark the list as a numbered list.|
|Next item index||Contains the index of the next new item in the list. If your organization works with a large amount of data, you might need to reset the Next item index.|
|Use Top Level As Default Page?|
Each list item has an index. The maximum value for a list item index is 999,999,999. The Next item index represents the index of the next new item. Subsequent imports can fail if your organization works with large amounts of data and the maximum value is reached. Previously, you had to contact Anaplan Support to reset the Next item index. You can reset the Next item index if:
- you're a workspace administrator;
- the list item index of the selected list is between 899,999,999 and 999,999,999;
- the selected list does not contain any items;
- the model is not in deployed mode; or
- the model is in deployed mode and the list is a production list.
To reset the next item index of a list:
- Select the list for which you want to reset the entity index.
- Select the Configure tab.
- Click Reset.
You can undo this change by restoring the model history.