You can follow any responses to this entry through the RSS 2.0 feed.
You can leave a response, or trackback from your own site.
Categories
- Business Objects (3)
- Best Practices (2)
- Fusion Charts (5)
- Main (3)
- SQL Server (1)
- SSIS (1)
- Uncategorized (1)
- Universe Design (3)
- Web Intelligence (4)
- Xcelsius (12)
- Design Practices (3)
- Excel (2)
- Tips and Tricks (4)
- Workarounds (1)
Archives
- July 2010
- May 2010
- April 2010
- March 2010
- February 2010
- January 2010
- October 2009
- August 2009
- April 2009
- March 2009
- January 2009
- December 2008
- November 2008
- October 2008
Tag Cloud
auto increment
best practices
bonavista
bulletgraph
Business Objects
charting
charting package
conditional formatting
content management
dashboard
datatable
dianne sawyer
dom
Excel
expand
fannie mae
fix
flash charts
fred carter
frederick carter
free
Fusion Charts
grid component
imt slider
inovista
java
javascript
Java Wrapper
microcharts
pathway technologies
populate dimension table
ripoff
scam
sorting
sparkline
SSIS
table
tree grid
universe
User Access
User Management
Web Intelligence
wrapper
Xcelsius
Xcelsius 2008
Latest Tweets
-
Using Filtered rows instead of VLOOKUPS in Xcelsius @
http://davidlai101.com/blog/2010/07/02/using-filtered-rows-instead-of-vlookup/ - posted on Jul 03, 2010
-
New Post on the Xcelsius Push Button Object @
http://davidlai101.com/blog/2010/05/29/xcelsius-push-button/ - posted on May 29, 2010
-
Xcelsius dynamic color binding article and video posted @ http://davidlai101.com/blog/2010/04/06/xcelsius-dynamic-color-binding/ - posted on Apr 06, 2010
-
New post on Xcelsius Canvas Containers @ http://davidlai101.com/blog/2010/03/26/xcelsius-canvas-container/ - posted on Mar 26, 2010
-
Guide on Business Objects access levels posted http://davidlai101.com/blog/2010/02/19/understanding-business-objects-access-levels/ - posted on Feb 19, 2010


Importance of Web Intelligence Contexts
With calculation contexts in web intelligence we are able to generate powerful reports quick and easily.
Let’s take an example where we have the following dimensions (year, quarter, product) and measure (revenue).
We can easily build a table to represent the sales revenue for each product in that quarter and year.
Now what if we wanted to display the sales revenue in a different context. For example we might want to display the highest quarter’s revenue each year.
You can add an aggregate row that happens after each year and retreive the highest quarter’s revenue from there.
But what if we want our values combined with the first table? This is where context calculation is important.
To accomplish this we need to take into account 3 points
calculation – maximum revenue
input context – year, quarter
output context – year
The combination of input and output contexts tells web intelligence to sum the revenue for each year/quarter and then output the maximum value for each year.
The formula to accomplish this is as follows “calculation(input context) output context” => Max([Revenue] In ([Year];[Quarter])) In ([Year])
The result will come out as the following

Finally we can insert the formula into the last column of the first table and instead of having 2 tables we can have everything on 1 table.
