Palo Community Forum

I have used the eclipse client for a very short time only. But I have two suggestions to make, nevertheless (perhaps not so difficult to implement..).

1) After loading the cube data, these data are first displayed with all the row and column hierarchies expanded. Could there be an option to have the all the elements collapsed instead (even if the loading takes the same time) ? Perhaps there is, with the past element frame, but that frame seems to me to be difficult to use, everything seeming often stalled for a long time (following bad manipulation perhaps ?).

2) When using dimensions with large hierarchies, it takes some time to collapse what you want to see collapsed and expand again what you want to see expanded (even if each indidual change takes place very fast, even with large hierarchies). So it is a pity that, when you choose afterwards an other element in one of the page dimensions, all the rows and columns's presentation is lost (every rows or column dimensions being expanded again). Could not the previous presentation be memorized to be kept unchanged? The tool would really be pleasanter to use with large hierarchies (even with not so little ones).

Thank you for your quick answer ; I shall make more tests with the eclipse client next week after refactoring my not so little database (250000 not empty cells): I have made the error of thinking as if with TM1, EXCEL LOCAL CUBES. or ANALYSIS SERVICES : instead of creating two different hierarchies in the same dimension, I have created two different dimensions (with only one cell not empty as the two dimension cross themselves); it leads to very important response times both to load and to access data in PALO (from EXCEL, PHP, or ECLIPSE CLIENT). I think the change will lead to a huge improvement (I was beginning to think that PALO was not to be used with large dimensions...).

Window/ preferences works only when opening the cube; when you select an other element in a page dimension this preference is not taken into consideration any longer (it will if you keep later the first display model).

When you expand afterwards the lower level displayed, all remaining levels are expanded at once. I made a test with a dimension that contains 26000 elements in a five levels hierarchy with 6 elements at the second level; so when you expand one of these 6 elements about 4000 element are displayed !

There should be two kinds of preference options:

- one that behaves as now : X levels expanded at first, then all remaining levels expanded,
- an other alternative one : X levels expanded at first, then expansions made one level by one level, only as needed (classical behaviour as with the demo_ rc3.php example)

I had not all tested ! if the preference X is equal to 1 , the levels are only expanded 1 by one, just what I was asking for !

I also think that opening the remaining levels one by one is the best option (at least if the dimension hierarchy is large with many levels).

I have not dared to already ask for an option given dimension by dimension, but I have given it some thought. It could also be taken into consideration that usually, more details should be asked if the dimension is displayed in rows than if the dimension is displayed in columns (from my experience).

Last, the preference window should be easy to open for its options being changed and applied from that time on. Sadly and strangely I have experienced a problem to open it while a cube was displayed : I had to stop the application altogether and re-run it (lack of memory perhaps, the dimension displayed being large).

I have changed my test cube to no longer load clients details in it, in order to obtain a less sparse cube, and I have now very good time responses.

Is is nice to know that you are already planning some improvements and that your are keen on listening to users' reactions and suggestions.