![]() | |
![]() |
| | Thread Tools | Display Modes |
#1
| |||
| |||
|
#2
| |||
| |||
|
|
Check out the following screenshots I took from the KPI browser: http://www.entrysoft.com/Gauge1.jpg value -0,5 showing it in green. http://www.entrysoft.com/Gauge2.jpg value -1 showing it in red. http://www.entrysoft.com/Gauge3.jpg value 0,5 showing it in green (exact same position as -0,5). I don't get it, is this a bug? What am I missing? I'm using SQL Server 2005 SP1. -- Kind regards, Stijn Verrept. |
#3
| |||
| |||
|
|
can you post the MDX syntax you use to identify the gauge color? |
#4
| |||
| |||
|
|
Jerome P wrote: can you post the MDX syntax you use to identify the gauge color? Sure: Case When Round([Measures].[Percent Rejected], 4) < .0103 Then 1 When Round([Measures].[Percent Rejected], 4) >= .0103 AND Round([Measures].[Percent Rejected], 4) < .0104 Then .5 When Round([Measures].[Percent Rejected], 4) >= .0104 AND Round([Measures].[Percent Rejected], 4) < .0105 Then 0 When Round([Measures].[Percent Rejected], 4) >= .0105 AND Round([Measures].[Percent Rejected], 4) < .0106 Then -.5 Else -1 End -- Kind regards, Stijn Verrept. |
#5
| |||
| |||
|
|
the system evaluate the value case by case until he found a match, so there is no need to compare using >= but I don't see something wrong in your query. maybe there is a problem in the XSLT file to display the right picture for the -0.5 value. |
![]() |
| Thread Tools | |
| Display Modes | |
| |