With many companies now updating to Office 365, we are seeing some Essbase clients needing to finally move away from the old Excel Add-in to Smart View.  At the same time we are seeing that the size of Essbase cubes are also increasing due the need for more detailed analysis.

With these two evolutions of Essbase, we have run into two error messages while retrieving and “Zooming In” in Smart View.

Maximum number of rows exceeded

The first error relates to the maximum number of rows allowed for a Smart View grid retrieval:


(click to enlarge)

This error is due the settings in the Provider Services being set to a maximum number of 5000 rows.  This is the default setting in Essbase, and can be changed one of two ways.  The first and simplest way is directly in the EAS client by going to the Provider Server and editing properties.


Then update the Maximum number of rows value:


If there is no server listed after you log into EAS, you will need to add the Provider server.  This is accomplished by first logging into EAS and then right click on Provider Servers -> Add Provider Server.  Then enter the server URL.



The second option to address the row retrieval error is to update the Essbase.Properties file directly on the APS server with the following statement


You can designate the number of rows that you desire or can enter a value of “0” as shown above that will result in an unlimited number of rows.

Maximum number of rows processed

The other error message that we have seen when zooming in on large dimensions occurs when the Suppress Missing option is enabled in Smart View.


By default Smart View limits the number of unsuppressed rows allowed prior to applying #Missing suppression to 250,000 rows. In this example above the number of unsuppressed rows exceeds the 250,000 limit.  This value can be changed by adding the “SSPROCROWLIMIT n” parameter to the Essbase configuration file, with n being the number of rows to consider.

Right click on the Essbase Server, then choose Edit -> Properties:


Add the SSPROCROWLIMIT parameter with the new value:


It is recommended not to exceed 500,000.

NOTE: After making either of these changes, it is required that you restart services before any of the changes take effect.