| Product(s): | APM Implementation and Performance Management | |
| Version(s): | 7 | |
| Environment: | N/A | |
| Area: | N/A | |
| Subarea: | N/A | |
Problem Description
An APM user with a 4D analytics integration was experiencing an issue with some indicators not calculating whereas some nearly identical indicators were calculating successfully.
Solution
The behavior occurs only with a specific set of circumstances. This occurs when the calculated indicator's asset classification is a Maintainable Asset, and the input indicator's asset classification is not the same as the calculated indicator's asset classification. APM code confuses the status of the input asset in these cases to think the input is an uninstalled component.
This was reported as a bug, VSTS977249.
The workaround is to ensure that all assets involved in the calculation are given a n Asset Status that is Operating (In Service)
See also
SR 7001461779