How can I compare Cube versions which don't align?
I have a large cube (~23mb), which due to it's size and use we have set up 7 versions.
I have an issue where Aligning is not actually aligning call versions. Version 1 is ending up slightly different to Versions 2-7.
I'm trying to compare V1 and V2 to hopefully work out where the issue is. The problem I have is that the csv file for V1 is >100mb, with more records/lines than Excel is able to show.
Does anyone know of a way to force BOARD to use a particular version. Alternatively, if I was to create some temporary cubes (purely to allow me to determine where the issue is), one dimensioned as V1, then other as V2, which version would BOARD use to dataflow to the new cubes?
Answers
-
when you enable data entry on a block it forces Board to use the first version. So when you put the cube twice in one layout and enable DE on one of the blocks, you should have one block using V1 and the other using one of the other version (depending on the rest of the layout and selections and so on).
You can check the capsule log to find out which versions where used in the query.
Otherwise you could extract V2 and load it into a diffferent cube.
Also: the reason for the missing values will probably be a missing relationship. So by fixing any problems in your relationships you will probably also fix your align problem.
BR
Sebastian
2 -
Thanks Sebastian, good tip about turning on Dataentry to force V1.
I ended up fixing it without actually being able to check where the difference was. I created a new cube with the same dimensions as V1, then dataflowed to this...which should force it to use V1. What was interesting is I then ended up with different values between the source V1 and target..the target checksum was matching V2-7 of the source cube..even though it would have dataflowed V1 due to the dimensions of the target cube. I cleared the original cube, dataflowed back into it from the new cube, then aligned. Now it aligns fully (to what was previously in V2-7.)
1 -
maybe you deleted a member of an entity included in V1. Sometimes BOARD then remember this value. Normally when you extract the cube, clear it and then reload the value is ok for all versions. Of Course the relationships must be OK like Sebastian Gurt said before.
0
