Publish data and visualizations to a dashboard to enable users to understand and work with a model.
Classic dashboards are not supported for new customers. Build Apps or Pages in the User Experience instead.
Anaplan's dashboard elements enable you to design your dashboards to suit your workflows and meet the needs of your users' model roles.
Plan before you publish
You can publish any dashboard element to a new dashboard, but we recommend that you prepare your dashboard first. Learn how to design dashboards to ensure that the data and visualizations serve the workflows you want to create.
Whatever layout you choose, ensure your dashboard components match the order the user accesses the data they enter. This helps the person who enters the data work efficiently.
Publish modules views and lists as grids
You can publish a module view to a dashboard as a grid. This enables you to view and edit module data without the need to enter the module itself.
If you want to edit list data, or reference a list in an action, you can publish a list to a dashboard as a grid.
You can also publish module page selectors, or publish a list as a page selector. This enables you to change the context of the data to match the item you select.
Visualize data
Publish charts to a dashboard to enable users to visualize data. As you adjust data in a grid this also affects any chart you publish to the same dashboard. This can help you understand the impact of changes.
Run actions from a dashboard
You can publish actions to dashboards, so non-workspace administrators can run actions in a model.
Note: Assign and assign only actions can only be run from a dashboard. Publish the action to a dashboard that also displays the list that contains the parents to which you want to assign items. You can publish the list as a grid, as a page selector, or in a module view that contains the list.
Publish list properties, list subsets, and line items
You can also publish list properties, list subsets, and selected line items to a dashboard.
These features function similarly to a field card on a board in the User Experience. However, as these dashboard elements are published individually, you can move them to different areas of your dashboard when you design your dashboard layout.
It's best to publish these features alongside a dashboard element that defines the context. For example, a page selector that displays the list.
Example
An HR manager wants to enter employee details into an Employees module. Employees uses an Employee names list and various line items to capture different aspects of the employees' data. The HR manager isn't a model builder, so they don't have access to the module.
To enable the HR manager to enter the data, you can create an Employee details dashboard. Publish line items from the module as a series of fields, and use Employee names as a page selector. The HR manager can enter employee data into the fields for each employee and use the page selector to switch between employees.
