SYMPTOM
After adding a derived metric, the attribute element name diappears or becomes 0 when there is no value returned in the derived metric while the original metric still has a value for that attribute element.
STEPS TO REPRODUCE
Execute the following steps in Strategy Tutorial:






CAUSE
This is a known issue with Strategy 9.0.x and 9.2.x. Report SQL with 2nd metric is generated as follows:
Sql
with gopa1 as (select a11.MONTHID MONTHID, a11.REVENUE WJXBFS1 from MSU2U1.FACTTABLE a11 ), gopa2 as (select a12.MONTHID MONTHID, a12.DESCRIPTION DESCRIPTION, a11.REVENUE WJXBFS1 from MSU2U1.FACTTABLE a11 join MSU2U1.TRANSFORMATIONTABLE a12 on (a11.MONTHID = a12.LASTMONTHID) ) select pa11.MONTHID MONTHID, pa12.DESCRIPTION DESCRIPTION, pa11.WJXBFS1 WJXBFS1, pa12.WJXBFS1 WJXBFS2 from gopa1 pa11 left outer join gopa2 pa12 on (pa11.MONTHID = pa12.MONTHID)

After that, the report SQL changed as follows, and the result comes back fine.
SQL
with gopa1 as (select a11.MONTHID MONTHID, a11.REVENUE WJXBFS1 from MSU2U1.FACTTABLE a11 ), gopa2 as (select a12.MONTHID MONTHID, a11.REVENUE WJXBFS1 from MSU2U1.FACTTABLE a11 join MSU2U1.TRANSFORMATIONTABLE a12 on (a11.MONTHID = a12.LASTMONTHID) )select pa11.MONTHID MONTHID, a13.DESCRIPTION DESCRIPTION, pa11.WJXBFS1 WJXBFS1, pa12.WJXBFS1 WJXBFS2 from gopa1 pa11 left outer join gopa2 pa12 on (pa11.MONTHID = pa12.MONTHID) left outer join MSU2U1.TRANSFORMATIONTABLE a13 on (pa11.MONTHID = a13.MONTHID)

Article Reference Number:
KB5516