Essbase Studio disappointing features

 As part of our upgrade of Essbase, from 11.1.1.3 to 11.1.2.3 it was our plan to move away from Essbase Integration Services [EIS] and start to use Essbase Studio.  

Having done our upgrade we have realized two serious problems with Essbase Studio:

1) Drill through from smart view is only allowed on a single cell, not a range.  Our users make use of drilling through on ranges of cells now and will be disappointed to lose that functionality.  Why would Oracle indicate that Essbase Studio is the direction customers should move in and reduce functionality compared to EIS?

2) We have setup an active/passive high-availability configuration for Essbase and related EPM components.  Essbase studio is not supported for high-availability.  My initial assumption was that the reason related to write-back issues to cubes but now I am also seeing that when we fail-over to the high-availability instance of Essbase we will lose the ability for users to drill down to relational data.  This drill functionality is important to our users so losing it largely defeats the purpose of having high-availability for Essbase.