If the same analysis is trying to be used for multiple templates, there will be times when some attributes are not available from a template - this will cause the analysis to fail. Even when the difference in attributes is known and attempted to be handled with an if/then/else statement, the overall line will fail if it contains an attribute that does not exist even if the logic will not be executed.
For example, Template1 contains Alarm1; Template2 (child of Template1) contains Alarm2 and Alarm3 (and inherits Alarm1). There is no way presently to create a single analysis on Template1 that will cover if Alarm1, Alarm2, or Alarm3 are active because Alarm2 and Alarm3 do not exist on Template1.
I have attempted to work around this issue by creating a "dummy" attribute on Template1 called Alarm2 that is defaulted to "Not Installed". Using an if statement in the analysis to identify which alarm set to use, I would analyze the attributes; however, if the "else" portion of the statement contains attributes that do not exist on the template, it does not matter whether or not the if statement is true.
This request is similar to PIDA-I-972 and PIDA-I-1003, but it is more broadly scoped to go beyond just the rollup analysis and PI tags, but to include all potential attributes.