I have discussed the MultiCube() function a number of times in my series of Variables presentations. In certain situations it allows you to fix measure objects when you have two (or more) unbalanced data providers in a full-client document. ForceMerge() is the equivalent for Web Intelligence.
So how do they work, exactly? What do I mean by unbalanced data providers? How is it fixed with these functions? Are there any special conditions to be aware of? Continue reading “Using ForceMerge() To Fix Unbalanced Data Providers”
One of the more powerful features of Web Intelligence (Desktop Intelligence as well) is the ability to combine data from more than one source into one document. This is done by creating multiple data providers, linking them up, and using the combined results in a report block. However, everything has to work out just right. Sometimes it doesn’t. 🙂
Merging Data Providers in Web Intelligence
Dimensions are the “keys” of a data provider. When two database tables are linked in a universe, certain columns are used to join them together. Dimensions serve this role in linking two data providers. When two (or more) data providers are built in Web Intelligence from the same universe they are automatically linked together using any common dimension objects. What happens when two different data sources are used? In that case, the report writer has to merge the information manually. And if the dimensions from each data provider are not identical, the report has what I call “unbalanced” data providers. That’s what I want to describe in this blog post. Continue reading “What Are Unbalanced Data Providers And Why Should I Care?”
Changing Data Providers in Complex Reports
We have some fairly complex reports at my current client. Of course the word “complex” is not very clear; what is simple to me might be complex to someone else. So let me quantify what I mean by “complex” in this case. The report in question has multiple data provders. Each data provider generates multi-pass SQL because of contexts. Altogether there are 29 data providers with an overall total of over 100 SQL passes. 😯 That’s what I mean by a “complex” report, and I think most folks would agree with that assessment.
The challenge is that for this (and other) complex reports we have been encountering severe issues. In some cases we are unable to edit the queries without restarting our browser session. We also have encountered a number of problems during the process of repointing the document from one universe (development) to another (user acceptance testing) within the same environment. Continue reading “Java Memory Errors During Data Provider Updates in Web Intelligence”
The Evils of Automatic Software Updates
A few months ago about half of the reporting team at my current client called me at various times over a week saying they were having problems running reports. Eventually I figured it out… they all had one thing in common: automatic Java updates. Turns out that was a Very Bad Thing™ to do. 🙂
Continue reading “Java 1.6 / 6.0 Update Issue”
The Challenge
In a previous post I showed a way to create the illusion of an alerter on a chart using the full client product. In this post I will reuse the same technique with a slight twist so that it works in Web Intelligence as well. If you have not already read Part I please do so first so you will be familiar with the basic steps for this technique.
Here is a summary of the steps that I used to solve this in Business Objects:
- Create two versions of the chart: one green and one red
- Create a variable that shows the trend of the data
- Use the Hide Block feature of Business Objects to keep one of the charts from being displayed
- Position both charts in exactly the same space, providing the illusion that the chart is changing colors based on the data
This is all fine… but Web Intelligence does not have the “hide block” feature. So how do I solve this issue?
Continue reading “Alerters On Charts Part II”
