When interfacing with Essbase information sources by means of Hyperion Essbase Deployment Services (EES), numeric esteems will despicably be returned as strings. This is a Hyperion issue. They guarantee that this will be settled in a future discharge. The workaround is to sidestep EES and interface with Essbase locally. (Hyperion Case #370427, DB2 Alphablox following #18668)
Drillthrough operations won't work when utilizing Hyperion Essbase Integration Services (EIS) to get to Hyperion Essbase Deployment Services (EDS), when the EDS server is sent on Unix frameworks. This is a Hyperion issue. Hyperion expresses that EIS Drillthrough from EDS on UNIX stages is not bolstered for 6.5.x. It is just bolstered on adaptation 7, which is currently accessible (DB2 Alphablox following #18681).
In the event that the Essbase essbase.cfg design record has the SSLOGUNKNOWN property transformed from its default an incentive to FALSE, recovering a Bookmark may show individuals which never again exist in a diagram. To evade the issue, keep the SSLOGUNKNOWN property set to its default estimation of TRUE. This will empower DB2 Alphablox to identify the issue and restore the suitable blunder message. (DB2 Alphablox following #17941).
On the off chance that you utilize Query Builder to develop an inquiry against an Essbase information source utilizing a computed segment name that shows up as a number (e.g. 400), a figured segment mistake will be returned. The workaround is to rename the figured section to something non-numeric. (DB2 Alphablox following #14491).
When utilizing the {RENAME} summon for a part, the intuitiveness in the network is lost (no drilldown), any progressions made to the individuals in the Page pivot are overlooked, any renamed individuals are not shown in the outline. (DB2 Alphablox following #12591).
Utilizing the ORDERBY summon in your report determination returns individuals as a connected string as opposed to restoring the discrete individuals in a comma delimited rundown. This makes a blunder happen. Hyperion case #120488.
Utilizing { PRINTROW "n" } with <PAGE part provisos in your report particular causes a mistake. Hyperion case #183804.