2. We create a variable: var2 = [Query 2].[Year].
3. In Web Intelligence XI 3.1, assigning [Query 1].[Year] to one of the axis of a cross-table and var2 to its body will result in the following:
4. Once migrated to Web Intelligence 4.x, the same table will result in the following:
The reason is that, in Web Intelligence 4.x, var2 is automatically added to the vertical axis of the cross-table. And since its content is incompatible with [Query 1].[Year], then the table becomes empty.
5. Note that if [Year] from query 1 and query 2 are merged, then Web Intelligence XI 3.x will automatically display the content of the merged dimension in the body of the cross-table:
6. In Web Intelligence 4.x, the result will still be an empty table:
2. If merging the two dimensions is not possible, then the dimension variable in the body should be modified into a measure variable. Indeed, measures are not automatically added to the table axis.
In our example, defining var2 as a measure instead of a dimension will result in the same output than in Web Intelligence XI 3.x:
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Subject | Kudos |
---|---|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
User | Count |
---|---|
21 | |
16 | |
13 | |
12 | |
11 | |
10 | |
8 | |
8 | |
7 | |
7 |