Hi,
I find that this have been adressed before, and that it apparently shall have been solved with some hotfix to the 10.3 version.
I am however using version 11.1, and am not able to get this to work (below showing a snapshot from my application with a quite simple cube report and quite a lot of these annoying emty rows).
Are there any settings I am missing?
If it has any relevance I am using an ADOMD connection to a MSSQL 2008 Analysis services cube database.
RegardsJorvart
Hello Jorvart,
I have been looking into your issue and cannot actually say what is causing it. The new functionality is not controlled by the API it is simply built-in and has been working without a hitch so far. I was wondering if you could please provide us with some more details about your project or if possible some test sample we can use to reproduce this and further investigate it.
Looking forward to hearing from you.
Ooops, sorry.
When looking deeper into this I find that your system works exactly as it should. I had made an error in my cell format setting so that 0 values 'disappeared'.
The shown 'empty' rows actually had transactions behind them, but the aggregateted values became 0.
Thank you for answering, and sorry again for wasting your time on my error.
Regards
Jorvart