For more information about plan types and included capabilities, see the Smartsheet Plans page.
As project requirements evolve, deploy change to all sheets, reports, and dashboards within a Control Center portfolio.
For more information about plan types and included capabilities, see the Smartsheet Plans page.
You must have Project Lead access to Smartsheet Control Center to make global updates. For information about Lead access, see the Access Smartsheet Control Center.
Find out if this capability is included in Smartsheet Regions or Smartsheet Gov.
As your project progresses, you may need additional information to keep the project running smoothly. For example, you might want to add an At Risk column, so users can flag tasks that they may miss a deadline.
Before you create and run Global Updates, familiarize yourself with the available Global Update types and their capabilities. Global Updates offers the following options:
Global Updates don't apply to title widgets that link to Smartsheet items. To implement this change, you need to edit the individual dashboard.
When you select an update, the plus sign on the tile changes to a checkmark.
Testing is required.
Select Create & Run to test and validate the proposed update against active projects and sheets.
The test creates a temporary copy of a project, ensuring you don’t apply changes until you’re certain you want them.
Hover over the Success message to see an update summary.
To edit the update, select Close to close the test, make your changes, and run the test again.
Select Close to return to the Update Summary page to test the update on additional projects . Select Test Update, and select the project to test. Do this as many times as you like until you're confident about your changes.
You have one last chance to review and confirm the proposed changes and select where you want updates applied.
If you want to update your templates, check Apply update to the base project template(s).
Global Updates remain on the Global Updates page. You can run them whenever you want. Select the update and run it as above.
To update an existing Global Update:
For answers to common questions related to Global Updates and Smartsheet Control Center generally, see Smartsheet Control Center FAQ.
For more information about plan types and included capabilities, see the Smartsheet Plans page.
Use Global Updates when you have made the following changes to a dashboard template:
Global Updates don’t apply to title widgets that link to Smartsheet items. You need to edit the individual dashboard to implement this change.
In Smartsheet, go to the blueprint source folder and make your changes directly to the dashboard template.
Name the update after what it does, for example, Move budget widget.
When you run the update, Control Center searches each project to find the dashboard that matches your dashboard template by either ID or name. It also shows you projects that don’t have a matching dashboard, either because a match wasn’t found or the dashboard wasn’t included when the project was originally created. You can add the newly edited dashboard to those projects when you run the update.
Global Updates rebuilds your entire dashboard and relinks widgets to the reports and sheets every time you run an update. Changes aren’t reversible, so run the update on one project and check the results before you run it on all your projects.
Global Updates for dashboards currently don’t update widgets with the sheet summary.
When building your dashboard templates for use with Control Center, it’s important to structure your source data in a way that avoids potential issues with Global Updates.
Data in the Primary column is used to identify the first and last row for the range of a chart or metric widget, even if you haven’t included this column as a part of your data range. Avoid using your Primary column in widget data ranges.
If duplicate or blank values are found, the widget breaks when you run a Global Update.
Use one of the following options to structure your source data:
In this example, the Primary column contains duplicate values (Very High, High, etc.). By using hierarchy, issues resulting from duplicate values can be avoided when running Global Updates. This is because the lookup for the Primary column returns the parent row and the child row.
With this method, it’s still possible to have duplicate values if you have two or more parent rows with the same name, and child rows with the same name under those separate parent rows.
If you use a report in a chart widget for your dashboard templates and has no results to create a chart from, it doesn’t map correctly when you provision your projects. Make sure you have at least one data point in your report template.
Errors related to missing data can occur if the referenced cells from a template sheet have never contained any data. To avoid this, ensure that your template sheets have cell history by right-clicking the cell and selecting View Cell History.
This is the most reliable method for making sure the dashboard matches your projects, even if you change the name of the dashboard. The dashboards in the project are direct children of the dashboard template in the blueprint source folder. Control Center easily identifies them as such and makes changes.
Widgets pull data from sheets and reports. The best way to avoid trouble with them is to make sure the sources feeding the widget are consistent and up to date.
If a widget on a project dashboard doesn’t work correctly after an update, check the following:
If a report or sheet is deleted from the project, the widget can’t find the data it needs.
The same error can happen if a widget refers to a report or sheet that was added to the project later, or if the item wasn’t created because it was optional.
If the Primary column value changes during the project, it no longer matches the template and the widget won’t find the data.
The update locates the cells by matching the column name and value in the primary column with the sheet template. If matches can’t be found, the widget has missing data.
For Global Updates to work well, don’t reference data in the Primary column. The Primary column should contain the name of the metric, and the data should be in other columns.