Troubleshooting Indicator Mass Update Requests

This topic explains common reasons for the Indicator Mass Update wizard to fail to update target indicators. It lists reasons the update failed that you might find in the Failed Updates tab of the log, along with suggestions for solving the problem.
The Indicator Mass Update wizard allows you to select any number of eligible target indicators. However, performance of the wizard might be unacceptable if too many indicators are selected. Performance can also be affected by the number of properties selected, as well as by the business logic that is triggered when certain properties are set. Failed updates can make the process take longer. When it hits a failed indicator, the system rolls back all of the copies to that point, and then re-does the successful ones.
There are three locations where failed updates are listed:
In the Indicator Mass Update wizard, select the Failed Updates tab after the process has completed.
Mass update requests for all indicators in the enterprise are listed in the Enterprise window, Configurations view, Mass Update Requests tab. Double-click a request to open its window. See the Failed Updates tab.
Mass update requests for the source indicator are listed in the Indicator window, Where Used view, Mass Update Requests tab. Double-click a request to open its window. See the Failed Updates tab.

A Dependant Property Was Not Selected to be Copied

Dependencies can exist between properties. For example, if you select the “Indicator states” data member to copy, the update will fail for any target indicator whose “Indicator states exist” attribute is not already set to “Yes”.

Examples

“The Indicator states could not be updated because it is read-only.”
“The Unit of measure could not be updated because it is read-only.”

Solution

Check the list of data members and their dependencies in Indicator Value Types and Their Dependencies. Copy the primary and dependent properties to the target indicators.

Cumulative Indicators Whose Readings are Cascaded

If you wish to copy the indicator from which readings are cascaded, ensure that the target has the “Collection method” attribute “Cascaded from another asset” and that you copy the asset as well.

Example

“Indicator from which this indicator’s value is cascaded-> Indicator ‘Cumulative3’ does not belong to asset - .”

Solution

Copy the “Asset from which this indicator value is cascaded” data member. Copy the “Collection method”.

Indicator Names are Not Unique for the Asset

If you copy the “Indicator name” attribute to another indicator on the same asset, the update will fail.

Example

“Indicator-> Indicator name-> An indicator called Numeric A already exists for asset 5. Indicator names must be unique per asset.”