Hello all. I've viewed a number of post regarding a stylesheet error "bad value" but cannot seem to get a solution.
I am creating a report that computes the difference and % difference of columns after an ACROSS. I am trying to create a condition on the % change. Here's what I have and it was built in the GUI:
SUM
'CNT.CUSTOMER/I9C'
BY 'GROUP'
ACROSS 'MONTH'
COMPUTE DIFFERENCE/D12C = C2 - C1;
COMPUTE PERCENT_CHANGE/D12.3% = (DIFFERENCE / C1 ) * 100;
COMPUTE FLAG/A1 = IF ( PERCENT_CHANGE GT 5 ) THEN 'Y' ELSE 'N';
ON TABLE SET STYLE *
UNITS=IN,
SQUEEZE=ON,
ORIENTATION=LANDSCAPE,
$
DEFMACRO=COND0001,
MACTYPE=RULE,
WHEN=FLAG EQ 'Y',
-* Bunch of styling follows this, then GUI
-* builds this:
$
TYPE=DATA,
COLOR='RED',
STYLE=BOLD,
MACRO=COND0001,
-* More styling
END

How does WF treat computed fields that need to come after an ACROSS? Does it not recognize them as legitimate fields?

Thanks all.

This message has been edited. Last edited by: Kerry,

Hello BobV,

It seems like you cannot reference COMPUTE'd fields by name when they've been created after an ACROSS but you can reference them by position.

Your example leads me to think that the number of ACROSS values in your request is always the same (2 months) which simplifies things. I've worked out an example using the CAR table based on a similar post (Negative Red) which might be useful to your case:

TABLE FILE CAR
SUM SALES
BY CAR
ACROSS COUNTRY
COMPUTE DIFFERENCE/D12C = C2 - C1;
COMPUTE PERCENT_CHANGE/D12.3% = (DIFFERENCE / C1 ) * 100;
COMPUTE FLAG/A1 = IF ( PERCENT_CHANGE LT 0 ) THEN 'Y' ELSE 'N';
WHERE COUNTRY IN ('ENGLAND', 'JAPAN')
ON TABLE SET STYLE *
UNITS=IN, SQUEEZE=ON, ORIENTATION=LANDSCAPE, $
DEFMACRO=COND0001, MACTYPE=RULE, WHEN=C5 EQ 'Y', $
TYPE=DATA, COLOR='RED', STYLE=BOLD, MACRO=COND0001, $
ENDSTYLE
END

The main point there is that the FLAG field is being referenced as C5 (positional notation) instead of by name and in that case the conditional style works.


Neftali.

This message has been edited. Last edited by: njsden,

Neftali, thanks for the quick response. More importantly, thanks for the solution. This worked. The GUI could use a little help when dealing with this.
7.6.1 would not do it for me, perhaps 7.6.10 will once we get it.

You're very welcome. I'm glad it helped!

I totally agree with you on the need for a much better support on these and other features from the GUI in Dev Studio but for now we'll have to rely on the good ol' editor.

Cheers,
Neftali.