Cube with calculated fields saved in version 2.x does not show correctly in 3.x

06-23-2009, 1:57 PM
We have been using the cube for a long time and are very happy with it. We have an old application which used cube version 2.0.4.0. We have lot of saved cubes in that version. Now when we open same cube in version 3.3.0.125 or 3.3.0.126, the calculated fields do not show up correctly.

Attached is the cube file which was saved with version 2.x. You will see the Yes% and No% calculated incorrectly if you open the cube in version 3.x, but opens correctly in version 2.x.

Re: Cube with calculated fields saved in version 2.x does not show correctly in 3.x

06-24-2009, 3:37 AM
Alok,

I've reproduced the issue that 2.x saved cube files load incorrectly with 3.x version (Calculated GroupFooters are wrong). I've entered a Case 131800 to address this. Unfortunately, I can't give a an estimate of when this case will be fixed because DynamiCube is in "End of Sale phase". The only workaround I can suggest is to load data from database and resave the files from DynamiCube3.

Thank you,
Andrey T.

Re: Cube with calculated fields saved in version 2.x does not show correctly in 3.x

06-24-2009, 8:34 AM
Andrey,

Thank you for your quick response. We have an off-the shelf product with 100's of customers, so it will not be possible for all of them to re-generate the cube from the database.

Is there a possibility that you can ask your development team for a hot fix. Your help will be much appreciated.

Re: Cube with calculated fields saved in version 2.x does not show correctly in 3.x

06-24-2009, 4:11 PM
Alok,

I've raised the priority of this case and also included your comments. I'll inform you if I'd have any news.

Thank you,
Andrey T.

Re: Cube with calculated fields saved in version 2.x does not show correctly in 3.x

07-15-2009, 12:49 PM
Do you have any updates.

Re: Cube with calculated fields saved in version 2.x does not show correctly in 3.x

07-16-2009, 1:23 AM
Alok,

We are woking on this issue now. I'll inform you when we have any news.

Thank you,
Andrey T.