While maintaining registry settings for Analysis Office 2.0 in a client PC settings are handled differently in Analysis Office 2.0 in compare to Analysis Office 1.0
Solution:
This problem occurs because, in the Analysis Office 2.0, the settings are maintained in the file system and not in the registry. The Analysis specific settings are stored in the file system. Therefore to resolve the issue we can change existing settings in the file system of the client PC.
As an Administrator, the settings can be maintained at machine level in two files: Cof_app.config. and Ao_app.config
The files will be located in the file system under %PROGRAMDATA%SapCof.
administrator level setting.jpg
As a user, settings can be changed by us from user level in two files: Cof_user_roaming.config. and Ao_user_roaming.config
The files will be located in the file system under %APPDATA%SapCof.
user setting.jpg
The above mentioned files will be created automatically if the setting is changed in the settings dialogue. The files can also be created manually
If the setting is not already available in the file, we can copy this setting from Cof_app.config or Ao_app.configfiles and then change the value.
The Administrator can also define whether the user is allowed to change a setting locally or not.
Allowing the user to change setting locally
Go to the folder %PROGRAMDATA%SapCof and open Ao_app.config file.
The configuration level defined in the configSections area for each setting. Therefore default level is UserRoaming, which means that the setting can be changed by the user locally. In this situation, if the same setting exists in both Ao_app.config and Ao_user_roaming.config, the value in Ao_app.config. will be overwitten by the value in Ao_user_roaming.config
<configSections>
...
<section name="PreferredPlatform" type="Int32" configurationLevel="UserRoaming" />
...
</configSections>
Not allowing the user to change setting locally
For this administrator have to change the configuration level for one setting to PerMachine, after this the setting can no longer be changed by a user locally. The value of this setting from Ao_app.config is used in any cases and the value of respective settings from Ao_user_roaming.config is ignored.
<configSections>
...
<section name="PreferredPlatform" type="Int32" configurationLevel="PerMachine" />
...
</configSections>
Example:How to maintain Analsyis Office settings at administrator level?
ResultSetSizeLimit
Go to the folder %PROGRAMDATA%SapCof and open Ao_app.config file.
Search and find the entry for ResultSetSizeLimit.
<!--default: value="500000" --> (This is Comment Line)
<ResultSetSizeLimit /> (The default value for this setting is empty. It means this setting will use the default value 500000 for maximum number of cells.)
The parameter can be set to -1 so that the setting uses the values defined in the BW system.
<!--default: value="500000" -->
<ResultSetSizeLimit value="-1" />
Or the parameter can be set to a specific number so that it define the maximum number of cells with this value.
<!--default: value="500000" -->
<ResultSetSizeLimit value="1000000" />
Save the Ao_app.config file
